This document provides information on project rooms, project room management, workspaces and workspace management. Additionally, it explains the basic application of this approach in solution life cycle, and what limited workspaces are. The following scheme shows how project rooms and workspaces stand in solution hierarchy.
A client’s enclosed environment is called a project room. Each client can have multiple project rooms. Each one includes members, developer teams, and workspaces:
- A workspace is a smaller enclosed environment that contains integration flows and credentials.
- A member is a registered platform user that has been invited to the project room by Owner and given a specific role. Members can collaborate or work individually.
- A developer team is a smaller enclosed environment that contains connector developers and their repositories.
Project rooms are virtually separated from each other and require corresponding memberships to enter and work in. With the invitation a user gets a user role.
Project Room Management
An Admin can create project rooms and set project room Owners. By default, only members with project room Owner or another role with the right permissions can manage project rooms. However, roles can be customized, so in this document we will differentiate project room and workspace members by permissions.
Here is the full list of project room permissions:
- Edit members in the project room
- Create workspaces in the project room
- View all workspaces in the project room
- Delete workspaces in the project room
- Edit contract repositories
- Edit developer team
A client’s enclosed environment within a project room is called a workspace. Each project room can have multiple workspaces, and each workspace is virtually separated from other workspaces within a project room. A workspace includes members, credentials and integration flows:
- A member is a user with certain access rights in the workspace. These rights are defined by user roles set by workspace Owner upon invitation of a project room member to a workspace.
- An integration flow is a set of integration connectors and credentials used to synchronize data between multiple applications or services. More details on integration flows can be found here. Project room members can be invited to a workspace within their project room by other members with the corresponding permissions. Members can contribute to integration flows in their workspace in collaboration with other members, or individually.
Any project room member can create workspaces. Only workspace Owner or member with corresponding permissions can manage workspaces. Here is the full list of workspace permissions:
- Edit the workspace (including memberships)
- Edit flows in the workspace
- Toggle flow status between active and inactive
- Toggle flow status between ordinary and real-time
- Edit credentials
You can learn more about workspace management here.
Workspaces and Life Cycles
Workspaces in a project room are separated from each other, but they can utilize the same connectors for their integration flows. This means that one can create similar integration flows in different workspaces within a project room. For non-disruptive testing one can create dedicated workspaces for testing and production stages, both running near-identical integration flows. The workspaces will have different credentials, so the testing stage may be accessed by the client’s engineers, and production environment is customer-facing only.