Overview
Security is where you decide who can touch your workspace and how they get in. It lives under Security in the panel sidebar, and it groups everything about people, credentials, and access into one place: the members you invite, the API tokens scripts use, the registry logins your Apps pull from, the SSH keys that log you into servers, and a running record of what happened.
Everything here is scoped to your workspace. A key you upload, a token you mint, or a member you invite applies to that workspace and the resources inside it, not to your whole account.
The Security submenu
Open Security in the sidebar and you get five pages. Here is what each one is for.
Where Security sits in the sidebar
The Security section is near the bottom of the panel sidebar. Selecting it opens the submenu above.
| Page | Route | What it holds |
|---|---|---|
| Audit Logs | /audit-logs | A history of actions in the workspace. |
| Access Control | /acl | Members and their access level. |
| Tokens | /tokens | API tokens for scripts and tools. |
| Registries | /apps/credentials | Private image registry logins. |
| SSH Keys | /ssh | Public keys for server login. |
Audit Logs
The Audit Logs page keeps a record of actions taken in your workspace. When you need to know who invited a member, who created a token, or when a resource changed, this is where you look. Treat it as your read-only history: it does not change anything, it just shows you what already happened.
Where to start
If you are setting up access for a team, begin with Access Control and invite your first member. If you are wiring up a script or an integration, start with Tokens. If you are deploying software that lives in a private registry, you need Registries.