Control who can access your projects

Before you Start

🛈 This feature is considered stable for production use. For any feedback or issues, please use bug reports and feature requests.

👥 This feature is available to all users.

This page explains how to control access to your projects using project visibility and project settings. For team membership and team access levels, see Manage project teams.

By default, a project you create is private and only visible to you. To collaborate with other users, you can make the project visible to all users (not private) and/or configure access rights through teams.

Projects can be either private (the default) or public. Public projects are visible (but not editable) to all connected users. Private projects are only accessible to specific users with whom you share it. See Share a project and Manage project teams for more details.

1. Share a project

You can own projects individually, or you can share projects with other people.

You can restrict who has access to a project by choosing the project’s visibility. For more information, see Project owner and visibility.

For projects you own, you can give other users access so that they can collaborate on your project.

  1. Open the Project Editor.

  2. Click the Settings button in the project menu.

  3. In the Visibility section, choose whether to keep the project private:

    1. Enable Keep the project private so only the owner and team members with an access rule can see the project (see Manage project teams).

    2. Disable Keep the project private to make the project visible to all users of the server (read-only unless additional access rights are granted).

To change sharing settings later, go to Project settings.

2. Project settings

You can adjust various settings of a project from the Project Settings page, accessible using the gears icon in the menu bar of the Project Editor:

  1. The General tab provides basic information about the project.

  2. From the Visibility tab you can configure the project visibility and access rules (see Manage project teams).

  3. From the Webhooks tab you can configure which webhooks are enabled for this project.

2.1. Project owner and visibility

A project has a visibility setting. In the UI, this is presented in the Visibility section of the project settings. For example, you may see messages such as:

  • The project is currently private

  • Keep the project private

Keeping a project private ensures that only its owner and members of a team with an access rule for the project can see its content. If the project is not private, it is visible to all users of the server.

In documentation, this corresponds to the two visibility states: private and public.

  1. If a project is public, all users on the system will be able to view all of its content, but not make any modification (unless explicitly authorized).

  2. If a project is private, by default only the project owner can view it.

To change the visibility of a project after its creation, select your choice in the Visibility tab of the project settings. The effect is immediate.

To give Read-only access to a private project or give collaborators Write access to a project, define Teams in the appropriate settings section. For team management tasks (access levels, members, and team creation), see Manage project teams.

2.2. Webhooks

From the Webhooks tab in the project settings, you can enable and configure project webhooks. For detailed webhook behavior and API integration information, refer to the Developer Guide.