Skip to main content

Projects

Projects help organize Intelligent Requirements by product, squad, client, or initiative. They group workspaces and knowledge bases so each team can keep its requirements context separated from other work.

When a user works inside a project, the workspace and related knowledge bases come from that same context.

When to use​

  • Use projects to separate work by business or delivery context.
  • Use them before creating workspaces that need project-specific knowledge bases.
  • Use them to avoid mixing information from different products, squads, clients, or initiatives.
  • Use them to make generated requirements easier to trace back to the right context.

Before you start​

  • Confirm the active organization.
  • Choose a project name that other users can recognize.
  • Prepare the knowledge bases that should belong to the project.

Step by step: use a project​

  1. Open the project area or select the project during workspace setup.
  2. Choose the project that matches the work context.
  3. Review the workspaces linked to that project.
  4. Review the knowledge bases available for that project.
  5. Continue the requirements flow inside the selected project context.

Expected result​

You should have a project structure that keeps workspaces, knowledge bases, and generated requirements aligned with the correct product, squad, client, or initiative.

See also​