Views can be exposed as workspaces. Workspaces encapsulate a view together with additional settings and are used to expose specific views to specific clients. This way the complexity of the view tree can be hidden from clients (like mobile applications etc) and the data available to specific clients can be centrally managed.

A workspace consists of:

•Workspace name and description: Two strings that help users to understand the contents of the workspace.

•Workspace type: Every workspace is of a specific workspace type. The workspace type defines which type-specific settings are available for that workspace and might also implement specific feature filters that are implicitly added to the underlying view.

•Underlying view: The underlying view specifies the features that will be available in this workspace. Note that depending on the workspace type the features might be additionally filtered based on the workspace type's internal logic.

•Type specific settings: Every workspace type can have its own specific settings that allow the user to specify the behavior of the workspace.

•User / user group association: Workspaces can be associated to users and user groups. Only those users associated with a specific workspace will see this workspace. Note that a workspace does not have its own privileges. However when adding a user or user group to a workspace the Application Server will give those users and user groups the view permissions List features (2), Read features (100), and the view permission Read observations (103)

One view can be exposed as many workspaces.