Sharing & permissions

Public and private maps, invite links, and how editor seats work.

Alkahest's sharing model in one line: projects live in workspaces, maps decide who can see them, and editor seats decide who can change them.

Visibility

  • A public project's maps are readable by anyone with the link — no account needed.
  • A private project is visible to workspace members (and invited collaborators) only.
  • Visibility can also be set per map — keep the project private but make one map public, or the reverse.

Every map has a stable Copy link URL. Access always follows the map's visibility — flipping a map private instantly gates the link.

People

  • Workspace members — your team. Each member has a seat role: viewer, commenter, or editor. Owners/admins manage members and settings.
  • Invite links & email invites — share an invite link (or send it by email) to bring someone in as a collaborator on a project or a single map, without adding them to the workspace.
  • Restricted projects — narrow a project inside the workspace to owners/admins plus an explicit allowlist.

Editor seats

Editing (issues, notes, publishing) needs an editor seat. Viewers and commenters are free; the Free plan includes one editor seat, Pro removes the cap. Reading and commenting never consume a seat.

Tokens

  • Publish tokens (alk_…) authenticate the CLI/MCP as you — anything your account can edit, your agent can edit. Create and revoke them at Publish tokens.
  • Widget tokens are scoped down to filing reports only — see Report widget.

Where to manage it

Everything lives on the Projects page: the project card's Share & access… (visibility, people, invite links) and each map's own visibility/share controls on the Maps page.