Permissions reference

Who can do what in the Context platform: people, agents, applets and administrative operators.

How authorization works

Roles are assigned to a principal at a scope (the organization, a workspace or an individual resource) and apply to the resources below it. The Context application tier resolves the principal’s roles and decides every request, including requests from agent sandboxes (see Sandbox network paths).

Findings marked * are caused by configuration or environment and can be resolved without a product change (see Known issues and hardening).

The permissions reference has these parts:

Page	What it covers
This page	Principals; organization, workspace and resource roles
Roles matrix	What each role can do
Agents and approvals	How an agent’s permissions are computed, who can run it, policy presets and approvals
Administrator access and audit	Who can read private data; administration and audit capabilities
Sign-up and accounts	Where a new account is placed

For the admin-facing summary of default permissions by role, see Roles.

Principals

flowchart LR
  subgraph P["Principals"]
    person["Person<br/>organization, workspace and resource roles"]
    agent["Agent<br/>member by default; adds its owner's file access"]
    applet["Applet<br/>bound folders and secrets"]
    device["Paired device<br/>no access of its own"]
    setup["Setup operator<br/>sign-in, models and features"]
    super["Platform superadmin<br/>bypasses authorization; audited"]
  end
  subgraph S["Scopes"]
    org["Organization<br/>owner · admin · member"]
    ws["Workspace<br/>viewer · member · admin · owner"]
    pws["Personal workspace<br/>private; created at onboarding"]
    res["Resources (organization, workspace or personal)<br/>drive folders and files, tasks, agents,<br/>skills, connectors, applets and secrets"]
    pd["Private drive<br/>the user, their own agents (read only), explicit shares"]
  end
  org --> ws --> res
  org --> pws
  org -.->|"Organization admins: standing access to every workspace (P-03) *"| ws

Roles assigned at a scope apply to the resources below it.

Principal	Description	Holds
Person	A user who signs in to the platform	An organization role, workspace roles and resource roles
Agent	An agent identity in the platform (not a Kubernetes ServiceAccount). Each person has a personal assistant, created at onboarding or when they join; organization admins can create further agents.	An organization role (member by default), workspace memberships and resource grants. For files, it also uses its owner’s permissions; for connectors and skill edits, the permissions of the person who started the task (see Agents).
Applet	A small application built on the platform	Folders bound to it, its own storage and vector store, and secrets bound to it, which it uses only through the application tier
Paired device	A user’s machine running Context Code	No access of its own; it claims and reports work for its user
Setup operator	Holder of the deployment’s setup password	Control of sign-in methods, models and feature settings; no role inside organizations
Platform superadmin	An account listed as a platform operator	Bypasses authorization; each use is recorded in the application audit log

Organization roles

Role	Rights
Owner	All organization rights, including managing owners, billing, security policy, deleting and transferring the organization
Admin	All organization rights except those reserved to owners, plus standing access to every workspace and resource in organization or workspace scope (see Administrator access)
Member	Read the organization; create workspaces; manage and publish skills and applets; create agents and use evaluations, each subject to organization settings

Organization settings can withdraw member rights. Platform defaults: creating workspaces is allowed for owners, admins and members; creating agents and using evaluations for owners and admins. The roles matrix uses the defaults.

Workspace roles

Role	Rights in the workspace
Viewer	Read content
Member	Read and write content; run tasks
Admin	As member, plus share content, manage members and settings
Owner	As admin, plus permanently delete content

Resource roles

Resource	Roles
Drive folders and files	viewer, user (read and write), admin (adds sharing), owner (adds permanent deletion)
Tasks	viewer, editor (through an edit link), owner (the task’s creator)
Agents	viewer, operator (run), admin (configure), owner
Skills	user, editor, admin, owner
Connectors	roles on connector definitions and on connector instances
Applets	viewer, user, admin, owner
Secrets	reader, owner