Web dashboard
The web dashboard at https://anchorify.io/dashboard is the primary surface for non-CLI users. It lists every share you own, lets you publish new shares, and exposes a per-share actions menu for the post-publish edits the CLI also supports.
The /new page#
Click New share from the dashboard, or navigate directly to https://anchorify.io/new.
Input modes#
The form has two ways to provide content:
- Paste — paste content into the textarea. The Filename field above it sets the filename, which drives content-type detection (
.md→ markdown,.csv→ table, etc.). If you leave the filename empty, the server stores the share as markdown by default. - Upload — pick a file from disk. The browser sends both the file's bytes and its original filename. The filename field is ignored when an upload is present.
You only fill in one — paste content OR upload a file, not both.
Form fields#
- Filename — optional. Used for content-type detection when pasting. Has no effect when uploading.
- Content — the paste textarea, or the file picker.
- Render as — overrides the detected content type. Choose
Auto-detect from filename (default)to leave it to the filename, or pick one ofmarkdown,code,json,yaml,csv,tsv,html. - Who can access — the access rung:
Restricted(only people you add), or one of the three anyone-with-the-link rungs (read / read + comment / read + comment + suggest). Default is read + comment. - List publicly & allow search indexing — off by default, which keeps the share hidden: reachable only by its link and served
noindex. On lists it on /discover and in the sitemap. - Password — optional. Only valid on a hidden, link-reachable share. Visitors must enter the password before the share renders.
- Slug — optional. If set, the share lives at
/<username>/<slug>. If empty, the server mints a random 8-character base36 id. Must match^[a-z0-9](?:[a-z0-9-]{0,58}[a-z0-9])?$— see slug rules.
Submit, and you land on a confirmation view with the canonical URL and a copy button.
The /dashboard page#
The dashboard lists every share you own, most-recently-updated first. Each row has the title, slug, last-updated timestamp, recent activity, access badge, a primary Copy URL button, and an Actions menu (⋯).
Actions menu#
Every row's ⋯ menu has the same items:
- Open in new tab — opens the share's public URL.
- View analytics — opens the analytics page for this share. Owner-only.
- Make public / Make unlisted / Make restricted — quick flips between the three reachability states, keeping the current rung. "Public" means listed + indexed; "unlisted" means hidden. Switching to public or restricted clears any password (the form asks for confirmation first). The full ladder — including the view / comment / suggest choice — lives on the share settings page.
- Share settings — the full per-share controls: general access, public listing, an Allow downloads of this file toggle (off removes the Download button, the PDF export, and the raw-file URL), a Render as picker, replace-with-a-file, slug, password, and theme.
- Set password / Change password — opens an inline form. Submit with the password field empty to clear an existing password. Only valid on a hidden, link-reachable share.
- Render as… — opens an inline dropdown of every render type. Picks a new one without touching the content. Useful for fixing paste-flow shares that got bucketed as markdown by default. Absent on file-backed rows (images, PDFs, other binaries): what those shares are is the file, so there's no render type to pick — use Replace with a file on the settings page instead.
- Rename — coming via CLI/API; the dashboard form for this lives on the row's edit page.
- Delete — soft-deletes the share. The URL returns
410 Goneimmediately. Hard-deletion runs on a rolling 30-day cycle.
The share page's own ⋮ menu#
Every per-share action is also reachable from the document itself, without going back to a listing. Open the ⋮ in the share's header:
| Item | Who sees it |
|---|---|
| Share settings | Anyone who can change the share's access — org admins, project editors |
| Version history | Org admins only |
| Suggestions | Org admins only. Carries the pending count, and puts a dot on the ⋮ when something is waiting |
| View analytics | Org admins, project editors |
| Move to… | Anyone who can edit the share, including a share-level editor |
| Replace file… | On file-backed shares, anyone who can open Share settings |
| Share on WhatsApp | Everyone |
| Delete | Org admins, project editors. Same confirmation and the same 410 Gone outcome as the row menu |
The top row keeps the things you reach for while reading: Edit or Suggest changes, Make a copy, Copy link, Invite, Download, and fullscreen.
The primary Copy URL button writes the share URL to the clipboard without opening the menu.
Tokens panel#
The dashboard has a CLI tokens panel below the shares table. Use it to create tokens for anchorify login (see CLI tokens).
Sign out#
The top-right menu has Sign out, which clears the session cookie and sends you back to the landing page. The CLI tokens are unaffected — sign-out is a browser-only action.
Fixing a share's render type after publish#
If you publish a share with the wrong content type (the most common case is pasting JSON into the textarea without a filename, which buckets the share as markdown), there are two places to fix it. Either works; the content stays the same and only the renderer changes.
- Share settings → Render as — open the share and choose Share settings, or go straight to
/<org>/<project>/<slug>/settings. This is the one to use if you are not an admin of the owning org: project editors and anyone else who can edit the share can reach it. - Dashboard or project row
⋯→ Render as… — the quick path when you are already looking at a list.
A share backed by an uploaded file — an image, a PDF, any other binary — has no render type to pick: what it is is the file. Use Replace with a file on the settings page to swap the bytes instead.
The same operation is available from the CLI as anchorify type <slug-or-id> <type> and via the API.
Next steps#
- Command-line — the same actions from the terminal.
- Access and passwords — the access model in detail.
- Content types and rendering — every renderer.
- Analytics — what you see on a share's analytics page.