AutoMaxSecurity
Secrets, API tokens, roles across organizations and workspaces, sessions, and what agents may touch.
Where secrets are allowed to live, how free scoped API tokens work, how platform, organization and workspace roles combine, and the boundaries agents cannot cross.
Secrets
- YAML holds
${VAR}references; a literal secret fails validation. .envfiles are parsed into a private map, never intoprocess.env.- Integrations and MCP servers store variable names only.
- Logs, HAR files and screenshots are redacted or masked by key pattern and
maskselectors.
API tokens
Tokens are free, unlimited, scoped and revocable. Format amx_ plus 40 characters; stored as SHA-256; shown once.
bun run automax tokens create --user ci --name ingest --scopes runs:ingest,runs:read --expires 90d
bun run automax tokens list
bun run automax tokens revoke <id>A token's scopes must be a subset of its owner's role, at creation and at use.
Roles
The effective role inside a workspace is the higher of the explicit workspace membership and the role implied by organization membership; platform admins are admin everywhere.
| Scope group | viewer | editor | admin |
|---|---|---|---|
*:read, artifacts:read | ✔ | ✔ | ✔ |
runs:write, runs:ingest, features:write, datasets:write, envs:write, schedules:write, processes:write, agents:* | ✔ | ✔ | |
users:admin, orgs:admin, workspaces:write, integrations:write, audit:read | ✔ |
Sessions
HttpOnly, SameSite=Lax cookies with sliding seven-day expiry; every non-GET request carries a CSRF header; login is rate-limited.
Agents
Agents can read the project, run scenarios and drive a browser. Their only write path is a proposal directory. Nothing reaches main without a person accepting it.