Bosca / System

Security & Identity

Who you are, and what you can do

One identity model under the whole platform: principals sign in, groups carry the permissions, and passkeys, OAuth, and scoped tokens cover every way in.

Principals

The identity behind everything

A principal is the identity you sign in as — not a profile. One principal can own several profiles, with one marked primary, along with its credentials, devices, and API tokens. What it's allowed to do comes from the groups it belongs to.

  • A principal is the sign-in identity, distinct from a profile.
  • One principal, many profiles — one of them primary.
  • It owns the credentials, devices, and tokens.
  • Its permissions come from its group memberships.
principal
identifierada@example.com
profilesAda (primary) · Editor
statusverified
groupsadministrators

Groups & permissions

Permissions go to groups

Access is granted to groups, not to people. A group is a flat set of principals — no nesting, no inherited membership. Actions are explicit, and groups come in two types: principal groups for everyday access, and system groups for platform-level control.

  • Permissions attach to groups; principals join groups.
  • Groups are flat — no nesting or inherited membership.
  • Actions: view, list, edit, delete, manage, execute, impersonate.
  • Principal groups for access, system groups for control.
group · editors
documentsview · list · edit
collectionsview · edit · manage
scriptsview · execute

Sign-in

Every way in

Sign in the way that fits. Passkeys bring passwordless WebAuthn — the private key never leaves the device. OAuth connects Google, Apple, Facebook, or any OpenID provider. And when someone needs to be signed out, you can end every one of their sessions at once.

  • Passkeys: passwordless WebAuthn, keys stay on the device.
  • OAuth and OpenID — Google, Apple, Facebook, or your own.
  • Classic email and password, when you want it.
  • End every one of a principal's sessions at once.

API tokens

Programmatic access, scoped

For scripts, CI, and server-to-server calls, a principal mints an API token — scoped to a subset of its own permissions, never beyond them. Give it an expiry, see when it was last used, and revoke it the moment you need to.

  • Authenticates as one principal, for non-interactive access.
  • Scoped within the principal's permissions — never past them.
  • Set an expiry, or leave it open-ended.
  • See its last use, and revoke it instantly.
api token · ci-deploy
tokenbsk_a1b0c7…
scopescontent:view · content:edit
expiresin 90 days
last used2h ago · 10.0.0.4

Studio Personas

Shape what Studio shows

A Studio Persona is a named set of the Studio areas a profile can open. Give someone the Content Manager persona and Studio shows them the content tools; give an analyst theirs and they land in dashboards and queries. Assign more than one, and they add up.

Content Manager
CMSWork OpsLocalization

Keep exploring

More on System