Organisations
Everything you make belongs to you, or to an organisation you work in. An organisation is a group of people who share apps, machines, volumes and the rest, each with a role that says what they may do. You can be in several, and switch between them.
Make an organisation
Open Organisations and choose New organisation. You are its Owner. Its page has a header with its name, your role and an Organisations menu to switch to another, make a new one or use an invitation. Beside it, its settings are grouped: People (members, teams, invitations), Access (API keys, connected apps, directory sync), Rules, Network and more, depending on what the realm runs.
Under Profile you name it and give it a brand colour, shown wherever you switch to it. Require two-step sign-in makes every member set up a passkey or an authenticator app before they reach their desktop.
Roles
Every member holds exactly one role:
| Role | May |
|---|---|
| Owner | everything, including who is in it and deleting it |
| Admin | run the work: projects, teams, settings; not who is in it |
| Member | work in every project |
| Guest | see only the projects and resources their teams are granted |
Roles lists what each role holds. An organisation always keeps at least one Owner: the last one can’t leave until someone else is made Owner.
Invite someone
- Choose Invite, give their email address and pick a role.
- They get a link by mail, valid for a week. Where the realm can’t send mail, you get a code to pass on instead; they paste it under Organisations › I have an invitation.
- Invitations lists the ones waiting. Revoke makes a link stop working at once.
An invitation is for the address it was sent to. Only the account with that address can join with it, so a forwarded or leaked link lets nobody else in. Someone without an account can make one with that address from the link. On a realm that is closed to new accounts, only people who already have an account can join through an organisation’s invitation; the link says to ask an administrator.
You can’t invite someone to a role with more rights than you have yourself, and an invitation stops working if its sender loses the right to give that role.
Teams and guests
Teams group members, and a team’s grants say what it may reach: a project or a single resource, with View (see it, change nothing) or Manage (work in it as a member would). A team inside another gets everything the outer team is granted.
Guests are how you bring in someone from outside, such as a contractor: make them a Guest, put them in a team and grant the team one project. They see that project and nothing else.
Projects
Inside an organisation, and in your own space, resources sit in projects: groups you make, rename, move and delete as a whole. Everything starts in Default. The Cockpit draws each project as a frame around its resources; drag a resource into another frame to move it. See Owners, projects and roles.
Leave or remove
- Leave takes away everything your role there let you do. Someone who may add members can let you back in.
- Change role and Remove on a member act at once.
- Delete the organisation only once nothing lives in it any more: no apps, machines, volumes or keys. Its roles, teams, projects and invitations go with it.
From your company directory
An organisation can let Entra ID or Okta add, update and remove its members, with their groups mapped to roles: Directory sync.