Tenants and users
Tenants
A tenant is an isolated inventory with its own users, integrations and settings. Create and manage them from System management → Tenants.
A tenant has a name, a logo used in the console chrome, and an id that appears in
every console URL scoped to it (/t/<tenantId>/…).
Removing a tenant removes its asset inventory, scan history and reports. There is no undo from the console.
Users
Users are managed from System management → Users. A user account is deployment-wide; access to individual tenants is granted through roles.
Inviting a user
- Users → Invite user.
- Enter the email address.
- Assign roles — global, per-tenant, or both.
- Send. The user receives an invitation email and sets their own password when they accept.
Invitations let the user set their own credentials, so no one has to transmit a password. Prefer them to creating an account with a password you then have to share.
Account state
An account can be enabled or disabled. Disabling revokes access immediately while preserving the account and its history — the right move when someone leaves, in preference to deletion.
Security enforcement
Per user, an administrator can require:
- MFA enrolment — the user must set up an authenticator before continuing.
- Password change — the user must choose a new password at next sign-in.
Enforcing MFA on one account does not enforce it deployment-wide. For a blanket requirement, apply it to every account, and to each new one as it is created.
Profile
Users manage their own name, avatar, password and MFA enrolment under Profile — no administrator involvement needed.
Document deployment-level settings (branding, session lifetime, password policy) and where they live in System management.