Use project settings to configure how Level CI analyzes your repository, organizes accessibility results, and manages issue ownership across your development workflow.
On this page:
- Project name
- Default baseline branch
- Quality gate
- Quality profile
- URL parameters
- Dynamic page URL templates
- Default assignee
Project name
The project name identifies your project in the Level CI dashboard and CLI.
Project names must:
- Be unique within your organization
- Be slug-compatible
Contain only:
- Lowercase letters
- Numbers
- Hyphens (-)
- Spaces and special characters are not supported.
Default baseline branch
The main branch defines the default branch analyzed by Level CI when no branch-specific parameters are provided.
Common examples include:
maindevelophead
When importing a repository from a supported Git hosting provider, Level CI automatically detects and configures the main branch.
The main branch must be analyzed before running analysis on additional branches.
Quality gate
The Quality Gate defines the accessibility criteria your project must meet.
Selecting a Quality Gate helps ensure your project aligns with your organization’s accessibility requirements and compliance standards.
If no Quality Gate is selected, Level CI uses the organization’s default Quality Gate configuration.
Quality profiles
By allowing organizations to customize which rules are evaluated and which issues should influence quality gates, Quality Profiles help align accessibility testing with internal standards, development maturity, and remediation priorities.
This enables teams to focus on the issues that matter most, reduce noise, and create a more consistent and scalable approach to enforcing accessibility requirements throughout the development lifecycle.
Ignore Unstable Issues
Configure project settings to suppress known unstable or flaky issues from affecting results, helping teams focus on actionable accessibility defects.
URL parameters
Enable URL parameters to include URLs with query parameters or hash fragments in accessibility analysis.
This is useful for applications where page content changes dynamically based on the URL.
Examples include:
/?page=main
/#order-listWhen enabled, Level CI analyzes each unique URL parameter combination to provide broader scan coverage.
Dynamic page URL templates
Dynamic page URL templates define patterns for dynamic routes and generated pages.
These templates help Level CI identify and organize related dynamic pages more accurately during analysis.
The field behavior may vary depending on workspace state:
- Initial state: prompts for template input
- Workspace access granted: displays previously configured templates
Default assignee
Use the Default Assignee setting to automatically assign newly detected accessibility issues.
Assignment behavior depends on the scan type:
| Scan type | Assignment behavior |
| Branch scans | Assigns new issues to the configured team member |
| Pull request scans | Assigns new issues to the pull request author |
This helps improve accountability and streamlines accessibility remediation workflows.