Workspaces
Workspaces are the environments where users organize a work front, product, project, or initiative inside Intelligent Requirements. A workspace brings together the project, the Lens knowledge bases used by AI, and the provider where backlog items can be published.
Each workspace is connected to a project and can use one or more knowledge bases associated with that project. This keeps generation tied to the right context and reduces the risk of mixing information from different initiatives.
The provider is optional. A workspace without a provider can still generate, refine, and save requirements to knowledge bases; publishing backlog items requires a provider with a configured adapter.
When to use
- Separate requirements work by product, squad, client, or initiative.
- Define which knowledge bases should guide AI generation.
- Connect generated requirements to the right provider.
- Keep a backlog context that the team continues to evolve over time.
Before you start
- Select the project that should contain the workspace.
- Confirm that the relevant knowledge bases are associated with the project.
- Confirm that the target provider and adapter are available when publication is needed.
Step by step: create a workspace
- Open the workspace list and select Create workspace.
- Name the workspace. The name must be unique within the organization.
- Select the project that represents the work context. You can also create a new project during the flow.
- Choose the provider, or keep the workspace without one.
- Complete the provider configuration: Jira and Azure DevOps require selecting the provider project; BusinessMap requires mapping the board, workflow, column, lane, and a card type for each level.
- Select the knowledge bases used as context for generation.
- Optionally, select the knowledge bases that should receive generated items and enable auto-save for items created in the provider.
- Create the workspace and continue to requirement generation.
Manage workspaces
- The workspace list supports search and sorting; each card shows the project, the provider, and the linked initiative.
- Workspace settings allow renaming the workspace, changing the project (which clears the selected KBs), and changing the provider configuration.
- Inside the workspace, the knowledge base panel controls the context KBs, the save KBs, and the write-back options.
- Deleting a workspace is permanent and asks for name confirmation. Generated initiatives stay in the history but are no longer linked to a workspace.
Understand the main fields
| Field | What it means |
|---|---|
| Name | Identifies the workspace in the list. Unique within the organization. |
| Project | Context that groups the workspace and related knowledge bases. |
| Provider | Work management destination where approved requirements can be sent. Optional. |
| Provider project or mapping | External project required by Jira and Azure DevOps, or the board mapping required by BusinessMap. |
| Context knowledge bases | Lens KBs used as AI context for generation and refinement. |
| Save knowledge bases | KBs that receive generated items, manually or automatically. |
Expected result
You should have a workspace that clearly connects the initiative, project context, knowledge bases, and publication destination used by the requirements flow.