Workspaces
The article explains the concept of a workspace and serves as a guide for owners and administrators on how to implement workspaces.
Contents
Workspace definition
A workspace can be considered a virtual partition. A workspace is owned by strictly one account. All data within the workspace is owned by and billed to the account owner.
The workspace is the scope for workflow and feature settings. Consequently, workflows and functionality may differ across workspaces. Similarly standard settings are overwritten at the workspace level.
The workspace is also the scope for entities and their associated data. Entities will always belong to strictly one workspace, while the entity may have links to other workspaces. There is no upper limit to the number of entities a workspace can contain.
Workspace administrators can invite confirmed partners to see and contribute to a workspace. All data generated by the partner in the scope of a workspace resides within the workspace. The workspace administrator may at his sole discretion revoke partner access making the data unavailable for the partner.
Workspace administrators can use workspace to granularly control user and partner access and permissions.
Joining or splitting workspaces
It is recommended to use separate workspaces when products or services differ significantly. This typically means that users, partners, workflows and feature settings are also different. Separating workspaces is a good way to remove clutter and noise because users are only served relevant information. The following two examples illustrate when it is best to combine or split workspaces.
Example 1: Join data in one workspace
Organization ABC produces make-to-order concrete elements for the construction industry. Despite being custom-made, all concrete elements share exactly the same manufacturing steps and process efficiency measures. Daily operations are managed within the same team of employees.
Example 2: Split data into separate workspaces
Organization XYZ have product categories A and B that are manufactured on separate production lines with separate performance metrics. Daily operations are managed individually by two separate production teams. Similarly, the supplier base is very diverse and only few partners supply both categories. In this case Organization XYZ should create separate workspaces. This enables the organization to granularly adjust features, settings, users and partners. Management can still maintain the big picture as data is seamlessly merged.
Workspaces as a fulfilment and compliance map
Customer support service by UserEcho
