Overview
Niro supports multi-tenancy through a recursive organization tree. This makes it well-suited for MSPs and platform teams managing fleets on behalf of multiple customers or internal teams.
Every user is a member of one or more organizations. Every cluster belongs to exactly one organization. A member of a parent organization can see and manage all clusters in that org’s subtree — including child orgs and their clusters.
Organization model
MSP Org (parent)
├── Customer A Org
│ ├── cluster: production-a
│ └── cluster: staging-a
├── Customer B Org
│ └── cluster: production-b
└── cluster: internal-tooling (owned by MSP Org itself)
- A member of Customer A Org sees only
production-a and staging-a
- A member of MSP Org sees all four clusters (through the org subtree)
- Customer A and Customer B members can’t see each other’s clusters
Creating a child organization
Currently, child organizations are created by the platform admin. If you need a multi-org structure for your MSP use case, contact support.
Members and roles
Each organization has members with roles:
| Role | Permissions |
|---|
| Owner | Full access: manage members, billing, settings, and all resources |
| Admin | Manage members and all resources, but not billing |
| Member | Read and write access to clusters and deployments |
| Viewer | Read-only access |
Inviting teammates
Go to Settings → Members and click Invite. Enter the team member’s email address and select their role.
The invitation is sent by email. When the invitee signs up (or logs in to an existing account), they’re added to the organization.
Authentication
Niro uses a self-hosted authentication system (no third-party auth vendor):
- Email + password: sign up with your email and a password.
- GitHub OAuth: sign in with your GitHub account.
Sessions last 24 hours and are refreshed automatically while you’re active.
Password reset
If you’ve forgotten your password, use the Forgot password link on the login page. Niro sends a one-time reset link to your email.
Plans and billing
Each organization is on a plan that controls feature access. See Plans for the full feature matrix.
Plans are managed by the organization Owner in Settings → Billing.
Organization settings
Settings → General:
- Organization name
- Default auto-sync setting for new deployments
Settings → Members:
- Invite and manage team members
Settings → Alerts:
- Configure notification channels (Slack, Discord, PagerDuty, Webhook, Incident.io)
- Set auto-investigation mode
Settings → Billing:
- View current plan
- Upgrade or downgrade
- Plans — feature availability by plan
- Alerts — org-level notification channels
Last modified on June 12, 2026
