Symbol Docs
Features

Organization security

Require a second factor or company sign-in, limit sessions, keys, sharing and networks, and review your workspace's events.

The Security tab in Workspace settings holds every safeguard a workspace can turn on. The owner and Admins manage it. Members see what the workspace asks of them, and why, if it refuses them.

Nothing changes for an existing workspace until someone saves a rule and the owner enforces it. A person's personal workspace and their other workspaces are never affected by one workspace's rules.

Who manages what

SafeguardOwnerAdminMember
Second factor, sessions, keys and apps, sharing and export, eventsChangeChangeSee what applies to them
Company sign-in, email domains, approved networks, retention, enforcementChangeSeeSee what applies to them
Directory tokensMake, rotate, revokeSee, revokeNothing

No safeguard gives the owner or an Admin a member's Private items, the secret of anyone's key, or anything in another workspace. Changing a rule asks you to confirm it is you first.

Reviewing a change before you save it

Each rule shows Review changes before Save. The review says who would be refused at once, who gets a grace period, which keys or apps would stop working, and which share links would be suspended or come back. If someone else saved the settings after you opened them, your save is refused and you reload to see their change. Relaxing a rule emails the owner and every Admin.

Enforcement

A workspace moves through three states, shown under Enforcement:

  • Not enforced: rules are saved but nobody is refused by them.
  • Preparing: the rules apply on the server at once. Symbol closes off what was handed out before: download links still inside their lifetime, cached copies, and copies devices saved. Each open item is listed with when it clears.
  • Enforced: every rule holds on every app, key and device.

Only the owner starts preparation or enforces, and while a second factor is required, only with one of their own. Enforcing waits until every open item clears. A Symbol Bridge that saved the workspace's content must reconnect and confirm it cleared its copy; the owner cannot mark that done for it. The list names each such device and when it last checked in, and the Overview counts the devices still to confirm. Stopping enforcement keeps your saved rules, but nothing is refused until you prepare again, including members you signed out and keys and apps you revoked. Those take effect again when you prepare. It lifts every rule at once, so it emails the owner and every Admin, as relaxing a rule does.

Second factor

Require an authenticator app or a passkey to reach the workspace. Members without one keep access until their grace period ends (0 to 90 days), then are refused until they add one. They see the deadline in the workspace, and you can send a reminder from the member list (at most one a day per member). Someone who joins later gets the full grace period from their first visit.

The owner must have a second factor before the requirement can be turned on.

Company sign-in

Connect your identity provider with OpenID Connect or SAML, then require members to sign in through it.

  1. Save the connection with the addresses the card shows you to give your provider.
  2. Test connection checks the provider's published keys and, for Okta, the read-only service app Symbol uses. Then sign in once through the provider to finish the test.
  3. Turn on Require company sign-in for every member and set the maximum sign-in age.

Requiring it is possible with Okta. Another provider can offer sign-in but cannot be required, because Symbol checks each member's account and assignment in Okta on every request: a suspended, unassigned or missing account is refused at once, and so is every request while Okta cannot be reached.

The freshness window. If your provider refuses someone's sign-in but leaves their account active and assigned, they keep access until their sign-in reaches the maximum age you set. At that age they must sign in through the provider again, and nothing on Symbol's side (activity, a refreshed token, a new key) extends it. Set the age to the longest you accept for that case. If your provider sends sign-out signals (OpenID Connect back-channel logout, Okta Universal Logout or Shared Signals), Symbol ends the affected sign-in when the signal arrives.

Connecting a member's company account

The first time a member signs in through the provider, Symbol asks them to connect the two accounts. They must already be signed in to Symbol, and Symbol names the workspace and the provider and waits for them to choose Connect account. Nothing is connected if they leave the page, and a link someone else sends them cannot connect anything on its own.

What the provider can do afterwards depends on the member's Symbol email:

  • If it is verified and at one of the workspace's verified domains, signing in through the provider also signs them in to Symbol.
  • Otherwise, signing in through the provider never signs them in to Symbol. They sign in to Symbol their usual way (password, Google or passkey), and the company sign-in then meets the workspace's requirement on top of that.

Owner recovery

If your provider is down or misconfigured, the owner can still repair sign-in from the Owner recovery part of the card: stop requiring company sign-in, or turn a connection off. Recovery works even when sign-in refuses the owner, reads no content, and can change nothing else. Every use is listed on the card and emailed to the owner and every Admin.

Email domains

Prove your company owns a domain by publishing the DNS TXT record Symbol shows you, then Check record. A verified domain lets people with an address there find your workspace from Sign in with your company, and you can:

  • choose what happens for people with an address at that domain;
  • only invite people whose address is at a verified domain.

The choices for people at a verified domain take effect once your identity provider has passed its test:

  • Nothing: sign-up and sign-in work as usual.
  • Offer company sign-in: Sign in with your company and the sign-up page offer your identity provider. People can still create a Symbol account.
  • Require company sign-in: Sign in with your company sends people to your identity provider, and Symbol refuses to create a new account at that domain, with a password or with Google. Symbol points them to your company sign-in instead. While this is on, someone at that domain who has no Symbol account cannot create one, so your directory cannot add them either (it needs an existing account). Switch to Offer company sign-in to let new people sign up.

Accounts that already exist are not affected: they sign in as before. To make members sign in through your provider, turn on Require company sign-in for every member under company sign-in.

A domain can be verified by one workspace only. Symbol checks verified domains again regularly, and a domain whose record is gone lapses.

