Organizations

Symbol supports multi-user workspaces so organizations can share and collaborate on knowledge.

RolesCopy Anchor Link

Each organization member has one of four roles, from most to least authority:

• Owner: full control, including workspace settings, members, ownership transfer, and deleting the workspace. Can also manage any member's shared content: delete it, change its visibility, create and revoke its share links, and edit or delete its projects.
• Admin: writes shared capsules and Types, and manages members below their own tier. Can also manage any member's shared content the same way an Owner can: delete it, change its visibility, create and revoke its share links, and edit or delete its projects. (This role is called "editor" internally; the app shows it as Admin.)
• Member: writes shared capsules and Types, but cannot manage other members or their content, and cannot change a Type's guidance, library template or packaging default (see Type guidance).
• Viewer: read-only access to shared content.

An owner or Admin can review every active share link in the workspace, whoever created it, and revoke any of them, from Workspace settings → Activity → Share links. A member's private (Self) content stays visible to, and manageable by, only its creator.

Transferring ownershipCopy Anchor Link

An owner can hand a workspace to another member from Workspace settings → Members → Transfer ownership. Pick a member, type the workspace name to confirm, and ownership moves: the chosen member becomes the new Owner and you become an Admin. Only the current owner can start a transfer, and it can only go to an existing member. Invite the person first if they are not in the workspace yet.

Transfer changes who controls the workspace; it does not move the billing relationship:

• The subscription stays with whoever purchased it. The purchaser continues to see and manage it, including cancelling, from their personal Billing settings, even after they are no longer the owner.
• Member entitlements are unaffected. A workspace's paid plan applies to the workspace, so every member keeps the same access before and after a transfer.
• Workspace invoice history follows the workspace. Past and future invoices for the workspace appear to the current owner on the workspace billing card. After a transfer the new owner sees them, and the previous owner no longer does, while still keeping visibility and cancel control of the subscription itself.

When a member leavesCopy Anchor Link

Everything a person creates in a workspace stays in the workspace when they go, so nothing is ever left that nobody can manage. This holds however they leave: an owner or Admin removes them, they leave on their own, or they delete their Symbol account.

• Their capsules, Types, Collections and projects pass to the workspace owner. The owner, and any Admin, can then edit, share, archive and delete them like any other shared content. If the owner already has a project with the same short name in another workspace, the handed-over project gets a numbered one, such as roadmap-2, and its address changes with it.
• Their share links stop working. Every link they created on the workspace's content is revoked. Content that was shared only by link becomes Private to the owner.
• Their private (Self) drafts pass to the owner when they are removed or leave, and stay Private, so nobody else gains access to them. The removal and leave confirmations say so before you continue. When someone deletes their account instead, their private drafts in the workspace are deleted with it, along with their files, and stop counting toward the workspace's storage. So are their private Types and projects that hold nothing else.
• Content handed to the owner never counts toward the owner's personal plan. Personal plan limits count only personal-workspace capsules, so a departure cannot push the owner over their own limit.

Removing someone always asks first. The confirmation names the person and the workspace, says they lose access immediately, and then says: "The capsules, Types, Collections and projects they created here pass to the workspace owner, including their private drafts, which stay private. Their share links stop working, and content shared only by link becomes Private to the owner. Their name stays on what they wrote." Cancel leaves them in the workspace.

The owner cannot leave or change their own role. Transfer ownership first; until then, trying either says so.

If you delete your account while you are the only member of a workspace you own, the workspace is deleted with it: its content, its files, its share links and its subscription. If other people still belong to a workspace you own, transfer ownership or delete the workspace first; account deletion is refused until you do.

A transfer of ownership moves nothing. Content keeps its creator, and the new owner manages every member's shared content through the Owner role.

Capsule VisibilityCopy Anchor Link

Control who can see each capsule:

