Teams & security

Shared ownership with security controls

Invite teammates into shared workspaces, assign built-in roles, review audit trails, and protect dashboard access with TOTP-based 2FA.

What teams get
  • Invite teammates into a workspace and keep operational ownership shared instead of relying on one login.
  • Use built-in roles and audited mutations for changes to links, domains, and team membership.
  • Protect dashboard access with TOTP, recovery codes, and workspace-level 2FA enforcement where entitled.
Availability

Available now

Nimriz uses built-in workspace roles: owner, admin, member, and viewer. More granular custom roles are planned.

Invite-driven collaboration

Email-first invites, explicit active-workspace selection, and membership-aware navigation make shared operations feel intentional.

Fixed roles that map to capability checks

The current workspace model stays simple: owner, admin, member, and viewer with capability-aware enforcement across the dashboard and live redirects.

Audit coverage

Critical actions such as link changes, domain verification, and membership updates can be reviewed through an audit trail.

Two-factor posture

Users can enroll in TOTP with recovery codes, and admins can enforce workspace-level compliance on eligible plans.

How a workspace stays accountable

Instead of sharing credentials or running everything through one admin, Nimriz keeps role assignment and critical changes visible.

Invite flow
Owner invites a teammate by email into the existing workspace.
Role posture
Viewer sees read-only surfaces while admins manage operational settings.
Security control
A workspace can require 2FA before normal access is restored.
Audit trail
Link, domain, and team mutations leave a record for support and governance.

What teams get from this

  • Operational ownership stays with the workspace instead of the newest admin or a shared inbox.
  • Security and audit posture apply to real product actions, not just sign-in settings.
  • Workspace-level 2FA enforcement helps protect operational surfaces while preserving remediation flows for members.
  • The current model stays intentionally simple until broader custom-role governance is ready.