Organizations
An organization is the boundary everything in AstroPulse lives in: clusters, cloud accounts, applications, models, add-ons, integrations, API keys, service accounts, notifications, the audit log and the plan. Nothing crosses from one organization to another. A person can belong to several, and works in one at a time.
Your default organization and team organizations
- Default organization. Everyone gets one at first sign-in, with themselves as owner. It is a personal space to try things: no one else can be added to it, and its billing is not an organization's.
- Team organizations. An organization people share, each with their own role. Team organizations are an Enterprise feature: creating one needs both the Enterprise plan and the account Admin role.
| Plan | Organizations | Members and the Admin role |
|---|---|---|
| Developer | 1, your default organization | No |
| Enterprise (default) | 5 | Yes |
Every Enterprise value is a default that can be changed for your organization: contact AstroPulse.
Your account roles are under Organization settings › Profile, in Roles.
In the console
-
Organization settings open from the account menu: select your name at the bottom of the sidebar, then Organization settings.
Open zoom view Select Organizations. Each organization you belong to is listed with its Owner, Your role, Plan, what is Enabled for it, and when it was Created.
Open zoom view -
To work in another organization, pick it in the switcher at the top of the sidebar. Every page, key and command then acts in that organization.
-
To create a team organization, select Create Organization, enter its name, and select Create Organization in Create New Organization. You become its owner.
Open zoom view
You should see
The new organization in the list with Your role Owner, and in the switcher. It starts empty: connect a cloud account or bring a cluster, then add members.
How organizations keep work apart
- Every request is scoped to one organization: the one in the switcher, the active one in
astroctl, or the one a key was created in. A key from one organization is refused in another. - Cloud accounts, clusters and integrations belong to one organization and are used only for its work.
- Each organization has its own audit log of who did what.
Other ways in
- API: the organizations calls in the API reference.
With astroctl
astroctl org list
astroctl org use my-team
astroctl org create my-team
org use sets the organization every later command acts in. Every flag: astroctl organization.