Project Settings is where project administrators review and manage how a project is configured. It brings project details, access visibility, customization tools, and advanced actions into one place.
Use Project Settings when you need to update project information, understand who has access, or manage project-specific setup such as fields, shared steps, parameters, and labels.
To open Project Settings:
You can open Project Settings only when your role allows access to project administration.
Project Settings is organized into four sections:
The General section manages the main project details.
You can update:
The Project Code is shown for reference but cannot be edited after the project is created.
The section also shows project information such as:
You can copy the Project ID when you need it for support, integrations, or administrative reference.
To update project details:
The project name is required. If you leave the page with unsaved edits, Hawzu helps protect you from losing those updates.
The Members & Access section gives an access overview for the current project.
It shows who can access the project directly or through groups, and helps you review whether access is clean and intentional.
You can review:
Project access can appear in different ways:
Each member row shows the user’s project roles, workspace role, access groups, and whether attention may be needed.
Use the filters in Members & Access to find project members quickly.
You can filter or sort by:
You can also open a user’s recent activity or move to the workspace Users page when deeper user management is needed.
For adding or removing members, see Managing Project Members.
The Customization section summarizes project-specific setup.
It shows counts and status for:
Each card explains what the tool is best for and provides a Manage action to open the related project configuration page.
Use project custom fields to capture project-specific information for work items such as test cases, requirements, and defects.
Project custom fields are useful when one project needs extra structure that should not apply to every project in the workspace.
Use project shared steps to reuse repeated test steps within a project.
Shared steps are useful for common setup, navigation, validation, or cleanup patterns that appear across many test cases.
Use project parameters to manage reusable project-specific values.
Parameters are useful for URLs, identifiers, credentials references, test data, or other values that repeat across test cases and shared steps.
Use labels to organize and filter project work.
Labels are useful for components, themes, release slices, triage categories, or any lightweight grouping your team wants to reuse.
The Advanced section is reserved for high-impact project actions.
It currently shows:
These actions are marked as coming soon. The page also highlights that advanced actions can be irreversible and should be handled carefully.
Project Settings depends on your project permissions.
Depending on your role, you may be able to:
If a section or action is unavailable, your role may not include permission for that area.
When managing project settings: