Product documentationUpdated October 6, 2025
Project Settings
Configure project defaults—environments, roles, integrations, and advanced options—so teams collaborate safely and runs stay consistent.
Overview
Project settings control how a project behaves day-to-day: defaults, access, environments, and integrations. Tight settings early prevent flaky runs and permission surprises later.
General settings
- Update name and description.
- Choose a default environment for runs.
Team and permissions
- Assign roles (Admin, Editor/Tester, Viewer) based on responsibility.
- Restrict who can change endpoints, tests, and configuration.
Related: Role permissions and User policies.
Environments and variables
- Define environment-specific base URLs and variables.
- Keep dev/stage/prod separate to reduce noisy failures.
Related: Configuration fundamentals and Test configuration.
Integrations and notifications
- Connect to CI/CD pipelines and automation workflows.
- Configure notifications (email/Slack/Teams/webhooks) for visibility.
Advanced options
- Enable versioning or change tracking where available.
- Set default import behavior for specs (OpenAPI/Swagger, etc.).
Related articles
Related articles
- Managing Projects · Product documentation
- Project · Product documentation
- Project Operations · Product documentation
Next steps
- Getting started · Install + connect your spec
- Configuration fundamentals · Stabilize runs
- Initial configuration · Users, licensing, projects
- Release notes · Updates and fixes
Still stuck?
Tell us what you’re trying to accomplish and we’ll point you to the right setup—installation, auth, or CI/CD wiring.