Create a Project
New projects are created with the New project button on the main Projects page or from Admin → Projects. The form has three tabs — PROJECT, USERS, and GROUPS — but only the PROJECT tab is required to create a project. USERS and GROUPS let you configure access rules at creation time, but they can be set up later.
How to create a project
- Go to Projects in the top navigation (or Admin → Projects) and click New project.
- Fill in the required fields on the PROJECT tab (at minimum, a project name).
- Optionally configure USERS and GROUPS access rules on the other tabs.
- Click Create. The project appears immediately in the Active tab on the Projects page and in the Active table in Admin.
Not sure where to start? On the Projects page you can also click Try the sample project to create a pre-built project with test cases, runs, and explorations. See Browsing Projects for details.
PROJECT tab fields
| Field | Required | Notes |
|---|---|---|
| Icon | No | Choose an emoji, pick from the icon library, or upload an image |
| Project Name | Yes | Must be unique within the workspace |
| Summary | No | Short description shown in the project list |
| Default Access | Yes | Controls how member roles are resolved — see below |
| Default Role | Conditional | Required when Default Access is set to Override with a specific role |
| Mark as completed | No | Toggle — immediately moves the project to the Completed tab |
Default Access explained
The Default Access setting controls which role is used as the baseline for members of this project. There are two options:
- Use each member's own role
- When a user is added to this project, their workspace-wide Role applies. This is the standard setting and means the project follows whatever role each user carries globally. Individual overrides can still be set on the USERS or GROUPS tabs.
- Override with a specific role
- A specific role you choose is used as the default for all members of this project, regardless of their Role. This is useful when you want a consistent permission floor for everyone in the project — for example, making all members read-only unless explicitly granted more access.
For how these settings interact with individual user overrides and access modes, see Project Access. For the relationship between Roles and project permissions, see Roles.
USERS and GROUPS tabs
The USERS tab lets you add individual users to the project and set their access mode at creation time. The GROUPS tab does the same for Access Groups. Both tabs are optional — you can create the project first and configure access separately using the Access button on the admin projects list, or the edit form from the main Projects page.
USERS tab columns
| Column | Description |
|---|---|
| User | The user's name and email address. |
| Workspace role | The user's workspace-wide role — read-only, shown for reference so you know what permissions they carry by default. |
| Project access | The access mode for this user in this project: Inherit, No access, Force role, or Specific role. |
| Override role | Only active when the access mode is set to Specific role. Choose a role to use instead of the user's workspace role for this project only. |
GROUPS tab columns
| Column | Description |
|---|---|
| Group | The access group's name and description. |
| Members | Number of users in the group. |
| Project access | The access mode applied to every member of this group: Inherit, No access, Force role, or Specific role. |
| Override role | Only active when the access mode is set to Specific role. Choose a role to apply to all group members in this project. |
For a full explanation of access modes and how effective roles are resolved, see Project Access.
Editing an existing project
On the main Projects page, project admins use the edit control on a project card. In Admin → Projects, click the Edit button on any project row. The same form opens on the PROJECT tab. All fields can be changed, including the Default Access setting. Changes take effect immediately.