Directory provisioning

Your directory (Okta, Microsoft Entra ID or another SCIM 2.0 client) can add, change and remove members with a token the owner makes here. The token is shown once. A directory can make and remove Admins, but never makes anyone owner or removes the owner. A person the directory removed is not added back by a delayed or repeated request. To let the directory add them again, the owner approves it through the API (POST /api/preview/organizations/{id}/security/directory-reprovision with the person's user id); the directory's next request to add that person, within 7 days, then succeeds. Their earlier sign-ins, keys and grants stay revoked. The Security tab has no button for this yet.

Sessions

  • Sign-in length: how long a sign-in to this workspace lasts before the member signs in again.
  • Idle timeout: how long without activity before the member signs in again. Activity means the member using Symbol; a tab left open that only refreshes itself in the background does not count.

Both apply to this workspace only. Sign out next to a member ends every browser session, key and app sign-in they have in this workspace, on every device at once. It works once the workspace is preparing or enforced. While settings are Not enforced nothing checks them, so the button is off; to cut someone off then, remove them from the workspace.

Personal keys that are not approved as service identities are held to the same two limits, counted from when the key was created. A key that a CI job or script uses stops working once it is older than the sign-in length, unless you approve it as a service identity.

Keys and apps

The card lists every browser sign-in, mobile app, personal key, connected app, Symbol Bridge and command line that has reached the workspace, with who holds it and when it was made, last used and expires. A key approved as a service identity is marked. It never shows a key's secret. Revoke ends it for this workspace only; it keeps working for the person's personal workspace and other workspaces. Like Sign out, it is off while settings are Not enforced.

You can also set:

  • a maximum key age;
  • API access and AI assistant access switches;
  • lists of the connected apps and AI assistant clients allowed.

Service identities (workload exceptions)

A key a script or CI job uses can be approved as a service identity, until a date you choose (the Security tab allows up to a year). Under Service identities, choose a workspace key, or a member's personal key once it has reached the workspace, set how many days, then review and save. It skips the second-factor, company sign-in and session rules, which a workload cannot meet. It is never exempt from the approved networks, the maximum key age or the API switch, and a personal key stops when its holder leaves the workspace. Under any rule, a key Symbol cannot classify is refused.

Sharing and export

  • Maximum share link lifetime: caps new links and shortens existing ones when they are opened. A stricter expiry a link already has is kept.
  • Copies into personal workspaces: allow or stop them.
  • Who can export: by role. An export never includes anyone's Private items.

While a second factor or company sign-in is required, people who are not signed in cannot open the workspace's share links at all. Members can, after the same checks as everywhere else. When both requirements are lifted, links that are still valid under every other rule work again.

Approved networks

List the IPv4 and IPv6 ranges the workspace may be reached from. Once enforced, browsers, keys, connected apps, share links and the Bridge are refused from any other address. Test my address shows the address Symbol sees for you and whether the list admits it, and a save that would lock the owner out is refused.

Events

The Events card lists what happened in the workspace, newest first: content changes, sign-ins, exports, AI access, directory changes, key and session changes, sharing, membership and security settings. Filter by who, kind, action and date, and export the same filter as CSV or JSON lines. Each export file holds up to 2,000 events, and each export is itself recorded as an event. Events name content by an id, never by its title or body, and never show a member's Private item or a secret.

Add a delivery destination (an https address on the public internet) to receive each event, sent within about five minutes. The signing secret is shown once, when you add it. Deliveries are signed, retried, and carry a stable id so a repeat can be recognised. For each destination the card shows whether it is delivering, failing or paused, how many events are waiting, any it gave up on, and when it last delivered. You can:

  • Send test: send a signed test request, with no event in it, and see whether it arrived;
  • Pause and Resume: events wait while it is paused and are sent on resume;
  • Send all again: queue every event again, each under its original delivery id, so a receiver drops the ones it already has;
  • Remove it.

Adding or removing a destination, or sending all events again, asks you to confirm it is you first.

Retention

The owner sets how long archived content, old revisions and events are kept, in days. Admins can see the settings.

  • Archived content: once archived content is older than this, it moves to Recently deleted. Empty keeps it until someone deletes it.
  • Old revisions: how long earlier versions are kept. Empty follows the usual revision history.
  • Events: kept 90 days unless you choose 90 to 3650.

A cleanup runs once a day and applies the current settings, so a change takes effect at the next run.

Data location

The Data location card lists who processes the workspace's data and where. A region is stated where the deployment fixes it; ask us for the others.

What these safeguards do not cover

The Overview card lists what your current settings leave open. Some limits apply to every workspace:

  • Content someone already exported, downloaded, copied elsewhere or pasted into another tool cannot be recalled.
  • A device that stays offline keeps what it saved until it reconnects, when its copy is cleared. A device that never reconnects keeps it.
  • Download links issued before preparation keep working until they expire.
  • With company sign-in, the freshness window above applies to a sign-in your provider refuses without suspending or unassigning the account.

For members

If a workspace refuses you, it says why and what to do: add a second factor, sign in through your company, sign in again, connect from an approved network, or ask an owner or Admin. While a deadline runs, for example the grace period for adding a second factor, it says so and gives the date. In the web app this banner shows on every page while that workspace is the one you have open, and on its Security tab. The same refusal reaches the mobile app, the command line and AI assistants. Your personal workspace and other workspaces keep working.

On this page