Skip to content
Browse the docs

Getting started

Roles and permissions

What each Nidus role can do, how location scope limits someone to their own sites, and why parts of the menu can differ from one person to the next.

The five roles

Access is deny-by-default: you can do only what your roles allow. An admin gives roles on Administration → Users, or maps them to Entra groups when the company uses Microsoft sign-in.

RoleWhat it is for
AdminEverything, including users, sign-in, integrations, branding, features, and the audit log.
ManagerAssets, custody, stock, discovery approval, reports, and approving mileage and time. Cannot change sign-in settings.
TechLook up, create, edit, and assign assets; read stock; link support tickets; work on projects.
InventoryReceive, issue, transfer, and count stock. Reads assets.
ViewerRead-only access to assets, stock, people, support, and reports.

Everyone can sign their own receipts and acknowledgments, and log their own mileage and time when those modules are on.

Location scope

An admin can limit a person to some locations on Administration → Users → person → Locations. They then see and change only the assets and stock in those locations and every location under them. With no locations ticked, they work everywhere.

  • An asset with no location is outside every scope.
  • Company-wide pages (Reports, Budgets, Exports, CSV import) are hidden for scoped people.
  • Moving something into or out of a scoped site needs someone who is not scoped.
  • Admins are never scoped.

Why my menu looks different

Your company turns optional modules on and off on Administration → Features. If a page such as Inventory, Projects, or Mileage is missing, either the module is off or your role does not include it. Ask your admin.

Built by IT, for IT

Need a hand?

Ask your company's Nidus admin about roles and modules. For anything else, or to bring Nidus to your team, get in touch.