nasiko-ee) or the equivalent API routes.
Creating a user
--role defaults to member. Place the user at creation time:
--superuser for superuser privileges (separate from --role — see below).
Move or remove users later:
Role vs. superuser
They’re checked separately everywhere.
role: admin does not grant superuser. Set it with --superuser at creation, or on the Users page afterward.
Departments and teams
A department contains teams; a team belongs to exactly one department. Creating, updating, or deleting either requires superuser.--manager or --lead does not change that user’s role. Bump it separately if they need the matching permission tier.
Single sign-on and automatic placement
Nasiko supports OIDC SSO with any standards-compliant provider. See SSO setup. Group-to-role mapping works with any OIDC provider that emits a group claim. Map an external group to an internal role, team, and/or department; it applies on sign-in. A user matching several mappings gets the highest-ranked role’s mapping applied in full — rows are not merged field by field. A user matching none keeps their current role, so manual promotions are never reset. Directory sync pre-provisions your whole hierarchy before anyone logs in. It requires Microsoft Graph and is Entra ID only.A user who signs in via SSO with no mapping or sync record lands as a plain
member with no team or department. An admin promotes and places them afterward.Next
- Access control overview — roles and permission tiers
- User → agent access — granting access to specific agents
- Secret management
