Workspaces

The Workspaces module enables you to structure your organization into independent business units or autonomous operational areas. This feature is designed for entities that require separate project management environments and distinct access controls, ensuring complete data segregation across the organization.

Worspace configuration

Administrators manage workspaces in System Settings -> Organization -> Workspace.

• Default Workspace: Every organization has at least one workspace. By default, a workspace named after the Organization is created.
• Adding: Click “+ Add”, enter a Name (mandatory), and select a Color for visual identification.
• Editing: Click a workspace name to rename it or change its color.
• Deleting: You cannot delete the last remaining workspace. To delete a workspace, you must select a target workspace to migrate existing data (Projects, Templates, Charters, Approval Paths).

Workspace data visibility

Workspaces act as strict containers for system objects, determining the availability of projects, standards, and data in reports.

• Projects: Every project must belong to a specific workspace. Selection is mandatory during creation (auto-filled if the user belongs to only one workspace). You can organize the Project List by grouping or filtering by workspace. To transfer a project to another unit, change its assignment in Project Settings (requires access to the target workspace).

• Project Templates & Paths): System standards are scoped to specific workspaces. When creating a project, you will only have access to Project Templates and Acceptance Paths assigned to your current workspace. This ensures that teams use only the procedures relevant to their business unit.

• Reporting: Global reports respect workspace boundaries. The system aggregates data only from the workspaces you have access to, ensuring strict data segregation. For broader analysis, you can use the Workspace column and filter to compare performance across different business units.

Worspace scope

The Workspace configuration defines the operational scope for key system elements. This ensures that data and processes are strictly isolated and only available within their assigned context:

• Projects: Every project is assigned to a workspace upon creation. Users can only access projects located in workspaces they are authorized for.
• Project Templates:
  •  Usage: When creating a project, you can only select templates assigned to the workspace where the project is being created.
  • Management: You can create and edit templates for any workspace you have access to.
• Acceptance Paths:
  • Usage: Inside a project, you can only select acceptance paths configured for that project’s workspace.
  • Management: You can configure new paths for any workspace you are authorized to manage.

Workspace visibility across reporting views

Workspaces are also surfaced in portfolios, project reviews, and graphical reports:

• In portfolios and project reviews, a Workspace column can be displayed, and the project list can be filtered by workspace.
• When adding projects to a portfolio or review, the workspace of each project is shown and can be used as a filter.
• In graphical reports, workspace is available both as a filter (see Filtering data on a single chart) and as a grouping option — for example, showing the number of projects or summed values of numeric attributes broken down by workspace.

Note: if your organization has only one workspace defined, the Workspace column and filter are hidden to keep the UI clean.