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.
When to use
- Use workspaces to separate requirements work by product, squad, client, or initiative.
- Use them to define which knowledge bases should guide AI generation.
- Use them to connect generated requirements to the right provider.
- Use them when a team needs to continue evolving the same backlog context over time.
Before you start
- Confirm the active organization.
- 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: prepare a workspace
- Open the workspace area in Intelligent Requirements.
- Select the project that represents the work context.
- Create or open the workspace used for the initiative.
- Review the knowledge bases available for the selected project.
- Choose the knowledge bases that should support AI generation.
- Select the provider that should receive backlog items when they are published.
- Continue to requirement generation when the workspace context is ready.
Understand the main fields
| Field | What it means |
|---|---|
| Project | Context that groups the workspace and related knowledge bases. |
| Knowledge bases | Lens KBs used as AI context for generation and refinement. |
| Provider | Work management destination where approved requirements can be sent. |
| Generated requirements | Backlog items created inside the workspace before review or publication. |
Expected result
You should have a workspace that clearly connects the initiative, project context, knowledge bases, and publication destination used by the requirements flow.