Organization
Client organizations, invites, and multi-org users
A client organization is your company's workspace on NodeRings: members, billing, VMs, and access control scoped to your tenant.
When you create an organization, choose Client if you intend to buy compute from marketplace providers. Organization type is permanent: it cannot be changed after creation.
| Type | Purpose |
|---|---|
| Client | Buy and manage VMs from marketplace providers |
| Provider | Sell infrastructure on the marketplace: see Provider Guides |
Client orgs do not require domain verification or NodeRings seller review.
Create a client organization
Open the organization switcher
Click your current org name in the sidebar header.
Create organization
Choose Client (Buys services from providers), enter a name, and submit.
Switch between orgs
If you belong to multiple organizations (for example one client and one provider), use the switcher to change context. Sidebar, VMs, and billing always reflect the active org.
Invites
Invite colleagues to share access to the same fleet and billing.
| Action | Where |
|---|---|
| Send invite | /organization/members?t=invites |
| Accept invite (signed in) | Link in email, or /profile?t=invites |
| Accept invite (new user) | Sign up first, then open the invite link |
Invited users receive roles assigned by the admin who sent the invite. See Access control for roles and permissions.
What clients do not need
Provider-only steps do not apply to client orgs:
- Domain verification
- NodeRings seller / KYC review
- Agents, nodes, IPAM, or preflight
Those belong to Provider Guides.
Orchestration (client org)
Under Orchestration in the sidebar you manage bootstrap and configuration used at VM launch:
| Page | Path | Purpose |
|---|---|---|
| SSH Keys | /organization/ssh-keys | Public keys for SSH auth at launch |
| Environment variables | /organization/environment-variables | Non-secret config referenced as {{ env.KEY }} in profiles |
| Secrets | /organization/secrets | Vault-backed values as {{ secret.KEY }} in profiles |
| Cloud-init user data | /organization/cloudinit-template | Saved #cloud-config profiles (replace provider user-data) |
These resources are scoped to the active client org. They apply when you create a VM: not retroactively on running instances.
Next
- Access control: members, groups, roles
- Settings: org profile
- Get started: first VM checklist