Project Settings
Manage your project's name, description, slug, and access the danger zone for destructive operations like project deletion.
Project settings let you update metadata, review project details, and perform administrative operations. Only users with the appropriate role can modify settings or delete a project.
Accessing Project Settings
- Open your project from the sidebar
- Click Settings in the project navigation menu
The settings page is divided into sections: general information at the top and the danger zone at the bottom.
General Settings
Project Name
The project name is displayed throughout the CallMeter interface -- in the sidebar, project list, breadcrumbs, and dashboards. You can change it at any time.
- Navigate to Settings in your project
- Edit the Name field
- Click Save
The name change takes effect immediately across the entire interface.
Slug is permanent
Renaming a project does NOT change its URL slug. The slug was generated when the project was created and remains fixed to preserve links, bookmarks, and API references. If your project was originally named "Test Environment" with slug test-environment, renaming it to "Staging QA" keeps the slug as test-environment.
Project Description
The description provides context for team members about what the project is used for. It is displayed on the project dashboard and in the project list.
Good descriptions answer:
- What SIP infrastructure is this project testing?
- Which environment does it target (production, staging, development)?
- Who is the primary audience or customer?
Examples:
- "Production Asterisk cluster -- 24/7 monitoring with probes and weekly load tests"
- "Acme Corp SIP trunk testing -- pre-deployment validation"
- "R&D codec comparison tests -- experimental, not for production use"
Understanding the Project Slug
The slug is the URL-safe identifier for your project. It appears in every URL under this project:
https://callmeter.io/app/{slug}/tests
https://callmeter.io/app/{slug}/probes
https://callmeter.io/app/{slug}/registrarsThe slug is auto-generated from the original project name at creation time:
| Original Name | Slug |
|---|---|
| My SIP Test Lab | my-sip-test-lab |
| Production PBX v2 | production-pbx-v2 |
| Acme Corp | acme-corp |
Why is the slug immutable? Changing a slug would break:
- Bookmarked URLs used by your team
- Shared links sent to stakeholders
- API integrations that reference the project by slug
- Probe webhook configurations that include the project identifier
If the current slug is unacceptable, create a new project with the desired name and migrate your resources.
Danger Zone
The danger zone contains destructive operations that cannot be undone. These actions are visually separated from normal settings to prevent accidental use.
Deleting a Project
Deleting a project permanently and irreversibly removes the project and all of its associated resources:
| Deleted Resource | Details |
|---|---|
| Tests | All test configurations and their entire run history |
| Test run data | All metrics, endpoint data, and SIP traces from every run |
| Registrars | All registrar configurations |
| SIP accounts | All stored credentials |
| Media files | All uploaded audio and video files |
| Probes | All probe configurations, health history, and scheduled executions |
| Status pages | All public health dashboards powered by this project's probes |
| Worker assignments | All user-owned worker assignments to this project |
| Webhooks | All webhook configurations associated with this project's probes |
This action cannot be undone
Project deletion is permanent. There is no recycle bin, undo period, or recovery option. All test run data, metrics, and historical probe results are permanently erased. If you need to preserve any data, export it before deleting the project.
To delete a project:
- Navigate to Settings in your project
- Scroll down to the Danger Zone section
- Click Delete Project
- Confirm the deletion by typing the project name exactly as shown
- Click Confirm Delete
Who can delete a project? Only organization members with the Admin or Owner role can delete projects. Viewers, Testers, and Editors cannot access this action.
Transfer Ownership
If your organization has multiple admins, you may want to transfer project ownership before deleting your account or leaving the organization. Contact your organization owner to reassign resources if needed.
Settings and Role Permissions
Not all roles can access or modify project settings:
| Action | Viewer | Tester | Editor | Admin | Owner |
|---|---|---|---|---|---|
| View settings | No | No | Yes | Yes | Yes |
| Edit name and description | No | No | Yes | Yes | Yes |
| Delete project | No | No | No | Yes | Yes |
Best Practices
- Audit before deleting -- Review the project's tests, probes, and registrars before deletion. Make sure no active probes are monitoring production infrastructure.
- Export data first -- If you need historical metrics or test results, export them before deleting the project.
- Use descriptions -- Keep descriptions up to date so team members always know the purpose of each project.
- Communicate slug choices -- Since slugs are permanent, coordinate with your team on naming conventions before creating projects.
Next Steps
- Managing Members -- Control who can access this project
- Creating a Test -- Set up your first test in the project
- Roles and Permissions -- Full RBAC reference