Users and permissions
Assign roles and workspace access according to each person's responsibilities.
Account roles
Each Panel account has one system role. Workspace membership is assigned separately.
| Role | Scope |
|---|---|
| Super administrator | Manages the platform and user roles, including administrator accounts |
| Administrator | Manages infrastructure and ordinary users; cannot grant or modify administrator accounts |
| User | Accesses assigned workspaces; registration and SSO create this role |
Registry and Panel use separate accounts.
Workspace access
Administrators assign workspace members as viewers or operators. Platform administrators have administrative access to workspaces.
| Access | Permitted actions |
|---|---|
| Viewer | Read workspace information and Console output; read and download files |
| Operator | Viewer access plus file changes, interactive Shell sessions, service controls, variables, Secrets, automation, and start-command changes |
| Platform administrator | Operator access plus workspace creation/deletion, membership, name, image, resource limits, network settings, and runtime user identity |
The same permissions apply to AI, automation, and plugins; approvals cannot expand them. Operators may change the start command, while administrators manage other deployment settings.
External plugin members
Integrations such as the QQ bot can bind a group or private chat to a Workspace conversation. The binding owner confirms the source and members in Panel. External members run tasks through the binding account, limited by both their assigned member role and that account's current Workspace permissions. Joining does not create a separate Panel account.
Member roles are administrator, operator, or viewer and apply only to the bound Workspace; they do not grant platform or binding management. The binding owner's access cannot be edited here. Members without an assigned role inherit the binding account's permissions.
Add only trusted members. The task's requester and the binding's external owner can answer its questions or handle permitted approvals. Complete approvals in Panel when a passkey or authenticator app is required. Pausing or removing a binding, removing a member, or changing a member's role cancels the related queued work and requests cancellation of relevant active tasks. Completed changes need separate handling.
The binding account's personal memory may appear in external replies, so use a dedicated account. See Use plugins for setup and Plugin security for permission boundaries.
Review access
- Grant administrative roles only to operators who need them.
- Review active sessions, passkeys, authenticator apps, SSO identities, and API keys regularly.
- Disable or revoke access when a user or integration no longer needs it.
Review active operations and schedules when removing access. Revoking an API key blocks subsequent requests and terminal commands; already accepted operations and user-owned schedules use their normal stop controls.
Browser sessions and API keys
API keys let external programs perform supported Workspace operations, such as managing files, terminals, services, and non-AI schedules. They use the account's current permissions and stop working when revoked, expired, or the account is disabled.
AI conversations, memory, approvals, account security, and administration require a browser login. API keys cannot create, edit, enable, or start AI schedules. See Panel's /api/docs for supported routes and connection details. Turning off additional verification does not expand API-key access.
Set additional verification
Administrators can enable identity verification separately for administration and critical-risk operations in Site Settings → Access control. Both are off by default. When enabled, affected actions ask for a passkey or authenticator app; follow the prompt on the current page. Account-security actions retain their own verification requirements.
AI writes or deletions of Workspace Secrets require manual confirmation in every approval mode. Reading a Secret shows its name and other details, not the saved value. See AI assistant.