Skip to main content
Plans: Pro and Enterprise. Self-hosted: Enterprise license.
A self-hosted open-source server has user accounts only, with no org structure. Nothing on this page applies to it beyond creating users. Nasiko models an organization as 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. Each unit can have one lead, and users can belong to any number of units. Separately, agent grants control which agents a user or unit can reach.

Roles

A user becomes a manager by being appointed lead of a unit, not by setting the role directly. For the full rules, see User and org management.
1

Create users

In the dashboard, open Access control → Users and add a user. On an Enterprise deployment, you can also use the admin CLI:
--role defaults to member. There’s no --password flag. The server returns a one-time access key and secret, and the secret is the user’s first password. Capture it, because it can’t be shown again.With SSO configured, users 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.
2

Build the unit tree

Open Access control → Org structure. An admin creates top-level units. A lead can create units inside the units they lead. Sibling units can’t share a name.With SSO configured, Nasiko can also create units from your directory’s groups and place people in them. See Org placement from your directory.
3

Appoint leads and add members

On Org structure, appoint a lead for each unit and add members. Appointing a lead makes them a manager unless they’re already an admin. Membership counts for every unit above: someone in Engineering > Platform is also reached by anything shared with Engineering.
4

Share agents

Role and unit membership grant no agents by default. Open the agent’s Access tab to share it with users, agents, or org units, or to make it public. From the admin CLI on an Enterprise deployment, you can share with users and agents, or make an agent public:
Grants to org units are made in the dashboard. See User → agent access.

Inspecting

With the admin CLI on an Enterprise deployment:
Admins also get an overview at the top of Org structure: user, admin, unit, and agent counts, plus checks for users in no unit and units without a lead.

API

The same operations are available through the API. See Organization API and Agent grants API. Running several Enterprise deployments? Most nasiko-ee commands accept --deployment <name>, or set a default with nasiko-ee use <name>.