Skip to content

Managing Projects ​

Projects represent the applications, microservices, and message brokers within your organization.


Creating a Project ​

To create a project, click New Project from the dashboard:

  1. Name: A descriptive name for the project (e.g., payment-service).
  2. Description: An optional summary of the project's function.
  3. Tags: Optional organization tags to categorize the project.

Visibility Settings ​

Projects support two visibility levels:

  • Organization: Visible to all members of your organization (default).
  • Private: Accessible only to explicitly added project members and organization administrators.

Member Roles & Permissions ​

Access within a project is controlled by three roles:

  • Admin: Full control. Can manage settings, specs, members, and dependencies.
  • Editor: Can update project details and upload specification versions. Cannot manage members or dependencies.
  • Viewer: Read-only access to specs, dependencies, and project state.

NOTE

Organization Owners and Admins have implicit Admin privileges across all projects.

Breaking Change Approvals ​

When a breaking change is detected in an upstream dependency, approvals for affected consumer projects can be submitted by:

  • Organization Owners and Admins
  • Project Admins on the impacted consumer project

Project Tags ​

Tags categorize and filter projects across your workspace.

  • Management: Organization Admins create and maintain available tags in Organization Settings.
  • Assignment: Admins and Editors can assign tags to projects.
  • Filtering: Filter the project list or graph view by selecting one or more tags.