Skip to content

Access Control

Rebyte enforces access control at multiple layers. Each layer is independently configured and enforced.

Two roles managed via Clerk:

RoleScope
AdminFull org control — network policies, security policies, agent policies, BYOK keys, system prompt, API keys, channels
MemberCreate workspaces, run tasks, use configured resources. Cannot modify org-level settings.

Each Agent Computer (workspace) has a visibility level and per-user access grants.

LevelWho can access
privateCreator and explicitly granted users only
shared (default)All org members — read and write
publicAnyone can view. Org members can edit.
LevelCan do
OwnerFull control. Delete workspace. Automatically assigned to creator.
EditorRead/write files, run tasks, configure settings. Granted to ACL members and org members (if shared/public).
ViewerRead-only. Only applies to public workspaces for non-org users.
  1. Is the user the workspace creator? → owner
  2. Is the user in the workspace ACL? → editor
  3. Is the user in the same org AND visibility is shared or public? → editor
  4. Is visibility public? → viewer
  5. Otherwise → denied

Grant per-user access via the workspace members/ACL settings.

Team skills use a creator-based permission model.

ActionWho
Create skillAny org member
View/download skillPublic visibility: anyone in org. Private: creator or ACL-granted users.
Update metadataAny org member
Delete skillAny org member
Change visibilityCreator only
Manage skill ACLCreator only
Rollback versionCreator only
View ACLAny org member

Skills support two visibility levels: private and public (within the org). The creator controls visibility, ACL grants, and version rollback.

Context Lake (data source connections) uses admin-gated creation with creator-managed ACL.

ActionWho
Create dataset/viewOrg admin only
List datasets/viewsAny org member
Query dataset/viewCreator, ACL-granted users, org admin, or any org member if visibility is shared or public
Manage dataset/view ACLCreator only
View ACLCreator or org admin

Each dataset and view has its own ACL and visibility setting. Shared/public datasets are queryable by all org members. Private datasets require explicit ACL grants. ACL entries include a granted_by audit trail.

Admins control platform-wide policies through Settings.

Per-executor controls:

SettingEffect
enabledEnable/disable an executor (Claude, Gemini, Codex, OpenCode) for the entire org
authMethodForce api_key (BYOK) or credits mode per executor
disabledModelsBlock specific models from being used

See Agent Shield for details. Network policy settings can currently be modified by any org member.

SettingDefault
Domain allowlist modepackage_managers_only
Additional allowed domainsNone
SettingDefaultEffect
Shield monitoringoptionalrequired enforces Shield on all computers; optional allows per-workspace opt-in

Per-workspace override: workspace editors can enable/disable Shield monitoring on individual workspaces when the org policy is optional.

Admins can set a custom system prompt applied to all agent executions in the org. Requires Team subscription.

API keys have granular scopes controlling what operations they can perform:

ScopePermission
tasks:readList and view tasks
tasks:writeCreate tasks, send follow-ups, delete
files:readView file metadata
files:writeUpload files
webhooks:readList webhooks, view public key
webhooks:writeCreate and delete webhooks

All scopes are granted by default on key creation. Granular scope selection is planned.

LayerControlled byGranularity
Org settings & policiesOrg adminOrg-wide
Agent Computer accessCreator + ACLPer-workspace, per-user
Skills accessCreator + ACLPer-skill, per-user
Context Lake accessAdmin (create) + Creator (ACL)Per-dataset/view, per-user
API key scopesOrg adminPer-key
Network egressOrg adminOrg-wide (via Agent Shield)