FAQ
01What this is
Each upload is a single web page, the kind of standalone file Claude (or any AI tool) produces when you ask it to write a report, build a small dashboard, or sketch out a one-off page. You upload the file, Vandygraph gives it a link of the form vandygraph.com/v/<name>, and you decide who can open that link.
Vandygraph doesn’t build websites, edit your file, or pull in anything that lives on your computer. If your page tries to load an image from your hard drive, that image won’t be there once the page is live.
Use Vandygraph when you have a one-off page (an AI-generated report, a printable summary, a campaign recap, a small interactive dashboard) that you want to live at a stable link you can update without re-sending.
02Sign in
Sign in with your work Google account. Vandygraph reads the part of your email after the @ (the domain) and checks it against the list your org has approved. If your domain is on the list, you’re added to the org automatically the first time you sign in. There is no invite step.
Open your org’s link.
It looks like https://<your-org>.vandygraph.com. If you don’t know what to put before the dot, ask whoever set up the account at your company.
Click “Sign in with Google.”
Google handles the password. You land back on your org’s dashboard. If you sign in with a personal Gmail, or an email not on your org’s approved list, Vandygraph turns you away with a generic message that doesn’t confirm whether the org exists.
You’ll know it worked when your name appears in the upper-right of the dashboard.
03Upload a page
You upload one file at a time, up to 5 MB on the free plan or 25 MB on a paid plan (roughly a long Word doc with images). Before saving, Vandygraph checks that the file is a web page, technically an HTML file, the same thing Claude produces when you ask for a “single self-contained page.” Anything else is rejected before it reaches storage.
Title.
Up to 200 characters. The title becomes the end of your share link after lowercasing and turning spaces into hyphens, so “Q3 Acme Recap” becomes q3-acme-recap.
The file itself.
A single web page (HTML). Styles, fonts, and scripts built into the file work, as do images and fonts loaded from a public web address. Images that live next to the page on your computer (referenced as ./logo.png) don’t get uploaded with the file, so the page can’t find them once it’s live. If Claude made the page, ask it to “inline everything into a single self-contained HTML file” and the problem doesn’t come up.
Visibility.
Defaults to Private, so only you can see the page while you preview it. The setting is editable later from the page’s edit screen.
Optional: attach to a team.
If you’re on a team inside your org, you can scope the upload to that team, and only people on the team will see and manage it. The option doesn’t appear if you aren’t on a team.
Upload.
Vandygraph checks the file, picks a unique link, and saves it. If saving fails, the upload doesn’t appear at all; nothing is left half-created.
You’ll know it worked when your new page appears at the top of your dashboard.
Vandygraph stores the one file you upload and nothing else. If the page tries to load an image or stylesheet from your computer, that piece will be missing once it’s live. Ask Claude to embed images directly into the file, or use images that already live on the web.
04Who can see it
There are five settings. Every time someone opens the link, Vandygraph re-checks whether they’re allowed in, so there’s no “publish” step. Change the setting and the next visit sees the new state.
| Setting | Anyone with the link (not signed in) | Signed in, your company | Works for guests outside your company |
|---|---|---|---|
| Public | yes | yes | yes |
| Company | must sign in | yes | no |
| Team | must sign in | team members only | no |
| Custom | must sign in | only specific emails on the list | the listed email also has to be on your approved domain |
| Private | must sign in | you only | no |
Custom lets you list specific people who can see the page, but it also requires their email to be on a domain your org has already approved (the kind of extra safety check engineers call “defense in depth”). If your org approves acme-co.com, you can list colleague@acme-co.com, but client@external.com will still be turned away.
For sharing with anyone outside your org, the only setting that works is Public. The link itself is the key, long enough that no one can guess it. If a Public link ends up somewhere it shouldn’t, change the link (see 06).
05Sharing the link
The link you send out looks like https://vandygraph.com/v/<name>: short, plain, no company name in front. Your dashboard’s “Copy” button puts this version on your clipboard. There’s also a longer version with your org’s name in front (your-org.vandygraph.com/v/<name>) but it only works for people already signed in to your org. Send the short version by default.
When someone opens the link, Vandygraph decides whether they’re allowed in before showing them anything. If they are, the page loads inside a secure preview window (technically a sandboxed iframe served from a different web address). Scripts inside the page run, but they can’t see the visitor’s signed-in account, read cookies, or affect anything outside the preview. If you change the link later, every copy of the old link stops working instantly.
| Title | Link | Visibility | Updated |
|---|---|---|---|
| Q3 Acme Recap | /v/q3-acme-recap | Public | 2m ago |
| Onboarding brief | /v/onboarding-brief | Company | 1h ago |
| Pricing draft | /v/pricing-draft | Private | Yesterday |
Copy the link from your dashboard.
Use the row’s “Copy” control. The link looks like https://vandygraph.com/v/<name>.
Test it in a private or incognito window before sending.
Open the link in a window where you’re not signed in. If the page loads, it really is Public. If you see a sign-in screen, the page is still on a restricted setting.
You’ll know it worked when an incognito window opens the page without asking you to sign in.
Send it.
Email, Slack, calendar invite, anywhere. The recipient opens it on any device.
06Editing later
A stable link is useful because the page behind it can change. Every edit lives on the page’s edit screen.
Replace the file.
Upload a new version. The link and access rules stay the same, and anyone who already had the link sees the new page on their next reload.
Rename the title.
The title is cosmetic and the link doesn’t change with it.
Change the link itself.
Useful when you want to break an old link that’s been forwarded somewhere it shouldn’t go. The old link stops working immediately and the new one is yours.
Change the visibility setting.
Flip between the five options. The change takes effect on the next visit.
Transfer to someone else.
Hand the upload over to another active person in your org. They take full control.
Delete.
Removes the page and the file. The link then behaves the same as a link that never existed.
07Org settings
The settings page covers members, approved email domains, your brand, and teams. It’s restricted to admins and owners. Anyone else asking for it gets a “not found,” the same response Vandygraph returns for anything a visitor isn’t allowed to see (the platform never confirms whether a page exists to someone who can’t access it).
Members
Most people are added automatically the first time they sign in, as long as their email is on an approved domain. To add someone explicitly (a contractor working from a different email, for example), use “Add member by email.” They must have signed in to Vandygraph at least once for this to work.
Approved email domains (owner only)
This list controls who auto-joins. Removing a domain doesn’t kick existing members out; it only stops new sign-ins from that domain from being added automatically.
Brand
A PNG logo (up to 1 MB), a primary color, and an accent color. The brand shows up on your org’s dashboard only. The shared page at vandygraph.com/v/<name> carries no logo or colors, so your brand never leaks into something you’ve sent to someone outside the company.
Teams
Teams are smaller groups inside your org. Create one at /teams/new. Any active member of a team can manage files attached to that team, not only the person who first uploaded.
08What to watch for
Files cap at 5 MB on the free plan (25 MB on paid). Large embedded images are the usual reason a page goes over. Smaller images, or images linked from the web instead of pasted into the file, fix it.
The preview is locked down. Scripts inside your page run, but they can’t see anything outside the preview window (your signed-in account, cookies, and so on). Public fonts and scripts loaded from the web work normally. A page that needs to talk to a private backend (anything behind a login) will require that backend to permit it with a setting called CORS.
“Not found” can mean anything. A link that doesn’t exist, one that does but isn’t visible to the visitor, and one that’s been deleted all return the same response. This stops people from probing URLs to learn what’s there. If a recipient says “your link is broken,” the visibility setting is the likely cause.
“Link name already taken” on upload. Rename the title and try again.
Links are unique across all of Vandygraph. Two different orgs can’t both own /v/q3-recap. If your title collides with one that’s already in use, Vandygraph quietly adds a few random characters at the end of the name.
Send the short link. The version that starts with plain vandygraph.comworks for anyone. The version that starts with your org’s name only works for people already signed in to your org.