docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md
This guide explains how you can effectively organize your infrastructure monitoring using Netdata Cloud.
You can organize your monitoring with two primary concepts that work together.
Spaces serve as your primary collaboration environment where you organize team members and manage access levels, connect nodes for monitoring, and create a unified monitoring environment.
Rooms function as organizational units within Spaces that provide infrastructure-wide dashboards, real-time metrics visualization, focused monitoring views, and flexible node grouping.
Key Relationship: Each node can only belong to one Space, but you can assign a node to multiple Rooms within that Space.
:::tip
You can create multiple Spaces, but we recommend using a single Space for most use cases. All team members in a Space can access its monitoring data based on their assigned roles.
:::
You control what each team member can do in a Space by assigning them a role. The Admin role has full control over the Space, including users, nodes, rooms, and billing. To make someone an Admin, you must already be an Admin yourself — only current Admins can assign the Admin role to others. For the full list of roles and what each one permits, see the role-based access model.
Role changes take effect immediately — the member gains the new permissions right away, with no reload or restart needed.
:::tip
Best Practices for Team Access: Invite all relevant team members (SRE, DevOps, ITOps) and configure role-based access control. Maintain clear permission hierarchies and conduct regular access reviews and updates.
:::
:::info
All nodes automatically appear in the "All nodes" Room. Each Room has independent dashboards and monitoring tools.
:::
| Strategy | Use Case | Examples |
|---|---|---|
| Service-Based Organization | Group nodes by specific services, purpose, location, or infrastructure type | Nginx, MySQL, Pulsar, webserver, database, application, physical location, bare metal, containers, cloud provider |
| End-to-End Application Monitoring | Create Rooms for complete application stacks and service dependencies | Complete SaaS product stacks, internal service dependencies, full application ecosystems including Kubernetes clusters, Docker containers, Proxies, Databases, Web servers, Message brokers |
| Incident Response | Create dedicated Rooms for troubleshooting and problem resolution | Active incident investigation, problem diagnosis, performance troubleshooting, root cause analysis |
Any user with Room access — Admin, Manager, Troubleshooter, or Observer — can leave a Room. Billing users do not have Room access and cannot leave a Room.
Leaving a Room removes your access to that Room's nodes, dashboards, metrics, and functions. It does not delete the Room or affect other members.
Rejoining a Room depends on your role:
For the full permission breakdown, see the Room Management table in the RBAC reference.
Only Admins and Managers can delete a Room. See the Room Management table in the RBAC reference for the full permissions matrix.
:::warning
Deleting a Room is permanent and cannot be undone. The Room and its dashboards are removed.
:::
The nodes in a deleted Room are not deleted — they remain available in the "All nodes" Room and any other Rooms they belong to within the Space.
Steps to delete a Room:
Only users with the Admin role can delete a Space. See the role-based access model for full permission details.
:::warning
Deleting a Space is permanent and cannot be undone. You cannot delete the only Space on your account — each account must have at least one Space.
:::
Steps to delete a Space: