@admin

Features

The 22 features the admin package declares, in two tiers: project.* inside a project, platform.* across projects.

Every admin route names the feature it requires, and the server checks it against the caller's real grants before the handler runs (the mechanism is on package-system Features). The Admin widget hides a tab the caller cannot use, but hiding is presentation; the server check is the gate. The routes each feature reaches are listed on Routes.

Project tier

A project.* feature acts inside the caller's current project.

FeatureGrants
project.dashboardThe Admin widget itself, dashboard stats, usage charts, health, package and stream lists, and the projects the caller belongs to
project.membersThis project's member and role inventory, and the exact-email lookup for adding an existing user
project.members.inviteInviting a new user into this project and issuing, listing and revoking one-time invite links. The role's invite flag is also required, and the assigned role may not be stronger than the caller's
project.agents.assignAssigning or unassigning a project agent to a member — who may manage it; who may use it is the Agents tab's attach. The role's role-management flag is also required
project.auditThe project-scoped logs: a project-installed package's log and the per-agent run logs
project.rolesReading this project's role map. Rewriting it also needs the role-management flag, which is a role property, not a grantable feature
project.sourcesThis project's source configurations, with live health, and their permission and sync edits
project.limitsThis project's spend-limit rules, including other members' per-user caps. Your own cap is always visible; editing limits needs the role-management flag
project.credentialsThe credential catalog at your own scope: ids and whether a value is set, never values
project.credentials.writeSetting or deleting a credential value at your own scope
project.canvasThe organization canvas and its per-member and per-agent detail
packages.manageThe project's packages (trust, build, the feature that gates one, withheld tools), cache clear and rescan. The host re-checks the live package-management grant on every call

Platform tier

A platform.* feature crosses the project boundary. None of them is granted to any role by default; an owner grants them explicitly.

FeatureGrants
platform.projectsProjects you are not a member of: the cross-project list, platform-scope usage and the per-project grouping
platform.usersPlatform-wide user records and cross-user spend, acting on a user in no project, deleting a user (with authority over them in every project), and the platform Devices tab
platform.scopeActing on a scope outside your session: another project, member or agent, or the platform-wide credential scope, and only on principals inside your own projects
platform.auditEvery platform-global log: the audit log, the route log and the native packages' own logs. None of them carries a project id
platform.configPlatform settings, the custom endpoint lists, the host CLI import, and the release line with its notification
platform.vectorVector store status, collections and the active embedding model
platform.vector.resetThe destructive, platform-wide vector reset
platform.packagesEvery package the host knows, and asking for one to be installed, updated or removed while the host runs
platform.packages.approveApproving a package request and restarting the host to apply it. What it installs runs inside the host on every project, so approving is held apart from asking
platform.projects.createReaching project creation. Creating a project also needs owner strength (priority 1 in an existing project), so this feature alone is never enough

Default grants

RoleDefault admin grants
ownerevery feature
adminevery project-tier feature above
manager, member, viewerproject.dashboard

Two features named by admin routes belong to other packages: core.agents (agent-core, granted to every role) gates the Agents tab's delete, whose real authority stays agent-core's per-agent check; platform.vector.maintain (brain-core, no default grant) gates the embedding-model rebuild.

Escalation inside one route

Some routes serve a project answer to a baseline caller and a wider answer to a caller who holds the matching platform feature:

  • the usage series needs platform.projects for the platform scope and platform.users for per-user grouping, and the Codex savings card at platform scope needs both;
  • dashboard stats fill the platform user and project counts only for holders of platform.users and platform.projects, and read 0 otherwise;
  • a project you do not belong to answers 404 unless you hold platform.projects;
  • in a project record, other members' emails, other roles' grant lists and other members' spend caps each appear only for holders of project.members, project.roles and project.limits;
  • a log source rooted in the platform zone needs platform.audit and is not even listed without it.

A missing escalation feature drops the field or answers 403; it never widens the answer.

On this page