• Self: only you (default)
• Org View: organization members can read
• Org Edit: organization members can read and edit
• Link: only the people you send the share link to. A link does not give other organization members access: to share with the whole organization, use Org View or Org Edit. Adding a link to something already shared at Org View or Org Edit keeps your organization's access as it was. Private is the only choice that removes your organization, and the share dialog asks first. See Sharing.

Deleting the organizationCopy Anchor Link

Only the owner can delete an organization. Deleting it ends every share link on its content. Any capsule or type that was shared by link stops opening at that link, and the content returns to its creator's personal workspace as Private. This matches making content private: withdrawing it ends its links.

Everything else returns to the people who made it:

• Each capsule goes to the person who wrote it, into their personal workspace, Private drafts included. Nobody receives someone else's writing.
• Each person keeps the structure their capsules sat in. If your capsule was in a Type, project or collection someone else created, you get your own copy of it, so your capsule keeps its fields and its place. A project or collection is copied only if you could see it before the deletion; otherwise your capsule simply leaves it. Copies start private to you.
• Names that clash get the organization's name. If you already have a Type or project with the same name, the one coming from the organization is renamed, for example "General (Acme)" at @general-acme. The empty "General" Type a new organization starts with is removed instead.
• Links in your capsules keep pointing where they pointed. A mention or reference to a capsule you now hold is updated to its new address. A mention of a capsule that went to someone else, or that did not exist, can no longer open anything, so it is shown as plain code text, and a reference field that pointed at one is emptied. If that field was required, the capsule is marked incomplete so you can choose a new value. Every change is saved as a new version, so the previous text stays in the capsule's history.

If someone creates a Type or project with a clashing name at the very moment the organization is being deleted, nothing is deleted and you are asked to try again.

InvitationsCopy Anchor Link

Invite organization members by email, as a Viewer, Member or Admin. The email's button opens the invitation itself: sign in, or create your account, and you land back on it to accept or decline in one step. Only the address the invitation was sent to can accept it, and both the email and the invitation page say which address that is. If you open it while signed in with a different address, the page tells you to sign out and sign in with the address that received it. You can also accept or decline from Organizations in the app.

Owners and Admins see pending invitations in Workspace settings → Members. A pending invitation holds a seat until it is accepted, declined, revoked or expires, seven days after it was sent. Resend sends the email again and restarts the seven days from that moment. When someone declines, their invitation stays in the list marked Declined, with the date, and Invite again sends them a new one. Inviting an address that already has a pending invitation is refused with a message saying so: resend it instead, or revoke it to change the role. When every seat is taken, the message says how many hold members and how many hold pending invitations.

Accepting an invitation is the only way into an organization, apart from creating one. Nobody can add you to an organization directly, so you are never made a member without agreeing to it.

An invitation is only as good as its sender's role. If the owner or Admin who sent it is removed from the organization, or changed to a role below Admin, their pending invitations expire. Accepting one then shows "This invitation has expired." Ask a current owner or Admin to invite you again.

Type guidanceCopy Anchor Link

A Type's guidance is the instruction every connected AI assistant reads and follows before it writes into that Type. Three settings on a team Type decide what your organization's assistants are told and how its content is published:

• the guidance (shown as Instructions for AI),
• the library template,
• the packaging default (Publish as).

Only the Type's owner, or an organization owner or Admin, can change these. That includes restoring an older version of the Type whose guidance is different. Other members still edit the Type's other settings, and see these three read-only. Organization API keys cannot change them yet.

When an assistant reads a team Type's guidance, it is also told who last changed it and when. If that person has since left the organization, it is told "a former member" instead of their name.

Deleting a Type other members useCopy Anchor Link

Anyone who created a Type can delete it while it holds only their own capsules. Once other members have capsules in it, only an owner or Admin can delete it, and the delete dialog says so before offering any choice. Other members' capsules are never permanently deleted on their behalf:

