Tano has distinct access boundaries: membership roles in an online workspace, OS permissions on a local folder, and permissions of an agent you configure separately. None automatically substitutes for another.
Online membership roles
The workspace service distinguishes owner, admin, writer, and reader. Owners and admins can edit content and manage membership, workspace settings, and plugins. Writers can edit workspace content but cannot manage the workspace in settings. Readers can view content. Workspace deletion and billing remain owner-only. Unauthorized users cannot access workspace content. Desktop two-way file sync requires owner, admin, or writer access; readers in a live session cannot submit edits.
Membership is managed by the connected service. A writable local folder does not grant online membership. See Online workspace and File sync.
Workspace owners and admins can invite a teammate by email with admin, writer, or reader access. An invitation grants no access until the recipient signs in with that verified email address and accepts it. Invitations expire after seven days and can be revoked by an owner or admin. Workspace members can view the member list; only owners and admins can change members or invitations. Membership changes cannot remove or demote the workspace owner.
An account's username is its stable @username namespace. Workspaces have separate UUIDs and owners; articles have stable short IDs and owners, independent of their Markdown paths. Workspace owners and admins can manage all members and article collaborators. An article owner can grant registered users view or edit access to that article, or transfer its ownership. Article grants cannot confer workspace management or expose other workspace files, including linked attachments. Workspace content permissions still apply to every article in the workspace.
Article-only editors may change that article's content, but cannot create files, rename or delete the article, or alter workspace rules. Revoking access closes live collaboration connections and blocks subsequent server requests. Copies already downloaded to another device cannot be recalled.
Local file boundary
A local desktop workspace is scoped to the folder you select and does not follow symlinks outside it. Markdown and attachments remain ordinary files; the OS determines whether other applications on the device can access them.
Local MCP Gateway offers scoped file, object, table, and relation queries. Default review access allows proposals; legacy direct Markdown writes require explicit write access. It does not execute arbitrary commands. It also restricts hidden paths and symlinks. See MCP integration and File access and writes.
Configure agent access separately
AGENTS.md can describe working conventions but cannot constrain an agent client's own file, network, or terminal permissions. Grant the directories and tools needed for the task, and review external edits and conflict notices. Local desktop activity records show a tool channel and content differences; they do not prove a model or person's identity.
Hosted @Agent tasks act within the requesting user’s current access; a mention does not grant extra privileges. See agent workflows.