Project settings
Review and update the identity and supported configuration of the active project.
Project settings control the supported editable properties of the active project. Open Project → Settings and verify the selected project before saving changes.
Project identity
Use a name that helps operators distinguish the product and environment. Changing a display name should not be used as a substitute for creating a separate isolation boundary.
Before changing settings
Check whether the value is used in dashboards, automation, or team conventions. Resource IDs remain the reliable programmatic reference even when a human-readable name changes.
What is configured elsewhere
Project settings do not replace resource-specific configuration:
- model fields belong to Data Models;
- warehouse connections belong to Warehouses and Credentials;
- write permissions belong to Ingest Clients or API Keys;
- read permissions belong to Query Clients or API Keys;
- team membership belongs to the workspace.
Production changes
Treat production project changes as controlled operations. Review the effective client scopes and destinations after editing related resources. Use separate staging and production projects when a change needs validation with real runtime traffic.