Skip to main content
Plans: Pro and Enterprise. Self-hosted: Enterprise license.
Admins and unit leads manage people in the dashboard under Access control, which has the Org structure and Users tabs. A Nasiko Cloud Pro workspace also has Invites. Account creation is also available in the Organization API, and on Enterprise deployments in the admin CLI (nasiko-ee), which also handles account recovery. A self-hosted open-source server has user accounts only: users with the admin role and superusers create, deactivate, and delete them through /api/users, and there’s no org structure or manager role.

Creating a user

In the dashboard, open Access control → Users and add a user. On an Enterprise deployment, you can also use the admin CLI:
No password is set. Nasiko returns a one-time key pair:
access_secret is shown once and is the user’s first password. There’s no way to read it again. If it’s lost, issue new credentials with nasiko-ee admin user-reset-creds <user-id>.
--role defaults to member. Pass --role admin to create an admin. Add --superuser for superuser privileges, which are separate from the role. See Role vs. superuser. Users who sign in through SSO are created on their first sign-in, or ahead of time by SCIM. On a Nasiko Cloud Pro workspace, people join by invite. The workspace owner invites them by email from Access control → Invites, and an accepted invite makes the person a user of the workspace. Deactivate or delete users later:
On Nasiko Cloud, a person you delete from a workspace loses their place in it. The next time they sign in to app.nasiko.com, they land in Nasiko Free. A person you deactivate also lands in Nasiko Free, but keeps their place in your workspace, so you can reactivate them. All user commands: Admin CLI.

Roles

Change a user’s role on Access control → Users. Two rules apply:
  • A manager can grant only roles below their own and can change only users below their own rank. An admin can change anyone’s role except their own, and can’t demote the last admin.
  • Changing a user’s role signs them out of every session, so the new role applies at once.
Demoting a manager to member also removes them as lead of any unit they led.

Org units and leads

The org structure is a tree of org units. A unit can sit at the top level or inside another unit, as deep as you need. A department with teams is a top-level unit with child units. A user can belong to any number of units. Membership in a unit counts for every unit above it: an agent shared with Engineering reaches everyone in Engineering > Platform. Each unit can have one lead. Appointing a lead makes them a manager, unless they’re already an admin. Replacing or clearing a lead returns the previous lead to member if they no longer lead any unit. A lead manages their unit and every unit beneath it, whether or not they’re also a member of it. On Access control → Org structure: Sibling units can’t share a name.

Units from your identity provider

With SSO configured, Nasiko creates units from your directory’s groups and places people in them. Those memberships follow the directory. You can’t remove someone from a directory-synced unit in Nasiko, because the next sync would restore it. Remove them from the group in your identity provider instead. Units and memberships you add by hand are never changed by a sync.

What admins see

Admins get an overview at the top of Org structure: counts of users, admins, units, and agents, and three checks:
  • Users in no unit. Grants on units never reach them. Use Assign to place them.
  • Top-level units without a lead. Only an admin can manage them.
  • Units with no direct members.
A user who signs in with no placement sees an “awaiting assignment” screen until someone places them.

Role vs. superuser

They’re checked separately. role: admin doesn’t grant superuser. Set superuser with --superuser at creation.

Next