Skip to content

Organizations

Everything in NubeStack Cloud belongs to an organization: your company, team or institution. An organization has people, service accounts for automation, and projects, which hold the resources. Each project runs in one location.

How an organization is organized The organization Acme has members, service accounts and projects. Its members are Ayesha, the owner, Bilal, an admin, Sara, a member, and Hina, with the billing role. It has one service account, automation-prod. It has two projects: web-shop, in Karachi, which holds instances, networks, volumes, load balancers, certificates and more; and analytics, in Islamabad. Acme Organization Members People, each with an organization role A Ayesha Owner B Bilal Admin S Sara Member H Hina Billing Service accounts For automation automation-prod Projects Hold the resources web-shop Karachi Instances Networks Volumes Load balancers Certificates … analytics Islamabad
The organization Acme: four people with their organization roles, a service account for automation, and two projects, web-shop in Karachi and analytics in Islamabad.

Two kinds of role

Organization roles decide what someone may do across the organization: invite people, create projects, see usage, change settings.

Role In short
Owner Everything, including security settings, closing the organization and acting on other owners
Admin People (except owners), projects, quota, settings and service accounts
Billing Usage, cost explorer, statements and prices; sees the people and the roles
Member Works only in the projects they have a role on
Viewer Sees every project's resources, read-only

Project roles decide what someone may do inside one project.

Role In short
Project admin Uses the project, gives and takes access to it, deletes it
Project member Creates, changes and deletes the project's resources
Project reader Sees the project's resources, changes nothing

An organization role never gives a project role. An owner manages access to every project, but creates instances in one only with a project role on it. Whoever creates a project becomes its project admin.

Owners, admins and the billing role also see the Organization scope in the console; members and viewers work in their projects only. See The console.

When the built-in roles do not fit, owners and admins can make custom roles. The full table of who may do what is in Roles and permissions.

Several organizations

One account can belong to several organizations. Each is separate: its own projects, people, quota and usage. Switch with the organization selector at the top left of the console; it is there only when you belong to more than one.

Next