Project scoping

A Project groups Sources, Destinations, Events, and metrics inside one Organization.

What Projects do

• filter lists and dashboards;
• organize environments such as production, staging, and development;
• group Sources and Destinations by product area or team;
• make large Organizations easier to navigate.

What Projects do not do

• They are not a separate access boundary.
• They do not grant access to a user who is not an Organization member.
• They do not isolate secrets from other Projects in the same Organization.
• They do not create separate billing or quotas.

The security boundary is the Organization. A member can access the resources their Organization role permits across its Projects.

Project settings

A Project has a display name, a URL-safe slug, and an environment. The slug uses lowercase letters, digits, or hyphens and is used in the dashboard URL. The environment is one of production, staging, or development; a new Project defaults to production.

Default Project

Onboarding normally creates a default Project. If an Organization has no Project, create one before creating a Source. A Source always belongs to a Project.

Filtering

Selecting a Project filters the dashboard view. It does not change your Organization access or move resources to a different Organization.