Organization

Organizations make collaboration easier. A user can be member of only one organization. When you create an organization your projects and client applications will be owned by that organization making them available for future members.

Organizational roles

New members are invited by their email address and an organizational role must be assigned beforehand. The chosen role can be changed later. The following table will help you choose from Admin, Modeller, Deployer, Integrator and Guest.

organizational roles
permission Owner Admin Modeller Deployer Integrator Guest
Can create projects
Can list authorized projects
Can create client applications
Can list authorized client applications
Can list web service containers
Can manage web service containers
Can change other members’ organization role
Can invite organization members
Can remove organization members
Can manage organization settings
Can leave organization
Can delete organization

Managing project access in organizations

Projects of organizations cannot be shared with users outside the organization. Organization members’ project access roles differ from the ones available for individual users. The following table explains these project access roles in an organization.

project access roles
permission Master Editor Deployer Viewer None
Can view the project
Can edit the project
Can manage user access
Can manage client application access
Can deploy the project
Can delete the project
Can manage project settings
Can duplicate the project

Organizational roles may implicitly grant access to all the projects. In these cases it’s not required to grant access to projects explicitly. Projects are basically owned by the organization not by a specific members. When a member creates a project he/she is granted access to it with a project access role defined by his/her organizational role. See the table below for details.

implicit project access and project creation access role
Organizational role Project access role granted to all projects Project access role granted to created projects
Owner Master Master
Admin Master Master
Modeller Viewer Editor
Guest None
Deployer Deployer
Integrator None None

For example a member with the Modeller organization role can view every project of the organization. If this member is granted Deployer access for a specific project then his/her permissions on that project will consist of both the Viewer’s and the Deployer’s permissions.

permissions Viewer Deployer Viewer + Deployer
Can view the project
Can edit the project
Can manage user access
Can manage client application access
Can deploy the project
Can delete the project
Can manage project settings
Can duplicate the project

Managing client application access in organizations

The same principles apply to client applications as projects, the access roles differ tough.

client application access roles
permission Master Editor Viewer None
Can view the client
Can edit the client
Can delete the client
Can manage user access
Can manage project access
implicit client app. access and client app. creation access role
Organizational role Project access role granted to all projects Project access role granted to created projects
Owner Master Master
Admin Master Master
Modeller Editor Editor
Guest None
Deployer Deployer
Integrator None None

Joining an organization

Joining as an existing individual user:
  • All owned projects are given to the organization.
  • You will lose access to all projects shared with you.
Joining as a member of another organization:
  • You will leave your current organization losing access to everything.
  • You will join the new organization without transfering anything from your previous one.

Leaving the organization

When you leave an organization you will lose access to all organization owned entities.

The owner of an organization cannot leave until he/she is the last member. As the last member the organization may be deleted. After deleting the organization the owner will keep all entities previously owned by the organization.