cloudscaleKnowledge Base

There are numerous projects, both in business and private life, that you do not work on alone. You can set up "organizations" for your company, your association, or yourself whenever you want to collaborate on your cloud resources with other people. As a "superuser" in an organization, you can manage its projects, invite "members", and specify for each project which members and/or teams should have read-only or full access.

Every organization member has their own login credentials and can enable two-factor authentication for additional protection. In addition, the traceability of changes in organization and project logs helps meet compliance requirements.

As organizations are each based on a separate framework agreement, they are also suitable for constellations where cloud resources need to be treated separately for accounting purposes.

The key concepts:

Projects: Cloud resources can be grouped in projects, e.g. for separate test and production environments. Access rights – either read only or with permission to make changes – can be defined separately for each project.

Organization: An organization represents a company, a department or any other group of people who work together on cloud resources. Organizations have a separate framework agreement and a separate balance, which makes them suitable for the contractual demarcation of cloud resources from other accounts and/or organizations.

Organization member: Organization members can work on projects of the organization. Irrespective of their rights for individual projects, organization members can – in the same way as employees in a company – see which projects, teams and other members exist within the organization.

External collaborator: Accounts that need to be able to work on one or several projects without having any insight into the organization beyond this can be invited as external collaborators. They will then only see these projects and not the other projects, teams and members of the organization.

Team: To simplify rights management, accounts (i.e. organization members and external collaborators) can be grouped into teams. Access rights for the team automatically apply to all team members.

Team leader: Team leaders can independently add and remove organization members and external collaborators as team members of the relevant team. Team leaders can also make other organization members (but not external collaborators) team leaders within the team and remove this role again.

Superuser: A superuser can manage all aspects of the organization. This includes managing projects, teams and rights as well as inviting and removing organization members and external collaborators.

Partner organization: The superusers of two organizations can agree on a partnership and share projects with the other organization. The superusers in the two partner organizations manage the access rights of their own organization members and external collaborators for the joint projects. As is the case for external collaborators, only the shared projects – and not the other projects, teams and members – of the other organization are visible.

You can find a comprehensive, fictional use case illustrating the collaboration features in the news article Collaboration that Meets Every Need – an Overview.