Member Permissions
Here, we will explain members' permissions in your Workspace. Each Workspace member has their own permission settings. There are two levels of permission settings – Workspace and Project – that are independent of one another.
| Permissions | Summary |
|---|---|
| Workspace | Permissions for Workspace-wide operations. Add/Delete Projects, Member Management, and more. |
| Project | Permissions for operations within a Project.Upload applications, create teams, and more. |
Workspace Permissions
Workspace permissions apply to Workspace members and Projects.
Permission Types
The following permissions are available for Workspace members, and can be set individually.
- Add/Invite User: Add new members to the Workspace.
- Delete User: Delete members from the Workspace.
- Change User Permissions: Change permission settings of other members, as long as your own permissions authorize you to do so.
- Create Project: Add a new Project to the Workspace and add/delete Project members.
- Delete Project: Delete a Project from the Workspace.
- Browse Projects: View Projects to which you do not belong. Users without these permissions can only see the Projects to which they belong.
You cannot change your own permission settings. You must have another member with administrative permissions make the changes for you.
Access Workspace Admin Console
Users with one or more Workspace permissions can access the Workspace Admin Console. Users without Workspace permissions (general members) will not be able to access it.
Preset Permissions
Frequently used settings have been grouped into 3 preset permissions combinations of “Administrator,” “Manager,” and “General User.” All other combinations will be displayed as “Custom” permissions.
| Permissions | administrator | Manager | General User |
|---|---|---|---|
| Add/Invite User | ◯ | ◯ | ✕ |
| Delete User | ◯ | ✕ | ✕ |
| Change User Permissions | ◯ | ◯ | ✕ |
| Create Project | ◯ | ◯ | ✕ |
| Delete Project | ◯ | ✕ | ✕ |
| Browse Project | ◯ | ✕ | ✕ |
- Administrators can view all Projects and can perform all Workspace operations.
- Managers can perform all operations related to their own Projects, as well as add new members to the Workspace. It is designed for members who manage projects, such as development leaders.
- General Users are designed for members who do not perform administrative operations, such as team members and testers.
Setting Permissions
Member permission settings can be accessed via Member Information. To change permissions, a member must have the authority to “Change User Permissions.”
Changes to Preset Permissions can be completed using the dropdown menu on the right side of the member list.
Project Permissions
Project permissions are set on a team basis, and cannot be set for individual members. These permissions enable the smooth operations of the Project, including uploading new applications or changing team configurations.
Normally, Project owners/administrators will set permission settings for each application that they oversee. For example, there may be a developer team for an existing application. For a new application, an administrator may assign this team to be testers instead, allowing the team’s members to have the flexibility to work on other applications without compromising their own work.
Note that the Workspace Admin Console will not reflect Project members’ team affiliations. Exception: The Workspace Admin Console will have the Project member list display Project owners (administrators) as “owners.”
Permission Types
Projects have 3 types of permissions, each classified into teams.
- Administrator: Access to all Project operations concerning applications and teams. Ability to upload new applications, create teams, and add/delete members. Access all of the Project’s applications.
- Developer: Update the team’s existing applications. Cannot upload new applications or modify teams.
- Tester: Can only download the team’s existing applications.
Please refer to Projects for details on teams and how to use them.
Project Access
Only members who have been specifically added to a Project from the Workspace Admin Console AND have the requisite team permission settings can access Project information.
For Workspace administrators to access a Project’s applications and teams, they must add themselves to the Project first, and if necessary, add themselves as a member of the owner team.