• Move them to another Type: every member's capsules move to the Type you choose, each keeping its creator, visibility and archive state. If that Type is View only, capsules members could edit become view only too, so nothing is more open than the Type it's in. Old references to them keep working. The Type you choose must be one the organization's members can see.
• Permanently delete: your own capsules are deleted. Capsules other members created are archived and moved to the workspace's General Type, where their creators (or an owner or Admin) can restore them. Old references to them keep working.

A member's private draft is never archived, shown or counted to the person deleting. It moves unchanged: to the Type you chose, or to General, where its creator still finds it, still private. An encrypted Type that holds other members' capsules can only be deleted by moving them to another encrypted Type. A log Type that holds other members' capsules can't be deleted until those members delete their capsules in it: a log's entries can only be read in a log Type, and capsules can't be moved into another log Type.

Publishing skills and agentsCopy Anchor Link

Publishing a capsule as a skill, or packaging it as an agent, delivers it to every member's machine through the organization's marketplace. That is a form of sharing, so it needs the right to share the capsule: you must be its owner, or an organization owner or Admin for content that is not Private. The same right is needed to update what teammates receive after someone edits the capsule. Organization API keys cannot publish yet.

A Private capsule is not served to the organization as a skill or an agent, even if it was published before it was made Private. Sharing it with the organization again brings it back without republishing. See Prompts & Skills and Agents for the details.

Links outside the organizationCopy Anchor Link

An owner or Admin can stop the organization's content being shared outside it. In Workspace settings → Governance, turn off Allow links outside the organization.

While it is off:

• every share link on the organization's capsules, Types and Collections stops working, and opening one shows the same not-found page as a revoked link,
• nobody can create a new share link on the organization's content. Trying says "This organization does not allow links outside the organization."

Links are suspended, not deleted. Turn the setting back on and every existing link works again. Its expiry date and view limit are unchanged, so a link that expired in the meantime stays expired. Personal content is never affected.

The setting does not cover the files inside a published skill. Those follow the skill: they keep working for the organization's marketplace while the skill is published, and stop when it is unpublished, archived, deleted or made Private. Anyone who already holds a copy of a published skill can still fetch its files while the skill is published, just as they still hold its text.

Organization API keysCopy Anchor Link

An organization API key gives a script, CI job or agent access to the workspace without signing in as anyone. Owners and Admins create, review, hand over and revoke keys from Workspace settings → API Keys. Members and viewers do not see the tab.

• A key works within its scopes. You choose them when you create it. A key with the delete scope can delete capsules, Types and projects that members can see, one with the share scope can change their visibility, and one with the update scope can edit those projects: the same content an owner or Admin manages. Neither ever reaches a member's Private (Self) content. Keys cannot create share links or publish skills and agents.
• A key has a holder. Each key in the list names its holder (Acts as), and content it creates is attributed to that person. What the key may do comes from its scopes, not from the holder's role. When they leave the workspace or delete their account, their keys are revoked and disappear from the list. Re-adding them later does not bring an old key back.
• Hand a key over to keep it working. Choose Hand over on a key and pick another owner or Admin. The key's secret stays the same, so nothing using it needs to change; content it creates is attributed to the new holder from then on. Hand a key over before its holder leaves, since leaving ends it.
• Stopped keys. A key whose holder left before keys ended with their holder is listed as stopped and does not work. Hand it over to bring it back, or revoke it.

CollectionsCopy Anchor Link

Members who can add to a type can add capsules to its collections and remove the capsules they added. Renaming or deleting a collection, or removing other people's capsules from it, needs the collection's creator or an owner or Admin. See Collections in an organization.

MCP Organization AccessCopy Anchor Link

Organization members can optionally enable MCP access to shared capsules, allowing their AI assistants to read organization knowledge directly.

Turning it off for an organization stops AI assistants, MCP clients and personal API keys on your account from reaching that organization's content. It does not affect the web app or the Symbol mobile app. A phone that signed in to the mobile app long ago under a custom device name can count as a personal API key until it signs in again.