Project permissions
A member can use an action only on a project you assigned, and only when that action is allowed for them.
The role stores the default actions. On the member, you can override those defaults for one project. The Permissions tab says: overrides for this member only, and role defaults apply where you do not override them.
Only an Admin can change this.
Open the Permissions tabOpen the Permissions tab
Open Settings, then Users, and stay on the Users tab.
Click the member's name. The panel shows Profile and Permissions.
Switch to Permissions. Role and Project access sit above the action grid.
Role and project on this tabRole and project on this tab
On the invite, project access is different: you check every project the person may open. That step is in Inviting users. This tab is where you set the actions inside one of those projects.
The action gridThe action grid
Each module has four checks: View, Create, Edit, and Delete.
The boxes above mark where each action sits. A filled check on the member allows that action. An empty check does not. Boxes you do not change keep the role default.
Choose Save on the panel when the checks should be kept. Saving this member does not change other members on the same role.
How the two choices fit togetherHow the two choices fit together
A member with no project checked on the invite has no project to open, even if their role allows View on Test Case or another module.