Skip to content

Projects and Roles

A project is a folder of artifacts plus a membership list. Access to private artifacts comes from the role you have on that project (or from a share link, if the artifact is org-visible or public).

Click the + next to PROJECTS in the sidebar. Name it, then click Create project. You become Owner.

New project dialog

Agents can also create projects over MCP with create_project. See MCP and API keys.

Expand the project in the sidebar and click the gear next to its name. The settings page is where you rename the project, manage members, and delete it.

Project settings

  1. Change the Name field and click Save. Use a name people will recognize in search and in the sidebar.

  2. The members table lists each principal (a user or a group), their type, and their role. At least one Owner is always required. You cannot demote or remove the last Owner until you promote someone else.

  3. Under Add members:

    • Choose User or Group.
    • Pick a role (see the table below).
    • Search by name or email, then add the selected people.

    Groups come from the organization. Assigning a group is a good way to give a whole team the same role without listing everyone.

  4. Use the trash icon on a row. If you remove yourself, you lose access until an Owner adds you again.

Roles are per project. They decide what someone can do with artifacts and comments in that project.

RoleWhat they can do
ViewerOpen and read artifacts. Cannot comment or edit.
CommenterRead artifacts and leave comments. Cannot create or edit artifacts.
EditorCreate, edit, and delete artifacts, and moderate comments.
OwnerEverything an Editor can do, plus members, settings, and deleting the project.

The Danger zone at the bottom permanently removes the project’s artifacts (including search index entries), comments, and memberships. This cannot be undone. Only an Owner can do it.