Invite-driven collaboration
Email-first invites, explicit active-workspace selection, and membership-aware navigation make shared link operations feel intentional.
Teams & securityPlus+, depth varies
Team workspaces with security controls
Invite teammates into shared workspaces, assign built-in roles, review audit trails, and protect dashboard access with TOTP-based 2FA and workspace-level enforcement.
4 roles
Owner · Admin · Member · Viewer
TOTP 2FA
With recovery codes
Audit log
Critical mutations tracked
app.nimriz.com/workspace/team
Team members
2FA enforced
A
Alice Nomura
Owner
2FA ✓
B
Ben Okoro
Admin
2FA ✓
C
Clara Voss
Member
2FA required
D
David Lam
Viewer
2FA ✓
Recent audit log
Ben Okoro added domain go.brand.com
Alice Nomura updated link /launch destination
Clara Voss invited via email
4
Members
4
Roles
3 / 4
2FA
Without a dedicated link workflow
- Configuration, reporting, and follow-up work can spread across multiple tools.
- Teams rely on manual notes or separate dashboards to explain what happened.
- Changing campaign behavior often requires recreating or replacing links.
With Teams & security
- The capability stays attached to the same branded short-link record.
- Operational details are easier to review alongside analytics and related links.
- Teams can keep the public URL stable while improving how the link behaves behind it.
What you 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
Team invites and standard workspace roles start on Plus.
Workspace 2FA enforcement starts on Growth. Audit logs are Professional+. Enterprise includes SSO and custom roles / expanded RBAC.
How it works
1
Invite teammates by email
Send an email invite into your workspace. New members land in the right workspace immediately with the role you assigned - no shared-credential workarounds.
2
Assign a role that fits the job
Owner and admin manage domains, billing, and security settings. Members create and edit links. Viewers see read-only surfaces. Each role has clear capability boundaries.
3
Enforce 2FA at the workspace level
Enable workspace-level 2FA enforcement so all members must have TOTP enrolled before normal access is restored. Recovery codes are generated at enrollment for account recovery.
Everything included
Four built-in roles
Owner, admin, member, and viewer - with capability-aware enforcement across the dashboard and live redirects. Simple until broader RBAC is needed.
Audit trail
Critical actions - link changes, domain verification, membership updates - leave a record for support, compliance, and operational review.
TOTP two-factor authentication
Users enroll in TOTP with recovery codes. Workspace-level 2FA enforcement requires all members to have 2FA enabled before accessing dashboard features.
Workspace-level enforcement
Admins can require 2FA enrollment for all workspace members - with a grace period and remediation flow so members are not hard-locked without a path forward.
Multiple workspace support
Users can belong to multiple workspaces with distinct roles in each. Active workspace selection makes it clear which operational context you are working in.
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; 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.
Related next steps
Ready to try it?
Teams & security is available on supported plans
Create an account to explore Nimriz, then use pricing to choose the plan and setup path that matches this workflow.