Yard Docs
Sign in
On this page

Sharing and roles

Organization and workspace roles, the Share dialog, organization-wide access, invites, allowed email domains, and view-only links to docs for people outside the organization.

Updated November 3, 2026 · 6 min read

Access in Yard works on two levels: your role in the organization, and your role on each workspace.

Organization roles

Role What it adds
Viewer Opens every workspace they can see, its docs and canvases, files, monitors and status pages, and gets alerts, read only, whatever a workspace's own settings say.
Member Opens the workspaces shared with them and creates new ones.
Admin Manages members and invites, runners, repositories, storage, usage and organization API keys. Owns every workspace.
Owner Everything an admin can, plus making people owners, changing an owner's role, removing admins, and deleting the organization.

Owners, admins and members can edit, as long as they hold a license that counts there. Owners edit their own organization without one, and whoever created a workspace edits it without one; everyone else without a license reads everything, read-only.

An organization always keeps at least one owner. To leave as the last owner, make someone else an owner first.

Change roles under Settings, Members, with the select next to each person. Remove takes someone out of the organization; Leave is on your own row.

Invite people to the organization

Admins invite people under Settings, Members, with Invite people:

  • Enter an email address, pick Member, Admin or Viewer (free), and choose Invite. Yard emails them a link.
  • Copy invite link makes a link anyone can use to join with the chosen role, for 7 days.

A new link is shown once, so copy it before you close it. Pending invites can be revoked. Billing never limits invites: whoever joins without a license reads everything until they get one, or the organization pays for it.

Someone new who opens an invite creates their account from it, confirms their address with the emailed code and lands in the organization, without setting up one of their own. An invite sent to one address fills that address in on the signup and sign-in forms.

Allowed email domains

Under Who can join in Settings, Members, add Allowed email domains such as example.com. From then on, only addresses at those domains can accept an invite or use an invite link; an invite to another address is refused, and the field warns you before you send it. People who are already members stay members. Remove every domain to let anyone you invite join again.

Workspace roles

Role Can
Viewer Open the docs, canvases, files, projects and every chat, read only.
Editor Everything a viewer can, plus edit the docs, canvases and files, chat with agents, run projects, push and open pull requests, and use terminals.
Owner Everything an editor can, plus decide who has access and change the workspace's settings, such as its name, runner, limits and archiving.

Organization owners and admins are always owners of every workspace. Other people get their role in this order:

  1. a role given to them on the workspace;
  2. otherwise, what Anyone in the organization gets on it.

Canvases and docs

Everything in a workspace is open to its members: its docs, prototypes, projects and sheets, each with what a member's workspace role allows. There are no restrictions on a single doc or sheet: what was once kept to a few people has joined the workspace's own, with its chats and links. To keep something from someone, keep it in another workspace.

When someone loses access (removed from the organization, given a smaller role, signed out, their account disabled, or their license or API key ended), what they had open stops updating at once: they are dropped from the canvases, chats and channels they may no longer see, a preview of a port they had open closes, and a terminal they opened ends, with everything it left running, if they can no longer edit the workspace. The Share dialog says it too: everyone with access sees every board, doc and chat.

The Share dialog

Choose Invite under More → People or in a doc's header (on a phone, Invite in the Menu panel). The dialog, Share "<workspace>", lists everyone with access and their role.

  • Invite: enter an email address, pick Editor or Viewer, and choose Invite. Someone already in the organization gets access at once. Anyone else gets an invite link, shown once, that makes them a member of the organization (a viewer, when you picked Viewer) and gives them this workspace.
  • Roles: change a person's role with the select on their row. No access removes their own role; they may still have access through the organization-wide setting, and Yard tells you when they do.
  • Anyone in the organization: choose Can edit, Can view or No access for every member without a role of their own. New workspaces start with Can edit.
  • Copy link copies the workspace's address. Only people with access can open it.

On someone's personal runner, a banner says whether others can edit or only view, and that only the runner's owner manages it.

Only workspace owners can change any of this; everyone else sees the list. The Access tab in Workspace settings shows who can open the workspace and leads to the same dialog (Open Share…, or Show in Share… if you are not an owner).

Share a doc outside the organization

Anyone who can edit a doc can give people outside the organization a view-only link to it. They read it without signing in or making an account, and cannot edit, comment, chat or see anything else in the workspace.

  1. Open the doc and choose Share in its header.
  2. Turn on Anyone with the link can view. The link is copied for you; Copy link copies it again whenever the dialog is open.
  3. Send the link to whoever should read the doc.

While a doc is shared, a globe shows next to Saved in its header and on its row in the sidebar; the globe in the header opens the same dialog. The dialog also says how many times the link was opened, and when last.

What the link shows:

  • the doc's title and its current text: an edit in Yard shows the next time the page is loaded;
  • pictures placed in the doc;
  • references to other docs, branches and pull requests as their names only, and links to web pages as links;
  • prototypes, canvases, repositories, code, cards and other blocks as a line that says they are not included. What is in them is not sent;
  • never the doc's chats, comments, the questions an agent asked in it, or who wrote it.

The page has no scripts, is not indexed by search engines, and cannot be shown inside another site.

Reset link makes a new link and ends the old one at once. Turning the switch off ends the link: whoever opens it is told it is not valid any more. A link also ends when its doc is deleted or its workspace is archived. Archiving the doc does not end it. While the workspace's runner is offline, the page says the doc cannot be shown right now.

Workspace viewers see whether a doc is shared, not its link. API keys cannot make, reset or stop links.

Admins choose under Settings, Members, Sharing outside the organization whether docs may be shared at all. Turning off Allow public links to docs asks first, then ends every link in the organization at once; Share then says links are off. Turning it on again does not bring old links back.

Was this page useful?
Edit this page