Platform BasicsPermissions
Project
What each project role can do
A project groups together issues and features. You can assign a separate set of members to each project, even within the same workspace.
Roles
A project has three roles. Higher rows have more permissions.
| Role | Description |
|---|---|
| Manage | Full control, including members, settings, and deletion |
| Edit | Create and edit issues, features, and content |
| View | View project content only |
Permissions
What each role can do at the project level.
| Action | Manage | Edit | View |
|---|---|---|---|
| View project | ● | ● | ● |
| View issues / features | ● | ● | ● |
| Create or edit issues | ● | ● | — |
| Change issue status | ● | ● | — |
| Create or edit features | ● | ● | — |
| Invite or change member roles | ● | — | — |
| Edit project settings | ● | — | — |
| Delete project | ● | — | — |
A private project is only visible to its members. Switch a project to public, and every member of the parent workspace automatically gets View access.