Skip to content
Hawzu Docs
API reference Go to app

Project Settings

3 min read

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.

Opening Project Settings

Section titled “Opening Project Settings”

To open Project Settings:

  1. Open a project
  2. Open the project menu in the project header
  3. Click Project Settings

You can open Project Settings only when your role allows access to project administration.

Settings Sections

Section titled “Settings Sections”

Project Settings is organized into four sections:

  • General – project name, code, description, and project information
  • Members & Access – people, roles, groups, and access visibility
  • Customization – fields, shared steps, parameters, and labels
  • Advanced – export and deletion options

General

Section titled “General”

The General section manages the main project details.

You can update:

  • Project Name
  • Description

The Project Code is shown for reference but cannot be edited after the project is created.

The section also shows project information such as:

  • Project ID
  • Created date
  • Created by

You can copy the Project ID when you need it for support, integrations, or administrative reference.

Updating Project Details

Section titled “Updating Project Details”

To update project details:

  1. Open Project Settings
  2. Select General
  3. Edit the project name or description
  4. Click Save Changes

The project name is required. If you leave the page with unsaved edits, Hawzu helps protect you from losing those updates.

Members & Access

Section titled “Members & Access”

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:

  • People with access
  • Direct members
  • Inherited-only access
  • Hybrid access
  • Inactive users
  • Groups with access

Access Types

Section titled “Access Types”

Project access can appear in different ways:

  • Direct – the user has a role assigned directly for this project
  • Inherited – the user receives access through a group or another access path
  • Hybrid – the user has both direct and inherited access

Each member row shows the user’s project roles, workspace role, access groups, and whether attention may be needed.

Finding Members

Section titled “Finding Members”

Use the filters in Members & Access to find project members quickly.

You can filter or sort by:

  • Name or email
  • Status
  • Access type
  • Project role
  • Group coverage

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.

Customization

Section titled “Customization”

The Customization section summarizes project-specific setup.

It shows counts and status for:

  • Custom Fields
  • Shared Steps
  • Parameters
  • Labels

Each card explains what the tool is best for and provides a Manage action to open the related project configuration page.

Custom Fields

Section titled “Custom Fields”

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.

Shared Steps

Section titled “Shared Steps”

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.

Parameters

Section titled “Parameters”

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.

Labels

Section titled “Labels”

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.

Advanced

Section titled “Advanced”

The Advanced section is reserved for high-impact project actions.

It currently shows:

  • Export Project Data
  • Delete Project

These actions are marked as coming soon. The page also highlights that advanced actions can be irreversible and should be handled carefully.

Permissions

Section titled “Permissions”

Project Settings depends on your project permissions.

Depending on your role, you may be able to:

  • View project settings
  • Update project details
  • Review members and access
  • Open project customization tools
  • Manage advanced project actions when available

If a section or action is unavailable, your role may not include permission for that area.

Best Practices

Section titled “Best Practices”

When managing project settings:

  • Keep the project name and description clear for all team members
  • Treat the project code as a stable identifier
  • Review direct and inherited access regularly
  • Use project-level customization only when it should apply to this project
  • Prefer shared steps and parameters for repeated content
  • Use labels consistently so filtering and reporting stay useful
  • Be cautious with advanced actions, especially project deletion

Next Steps

Section titled “Next Steps”