Appearance
Who sees what
Your rights come from your rank in the workspace. Your teams decide which projects you see.
Workspace ranks
| Rank | You can |
|---|---|
| Admin | Everything in the workspace: invite people, manage members, teams and settings, see every project, delete tickets. |
| Contributor | Work: create and edit tickets, assign, freeze and cancel them, create projects, register your own conductor, record your own time. |
| Guest | Read tickets, comments, projects and teams. Change nothing. |
The person who created the workspace has every right in it. Creating or deleting a workspace itself is reserved for the instance administrator.
Teams
A team makes its projects visible to its members. You see every ticket of every project you can see; tickets are never filtered by person.
| Team role | Adds |
|---|---|
| Member | Sees the team's projects. |
| Lead | Edits the team's projects and billing accounts, sees the team's statistics and the recorded hours of active members. |
| Owner | Also manages who is in the team. |
In short
| You want to | You need |
|---|---|
| See a project and its tickets | Membership in one of its teams, or Admin |
| Create, assign, freeze or cancel a ticket | Contributor |
| Review a ticket | To be listed under Reviewers on that ticket |
| Record your time | Contributor; only you can edit your entries |
| See a teammate's hours | Team Lead, for active members of your team |
| Manage billing accounts | Team Lead, Team Owner or Admin |
| Change a conductor or machine | To be its owner |
| Invite someone | Admin |
Another workspace is invisible to you, even its name. An API key you create acts as you, with your current rights, for at most a year.
Review, merge and deployment stay explicit human decisions, whatever your rank.