Secrets
Your own API keys and other credentials, stored as name/value pairs. Every agent you own gets them as environment variables, and LLM router configs reference them by name. A secret with the same name on an agent’s own Settings tab overrides yours for that agent only. Values are encrypted at rest and masked in the list. You can read back only your own secrets, one at a time, with Show or Copy on each row. Delete removes one after confirmation. With nothing stored, the screen shows No secrets yet. To add a secret, enter a Name (A–Z, 0–9, and _, starting with a letter or _, up to 128 characters — API_KEY style) and a Value, then click Add secret. Adding a secret under an existing name replaces its value. Names that would change how an agent’s container runs are reserved and rejected.
Router configs pick up a changed secret on their next model call. Agents read secrets when they start, so restart or redeploy an agent to apply a change. See managing agent secrets and secret management.
Settings
Settings has a Workspace group of sections, shown only to superusers:
Read-only values are marked Set by the server: they come from the server’s environment variables, so you change them there and restart. See configuration.
Provider API keys aren’t entered on this screen — router configs reference your encrypted secrets. Manage them on the LLM router and Secrets pages. Registry pull credentials are issued by Nasiko per agent and aren’t configured here either.
General and Registry share one form: click Save changes to apply edits from both.
Your personal preferences — Appearance, Password, and Keyboard shortcuts — are under Account settings in the account menu.
Access control
Plans: Pro and Enterprise. Self-hosted: Enterprise license.
admin role and superusers create, deactivate, and delete them through the API.
Access control is for admins and unit leads. Anyone else sees Not available for your role. It has two tabs.
On Nasiko Cloud, it also has an Invites tab. The workspace owner invites people by email there and can revoke an invite that hasn’t been accepted.
Roles are admin, manager, and member. The separate superuser flag passes every role check. See access control.
Org structure
The tree of org units: each unit’s lead, members, and sub-units. A lead manages their unit and everything under it.- Create unit — a name and an optional Parent unit. Admins create top-level units; a lead creates sub-units inside the units they lead.
- Set lead — appointing a member makes them a
manager. Leave it empty to clear the lead. - Add member and Remove — manage a unit’s direct members. Members that come from your directory are marked Managed by the identity provider: remove them from the group there instead.
- Delete unit — members keep their accounts, and grants on the unit stop applying. Deleting a unit with sub-units removes everything beneath it.
Users
Everyone who can sign in, with role, org units, status, last activity, and creation date. Filter by role or status, or search.- Create user — username, email, and optional display name. No password: Nasiko generates a one-time Access key and Access secret. The secret is also their first password and won’t be shown again.
- Edit — profile, status, or a new password. Users who sign in through SSO are managed by the identity provider.
- Change role — a
managercan grant only roles below their own. Changing a role signs the user out everywhere. - Delete — permanently removes the account. A user who owns agents can’t be deleted.
Doing this from the CLI
- User and org management — creating users, org units, and leads
- Managing agent secrets — secrets from the command line
- Access control reference — the full model behind roles, grants, and agent-to-agent access