Organizations

Are You Organized?

An Organization helps you, for lack of a better term, organize your Tuono-related assets.

Credentials

Credentials are added at the Organization layer and can be used by any user within the Organization. Credentials can only be added and removed by organization owners.

Organization, Teams and Users

The Organization is the top-level of the hierarchy for the Tuono solution. An Organization can have n number of Teams and n number of users within the Organization and users can be members of n Teams.

In this example you can see that:

• User 1 in a member of Team 1

• Users 3 and 4 are members of Team 2

• Users 5 and 6 are not members of any team

• User 2 is a member of both Team 1 and Team 2

User permissions over Environments or Blueprints can be explicitly granted at the user-lever, or or they can be inherited from the Team permissions.

Environment and Blueprints

Environments and Blueprints are created at the Organization layer, but user access to these objects is seperately controlled via Role-Based Access control, either through the users own permissions, or permissions inherited by being part of a Team.

In this example you can see that:

• User 1 has access to Environments 1 and 2 and Blueprints 1 and 2 inherited by being a member of a team

• User 5 has explicit permissions over Environment 2 and Blueprint 2 only

Roles

There are four roles that can be applied to either Users or Teams:

• Owner

• Collaborator

• Observer

• No Permissions

For more details on this, please take a look at Role-Based Access Control.