Last updated

Workspace Setup

A workspace groups work items, people, pages, tests, and delivery views. Its settings control local access and the tools shown to the team.

Create a workspace

  1. Open Workspaces and select the create action.
  2. Enter a name and workspace key.
  3. Choose a built-in pack, an available template workspace, or a blank setup.
  4. Review the creator-only visibility option.
  5. Create the workspace.

Creating a regular workspace requires the workspace.create global permission. The personal Todo List does not require it. The helpdesk pack supplies a starting support process. See Helpdesk in a workspace.

Members and visibility

Workspace administrators assign users and groups in workspace member settings. Use a built-in role to grant permissions. Custom roles are routing labels, not permission grants.

An empty member list does not make a regular workspace private. The Everyone fallback can grant access to all authenticated users. Use creator-only visibility at creation when the workspace must start restricted, then assign the intended users and groups. See Workspace Roles.

Process configuration

A configuration set supplies workflows, screens, item types, priorities, and governance. System administrators manage those shared definitions. Changing a workspace's configuration can require migration when existing work uses definitions absent from the new set. See Configuration Sets.

Workspace navigation settings control enabled views and their order. The queue is optional. A workspace default view must remain enabled. Hiding a navigation entry does not revoke API or item permissions.

The workspace welcome dashboard has its own layout. It is separate from your personal home dashboard. Customize its sections and widgets for the workspace, subject to workspace administration rights.

Work item templates

Workspace administrators manage description templates in workspace settings.

  • Selectable templates appear in the create form for matching item types. A template without type restrictions can apply across types.
  • Mandatory templates target exactly one item type. When the description is empty, Windshift fills it from the template. They do not force users to preserve the template text in a description they already supplied.

Templates prefill descriptions. They do not replace required fields or workflow validation.

Other workspace tools

Workspace settings also connect source control, configure service levels, and manage canned responses and recurrence rules. Agent Studio manages Standard and Coding agents for the workspace.

Reuse workspace content

Workspace bundles provide portable pages, labels, seed items, item links, and optional process configuration. Built-in packs use this format. A bundle is not a full backup of every workspace record or attachment.

In 0.9.5, bundle export and import are available through API v2. Export requires workspace administration. Import requires page and item creation rights. Bundles containing navigation or service-level settings also require workspace administration. An embedded configuration-set template requires system administration before any content is imported.

See the REST API overview for the v2 reference. Do not use the deprecated v1 API for a new integration.