Skip to content

Security

Isolated by company, denied by default

Nidus is multi-tenant from the ground up. Each company's data stays inside that company, access starts at zero, and the changes that matter leave an audit trail.

Tenancy

Every company is its own space

Tenant isolation

The company comes from the signed-in user, never from the request. Other companies' records are simply not found.

Your own subdomain

Each company signs in at its own address, such as acme.nidus.sh, branded with its own name, logo, and colors.

One company per person

A person belongs to one company. The same email in two companies is two separate accounts.

Sign-in

Email and password by default, Entra when you want it

Sign-in options

  • Email and password for every company, with a 12 to 128 character policy
  • Throttled failures: repeated wrong passwords add a growing wait
  • Two-step verification with an authenticator app and recovery codes, or a passkey
  • Session control: see every signed-in device and end any of them; a password change ends the rest
  • Email links for invites and password resets, plus a notice when security settings change
  • Microsoft Entra SSO as a paid add-on, with roles from security groups
  • Owner recovery with a password and authenticator app as a break-glass path
  • New owners get an emailed invite link and choose their own password
See the SSO add-on

Access

Least privilege, out of the box

Deny by default

No role means no access. A blocked user sees why, and nothing else.

Five roles

Admin, Manager, Tech, Inventory, and Viewer, each with a fixed permission set.

Location scopes

Limit a person to a site and everything under it. Out-of-scope records are hidden and out-of-scope changes are refused.

Session revocation

A password change or an admin reset ends sessions right away, not when a token expires.

Audit trail

Changes record the actor, the time, and the values before and after.

Write-only secrets

Integration keys cannot be read back after saving. Admin screens show only the last four characters.

Safeguards

People stay in control of the record

Human approval

Discovery tools suggest. A person approves new assets and stock adjustments.

Soft archive

Assets are archived rather than deleted by default, so history and custody survive.

Recovery checks

Admins can review a recovery posture snapshot for their company.

Questions

Security FAQ

Can one company see another company's data?

No. Every record belongs to one company, and every query loads the company from the signed-in user. A record from another company returns the same not-found error as one that does not exist.

How are passwords stored?

As salted PBKDF2 hashes, scoped to one company. Passwords must be 12 to 128 characters, and repeated failed sign-ins are slowed down.

Do you support two-step verification and passkeys?

Yes. Anyone can turn on two-step verification with an authenticator app and ten recovery codes, or add a passkey, from their profile. They can also see their signed-in sessions and end any of them.

What if our single sign-on breaks?

The company owner can enroll a break-glass recovery sign-in that uses a password plus an authenticator app, and still works when Microsoft sign-in does not.

Built by IT, for IT

Have a security questionnaire?

Send it over. We will answer it directly and tell you plainly where Nidus stands today.