Protected Types
Hold every change to a Type and its items for approval, protect all of an organization's content at once, and review and approve changes with a fresh proof of identity.
Protecting a Type means nothing in it changes until someone approves the change. This matters most for content that people or assistants rely on as instructions: a published skill, an agent, a prompt or a Type's guidance. If a key, a connected app or a signed-in browser falls into the wrong hands, whatever it writes waits for approval instead of reaching everyone who reads that Type.
Protection is set on a whole Type, never on a single item. Every item in a protected Type is protected, including ones added later.
What happens to a change
When someone changes a protected Type or one of its items, Symbol saves the change for approval instead of applying it:
- Everyone who reads the Type keeps getting the approved version: in the app, in search and lists, on share pages, and through AI assistants.
- A mention in a protected item, such as
@notes/3, opens the capsule it named when the item was approved, even if another capsule has taken that address since. A mention of something approval did not include, a pointer mention (~@notes/3) and a mention of a Type stay plain text, and so does every mention while the approved version is still being recorded. - A new item does not appear anywhere until it is approved. It is not in lists, search or the Type's page.
- The person who made the change sees Saved for approval, with a link to the change (unless they could approve it and made it in the browser: see Your own changes in the browser).
- Only one change per item waits at a time. A second change to the same item is refused until the first is approved, rejected or withdrawn. If you may review the waiting change, the refusal names it and links to it. The item's Skill menu says Waiting for approval with the kind of change and a View change link, and leaves publishing unavailable until the change is decided.
This applies however the change is made: in the browser, in the Symbol mobile app, with an API key, through a connected app or by an AI assistant. The one exception is a change made in the browser by someone who could approve it, described next.
Your own changes in the browser
If you can approve changes to a Type (you own the personal workspace, or you are the organization's owner or an Admin), most changes you save in your browser apply at once (the exceptions are listed below). There is no trip through Changes for approval to approve your own work.
- When you save, Symbol asks you to confirm it's you, in place, unless you confirmed in the last 10 minutes. One confirmation covers a run of saves.
- If you cancel, nothing is saved and nothing waits. Your edit stays in the editor, so you can save it again.
- The change is recorded in the Type's history on Changes for approval as approved and marked Applied by its author, with who made it and when. Everyone who reads the Type receives it as the approved version, exactly as if it had been approved from the review page.
- If another change to the same item is already waiting, your save is refused and changes nothing. Approve, reject or withdraw the waiting change first. A save never approves or replaces it.
These still wait for approval, even when the person could approve them:
- a change made with an API key, through a connected app, with an organization key or with the Symbol CLI;
- a change from the Symbol mobile app;
- a change from an AI assistant that connects to Symbol, such as through Symbol's assistant server, the Bridge, or any app that tells Symbol it is an assistant;
- an encrypted change, a move that both sides must approve, and a full Symbol import;
- deleting a protected Type itself;
- a new item created together with files;
- a change saved while you were offline and sent when you reconnected;
- every change in an organization whose approval service decides its changes.
Members who cannot approve changes in that workspace keep seeing Saved for approval.
An assistant that operates your own browser, after you confirmed it's you, sends the same session and the same confirmation as you, so Symbol treats what it saves as yours. Only let an assistant use your browser if you would make the same change yourself. Assistants that connect to Symbol any other way always wait for approval.
An assistant can include files with a new item saved for approval. Those files join the waiting change in the item's workspace, whether the assistant names your personal workspace, names the team, gives its ID or leaves the workspace out. The reply says whether the files joined and links to the review.
Protecting a Type
Open the Type, open its settings and choose Protect this Type. In your personal workspace you can protect your own Types. In an organization, the organization's owner and its Admins can.
Turning protection on takes effect at once and needs no extra step, since it only narrows what can change.
Turning protection off asks you to confirm it's you. It also withdraws every change still waiting in that Type. Turning protection off never publishes anything that was waiting.
Skills, agents and prompts
Protection is only ever turned on on purpose: by the Type's owner, by an organization's owner or Admin, or by an organization that protects all its content. Publishing a skill, packaging an agent, making a prompt, or setting a Type's defaults to make its items those, applies at once in an unprotected Type and never protects it.
Types that Symbol used to protect automatically because of such an item have had that protection turned off. A change that was waiting only because of it was withdrawn, nothing in it was applied, and its author and the people who decide changes got a notice in the Inbox. Make the change again if it is still needed: in an unprotected Type it applies at once. Types that their owner or an organization protected stay protected.
To keep a Type that holds skills, agents or prompts protected, choose Protect this Type in its settings.
Checking before a write
Anyone who can read a Type can see whether it is protected. A person sees it in the Type's settings. An AI assistant or script sees it when it reads the Type, so it can choose another Type or leave out a publishing step before it starts, rather than finding out from a change saved for approval.
The Type read says:
- whether the Type is protected, and whether that came from its owner or from its organization
- when protection was set, and when an organization began enforcing it
- when the Type's own protection was last turned off
This reading describes the Type, not what you may do with it. It does not give a reader the right to change protection, and Symbol checks again when the write arrives, so someone else's change between the read and the write still applies.
Symbol Bridge checks protection with Symbol on each full Type listing, even when the rest of the listing comes from its local copy. When Symbol cannot be reached, the listing shows the last value the copy saw and when it was checked. A copy that has never seen a Type's protection says it is unknown, which never means unprotected.
Protecting all of an organization's content
An organization's owner or an Admin can protect everything the organization holds. Open the organization's settings and choose Protect all content.
- Every Type in the organization is protected, existing and new.
- A Type then shows no protection setting of its own, and an attempt to change one is refused.
- Other workspaces, including members' personal workspaces and other organizations, are not affected.
Choosing Stop protecting all content asks you to confirm it's you. Types that were protected individually stay protected. Changes waiting in Types that are left unprotected are withdrawn, not published.
Reviewing and approving changes
Changes waiting for approval are listed on the Changes for approval page (/changes). You can filter by your personal workspace or by an organization. The people who can see a change are:
- its author, who can follow it and withdraw it;
- the people who can decide it: the owner of a personal workspace, or an organization's owner and its Admins.
An organization can also switch on Sentinel, an AI reviewer run by Symbol that approves or rejects each change and sends the ones it is unsure about to an owner or Admin.
Opening a change shows who proposed it, when, and how: in the browser, with an API key, through a connected app or through an AI assistant. A label the client sent about itself (for example the name of an assistant) is shown separately, as the client's own claim. The review shows the approved and the proposed version side by side for every item the change touches.
Deciding never opens content you cannot otherwise read. If a change touches an item you cannot read, you cannot review or decide it.
Approving
Approving asks you to confirm it's you, in a browser session. An API key, a connected app, an organization key and an AI assistant can propose changes but can never approve them, and there is no assistant tool for approving.
Approval releases exactly the version you reviewed. Approving an edit to a published skill also updates the skill your assistants load, when the edit asked for that (an AI assistant's edit does, unless it was sent with republish: false). You approve once: there is no second change to publish it. The new version reaches assistants shortly after, as the skill host picks it up. If the skill cannot be updated, for example because skills were turned off for the workspace, the approved edit still stands, the skill keeps serving its previous version, and the item's Skill menu says why.
When an assistant asks to publish or republish a skill in a protected Type, that request waits for approval too, and the assistant's reply includes the link to review it.
If the change, or the item it was proposed against, moved after you opened the review, nothing is released and you are asked to review it again. Approving the same change twice does nothing the second time.
A new item can show one of its own images in its body. Its review shows the files and images, available only to people who can review that change. Approval creates the exact reviewed body with those files. Older waiting creates that cannot identify their reviewed files ask the author to propose the item again and release nothing. After approval, the review opens the item's ordinary files. Its current access, deletion and retention rules apply there too.
Moving out of a personal workspace
A move from a protected personal Type into a protected team needs both sides. The app says Waiting for its author until the author agrees to moving it out. The team cannot approve it before that step is done.
For content the browser can show, the author can open that review from the app and confirm the source side there. For encrypted content the app shows the waiting status, with no source approval action. After source consent, the team reviews and approves the destination side. Source consent alone moves nothing.
Rejecting and withdrawing
Rejecting closes the change without applying anything. It needs the right to decide but no new proof, since it releases nothing. The author can withdraw their own change at any time while it waits.
Encrypted Types
The server cannot read encrypted content, so it cannot show what an encrypted change does. The web review says so, and the change is reviewed in the Symbol mobile app, which holds your keys and shows the approved and proposed versions side by side.
Releasing it still happens in a browser, where you can confirm it's you. After you review the change, the app opens a confirmation page in the browser for exactly the version it showed. Both the app and the page show a short code for that version: check that they match before you release it, and cancel if they differ. The page asks you to confirm it's you, then releases that version and nothing else.
The confirmation works once and expires after a short time. If the change was edited, or the encryption keys changed, after the app showed it, nothing is released and you review it in the app again. The web app never approves an encrypted change it cannot show, and a confirmation started by someone else's app does nothing for you.
Notifications
The Inbox tells you when a change is waiting for you to decide, when a change you proposed or can decide was approved, rejected or withdrawn, and when protection was turned off. These notices are part of the Inbox for everyone; they do not need Experimental features. They carry no proposed content, and a notice for a change you can no longer see shows as unavailable. No email is sent for them.
Clearing a notice does not change the change it points to.
Apps, assistants and older versions
The current web app, Symbol mobile app, Bridge, Symbol CLI and Symbol's AI assistant server understand changes saved for approval and say Saved for approval. The CLI prints the link to the waiting change, and symbol capsule export writes the approved version of a protected item, the same file a download from the web app gives you. A client that does not understand them is refused instead, with nothing saved, so an older client never reports a save that did not happen. Update it to save changes to protected Types. Developers can read how this works in the preview API reference.
Reading works the same way. Current apps ask for the approved version of protected content, and Symbol delivers it with exactly the material it was approved with. An older app, Bridge or API client that does not ask that way is refused when it reads a protected item, and a list, search or sync that would include a protected item is refused as a whole rather than quietly leaving the item out. Everything outside protected Types still reads as before. Update the app or Bridge to read protected content again; developers adopt the x-symbol-approved-delivery header described in the preview API reference.
An older app or Bridge that is still running may keep using what it already saved on your device. It can show that saved copy, and it can combine a saved protected item with a newer version of something it refers to, until it is updated and its saved copy is cleared. Symbol cannot reach into a device and remove content it already downloaded, so protection describes what Symbol delivers to current apps, not copies held elsewhere.
When the Bridge updates, it stops the older version's background sync on the same computer, removes the copy that version saved, and builds a new copy that holds only approved versions. If the older sync cannot be stopped, bridge_status and symbol-bridge sync-status say the migration is incomplete; quit the apps that use the Bridge, or restart the computer, and open it again. Copies kept on other computers, or by an older Bridge or assistant server you started yourself and have not updated, are not changed by this.
Limits
- Protection decides who can change content. It does not change who can read it, and it never makes anything public.
- Deleting a protected Type waits for approval as one change, whether its items are deleted with it or moved to another Type, and so does deleting a Type whose items would move into a protected one. Nothing changes until it is approved, and approval deletes the whole Type or nothing. If the Type gained items or changed after review, approval releases nothing.
- Adding a file to an item or removing one waits for approval like any other change. A file waiting for approval is kept out of reach until it is approved, and approval adds exactly the file that was reviewed. If the file is replaced before approval, or it waits longer than a day, approval releases nothing and the file is added again for a new review.
- Creating an item with files in it waits for approval as one change, and the review shows the new item with its files. Approval creates the item with exactly the reviewed files, under the same one-day limit. Files you upload after the new item is saved for approval join that change as a new version of it, from the same sign-in or key that proposed it, and a review of the earlier version releases nothing.
- Turning an image a quarter turn, and every change to an item's gallery and cover or to a Type's own images (adding one, choosing the cover, reordering, removing one), wait for approval too. A new or turned image is kept out of reach until it is approved, and approval shows exactly the reviewed image, with the same one-day limit.
- Converting notes to a log, converting chosen items into log entries, and undoing a tag rename in one step wait for approval as one change, which shows every new log entry or tag it changes. Converting notes into an owner's log that does not exist yet waits as one change too: approval creates the log and its entries together.
- Importing selected Types from a Symbol export waits as one linked change if any destination protects its content. The whole selection waits, including items going into unprotected Types in that same import. Review every item, its links, the Type context and where it will be placed. Invalid rows are listed as not imported, with their reasons; placements you cannot make are listed as omitted. Approval creates exactly the reviewed graph and placements, or nothing. If every item is invalid, nothing is saved for review and no Types or placements are created, even an empty Type in that selection. An export containing only empty Types, with no invalid items, still saves those Types for review. Project share confirmation still applies. Approval does not authorize sharing. Review every item and report page in the browser or the Symbol app before approving. One protected import can contain up to 1,000 items including new Types, with up to 64 MiB of uploaded input. For a larger selection, import unprotected Types separately or select fewer Types. An import with no protected destination works as usual.
- Most changes can cover up to 5,000 items, or 1,000 for a snapshot restore or a selected Symbol import. Split larger edits into smaller changes. For a tag rename, Type deletion or snapshot restore, an owner or Admin can turn protection off for the Type, or in team settings if it is enforced, while making the change. Its review shows items a page at a time. A log with many proposed entries pages those entries inside the log, while still counting as one item. Load every item page and every entry page before approving. Ordinary limits, such as 1,000 notes per Type conversion, still apply.
- Moving or copying items into a team where a protected Type, or a team that protects all its content, would hold them waits for approval. The team's reviewers see each item's whole content as a new item, exactly as it would arrive, and approving it moves or copies it as you. Editing a source item while its move waits makes that move out of date. A copy keeps the content, files and images its reviewers saw, even if you change the original later. Its staged files have the same one-day limit as a new item's files. Leaving the team or losing access to the source before approval releases nothing. Moving items out of a protected Type in your personal workspace into a team waits for your own approval.
- Moving a whole project into a team waits as one change covering every item when a protected Type is involved on either side, and approving it moves the project and all its items together.
- Moving items from a protected Type in your personal workspace into a protected Type of a team, or into a team that protects all its content, needs both sides to approve. The change waits in the team, and nothing else can be proposed for those items meanwhile. You approve moving them out of your Type first, from the change's review page, and then the team's reviewers approve them arriving, which moves them. If the team's reviewers get to it first, they are asked to wait for you. Approving your side moves nothing on its own, and if the change is updated afterwards, you approve it again.
- Copying a whole project into a team creates the team's project at once. Items whose copies a protected Type, or a team that protects all its content, would hold are each saved for approval as their own change, and each copy joins the project once it is approved. The rest are copied straight away.
- Restoring a snapshot restores the rest of your workspace at once. For each protected Type, what differs from the snapshot (edited items, items added or removed since, items moved in or out, and the Type's guidance and fields) is saved for approval as one change, and the Type stays as it is until that change is approved. The restore's result links to it. Protection itself, its opt-out and the changes already decided or waiting are never taken from a snapshot. If a change to one of those items is already waiting, the protected Types are left as they are and nothing is saved for approval; decide the waiting change, then restore again. A Type that is no longer protected but has had changes proposed to it is restored at once, keeping its record of those changes. Restoring a single item from its history waits for approval too.
- A restore whose changes to protected Types include log entries is saved for approval, but it can only be rejected, because the review cannot show the entries' text. One that includes encrypted items is reviewed in the Symbol app, like any encrypted change.
- Removing access, deleting your account and other legally required deletion are not held for approval. They can make content unavailable, but they never put an unapproved version in its place.
- An organization's owner and Admins decide unless it has enrolled an approval service of its own.