Primary Role: any user
Workspaces are logical collections of Projects, Workflows, Connections, and Resources that are accessible to assigned groups of users. These are managed by workspace managers and administrators. All users are automatically assigned to the Default workspace.
Creating, editing, and deleting workspaces requires Administrator permissions. For more information about workspaces as an Administrator, see the Workspaces section of the Administrator Guide.
A workspace is a unit of separation defined by the scope of a user’s permissions within the workspace.
A user’s role and the workspace(s) they belong to define the user's permissions and access.
Role permissions define the actions a user with that role is allowed to do.
Workspaces allow administrators to grant access to entities that belong to the workspace, such as projects, connections (git, S3), resources, and workflows.
Example: User A belongs to Workspace 1 and Workspace 2.
Workspace 1: This workspace has workflows, but User A has a Viewer role, so they can only view workflows in this workspace.
Workspace 2: This workspace has workflows, and User A has an Operator role in this workspace, so they can view and run workflows in this workspace.
This feature allows an organization to manage user access within multiple workspaces. Each workspace has a separate dashboard, projects, users, and connections.
A user with a role within the default workspace can have a different role in another workspace.