For a brief introduction to Workspaces, refer to this article.
With the addition of Workspaces, a new user role has been added called a Workspace Owner. This user role will have all Account Owner permissions but restricted to the assigned Workspace. All other user roles/permissions remain unchanged. Learn more about other User roles here.
An Account Owner can specify which Workspace a user has access to by navigating to the Account Settings and then to the Users page. SAML and LDAP functionality remains unchanged. For SAML, Account Owners will have the ability to specify a Workspace mapping from their IdP. This will be used to set the initial Workspace for a user. A default Workspace can also be defined for all new users.
Here is the breakdown of resource sharing at the Account and Workspace level:
Machine Data Sources
With Workspaces enabled, here is a breakdown of the Account and Workspace scoped settings that can be adjusted by Account Owners at the account level and Workspace Owners at the Workspace level :
Date and Time - Time Zone
Date and Time - Format only
Schedules and Shifts
Navigating Across Workspaces
Only Account Owners have the ability to navigate across workspaces within an instance.
All other User roles are Workspace specific. At this time, a user can only have one role within one Workspace, i.e. John Smith can be an Administrator in only one workspace.
In the App editor, you can navigate across Workspaces using the dropdown menu in the top left of the page from Workspace scoped pages.
Workspaces cannot be deleted or hidden once created. A Workspace's name and other settings can be customized after creation using the Workspace Settings page.
In order to add a Workspace, please get in touch with Tulip Support at email@example.com or via Live Chat.
Moving Apps across Workspaces
The App Import/Export functionality remains unchanged across Workspaces within the same instance.