Skip to content
Hawzu Docs

Workspace Projects

1 min read

The workspace Projects page shows the projects available in the current workspace. It is the first page you see after opening a workspace.

Projects organize repository items, requirements, releases, test runs, defects, labels, settings, and reports for a specific application or area of work.

Open the Projects Page

Section titled “Open the Projects Page”

To open workspace projects:

  1. Open Workspaces
  2. Select a workspace
  3. Review the workspace Projects page

Path pattern:

/workspace/:workspaceId/projects

Project Cards

Section titled “Project Cards”

Each project appears as a card.

A project card can show:

  • Project name
  • Project code
  • Project description
  • Open action
  • Settings action when your role allows project editing

Click a project card or Open to enter the project. When you open a project, project-level navigation becomes available for repository, requirements, test suites, releases, test runs, defects, observatory, and settings.

Create a Project

Section titled “Create a Project”

When your role allows project creation, click Create Project from the workspace Projects page.

Project creation includes:

  • Project name
  • Project code
  • Optional project description
  • Initial user and role assignments

The project code must be exactly 3 characters. Required fields must be valid before the project can be created.

For the full creation guide, see Creating a Project.

Project Access

Section titled “Project Access”

Project access depends on roles.

Users can access a project through:

  • A direct project role
  • A group that has project access
  • Workspace-level access from a high-privilege workspace role

Use the project Users page or workspace settings access views to understand who can access a project and why.

Learn more:

Best Practices

Section titled “Best Practices”
  • Use clear project names that match the product or area of work
  • Use meaningful 3-character project codes
  • Add descriptions so team members understand project scope
  • Review direct users and group access regularly
  • Use groups for team-based access when several users need the same role

Next Steps

Section titled “Next Steps”