Managing Project Members and Roles

Project members are the people on your project team. They are the people who will submit or resolve issues on your project. From a project screen click Admin > Members on the navigation bar to access the Members screen, where all project members are listed with their roles. Project managers add members to the project from the pool of users within their company. Project managers can also remove individual members from the project as necessary.

A project manager can add or remove a member by clicking Admin > Members on the project navigation bar.

Project Members

From this page, you can view a list of company users who are also project members, along with their assigned role(s) and the date of their last activity in Squish. You can mark the checkbox(es) next to members, then select the roles which that user(s) should have. After all roles are selected, click Set roles for selected members. Note that this will remove previously assigned roles from user accounts before adding the selected role(s).

Note: If there are no company users who are active and are not already members of the project, this section will not be displayed.

The search field allows you to search the members list by selecting attributes to filter on or by keying in a full or partial name or word. The search results highlight the keyword entered in the field.

• Filter options include:
  • Role
  • Group
  • Active
• By default all active users with a User Type of Normal are displayed.
• When the user list is displayed after editing a user account, any filter criteria you add will be remembered.

There is a link to See an overview of member permissions. The page this opens has a chart which lists every project member. It details each member's overall permissions, as well as their permissions for each available issue type.

To Add Project Members

1. Click on the Add Members button.
2. Select one or more company users' names from the Select Users to Add field. The name(s) will appear in a row. You can select as many names as needed.
3. Select the role(s) for the user(s) by checking the boxes next to those roles.
4. Click the Add Users button.

Note: If you have selected a user by accident you can remove them from the line before clicking the Add Users button by clicking on the X at the right of their name.

Individual Member Screens

You can reach an individual Members screen by clicking on the project Admin menu and clicking on Members.  From the Project Members click on a project member name.

A permissions table displays the member's permissions to perform actions for each issue type. You can change the roles that a member has by checking and unchecking the boxes next to the roles in the Roles field. You may also add or remove group membership for the user. Click Update Member when finished. 

To Remove Project Members

1. Click the checkbox next to the members you would like to remove.
2. Click the Remove Selected Members button.
3. Click the OK button on the dialog box to confirm.
• If the user has any issues assigned to them, another page will open notifying you of the number of issues assigned to them. You may select a new user to assign those issues to or select the option to reassign those issues to no one.

Roles provide a way to group users logically within a project.  They also control the general permissions and permissions specific to each issue type within the project.

A user may be assigned multiple roles, and the general permissions below only need to be assigned in one role for the user to perform that action, unless otherwise specified. For instance, if a user is a member of Role A, which can be assigned issues, and Role B, which cannot, then the user can be assigned issues.

General permissions

 The general permissions are:

1. Can access the project administration pages - This allows users who are not the Project Owner to access the project management interface and options.
2. Can be assigned issues - Whether the user can be assigned issues.
3. Can create and edit wiki pages - Determines whether the user can edit wiki pages.
4. Can mass change issues via search - Whether the user can mass change issues within the project.
5. Ensure issue updates only occur via workflows - If selected, the user will be required to use available workflows when updating issues.
   • Unlike other general permissions, the Enforce Workflow permission only requires workflows be used to update issues if that permission is assigned in all of the user's roles.
6. Can view private fields - Whether the user can access fields which are marked as private.
7. Can view confidential issues and comments - This allows users to view comments and issues which are flagged as confidential.
8. Can convert issues between types - If selected, the user will have access to the Convert To menu option when viewing an issue. 
9. Can be contacted via Contact Manager - Indicates that users with this role will be available as options when selecting the Contact Managers header bar option on the homepage.
10. Badge - Text typed into this field will appear next to the name of users assigned this role in issue comments they submit.

You can see a list of which members have each role by clicking See overview of all roles to go to the Role Overview screen. From the Role Overview screen, you can click the role names to edit the role or on member names to go to the individual Members screens for those members.

Issue Type Permissions

There are seven permissions that govern what a user may do for issues of each type:

1. Can View
2. Can Submit
3. Can Comment
4. Can Update
5. Can Modify Resolved
6. Can Delete
7. Notify on Submit
8. Notify on Update

These permissions are assigned by issue type and role. For instance, a Developer role may be able to view all issue types, but only submit Bugs. The ability to delete issues might be only assigned to the Manager role. Like general role permissions, these permissions are checked across all of a user’s roles for the applicable issue type – if any of the user’s roles have permission for the issue type at hand, the user has that permission.

Permissions are also respected when displaying issues. A user will only see issues of types they have permission to view. A user that only has permission to view an issue (not update) will not have the ability to update any of the fields. Finally, only issue types a user has permission to submit will be visible to that user when submitting.

To add a role:

1. Click Create a New Role on the Roles screen
2. Enter a Name for the role.
3. Check the appropriate options for the role.
4. Select project members to be assigned the role. A keyword filter is available to narrow the number of members displayed. The list of members may be filtered to show users fitting each of the following criteria:
   1. Initial – users assigned this role before the edit page was opened.
   2. All – all users.
   3. Selected – all users who will have this role after the Save Changes button is selected.
   4. Not Selected – all users who will not have this role after the Save Changes button is selected.
   5. Additions – all new users who will have this role after the Save Changes button is selected.
   6. Removals – all users who will not have this role anymore after the Save Changes button is selected. 
   7. Changes – all changes made to users with this role since the last save.
5. Check the appropriate permissions to be associated with each existing issue type.
6. Click Create Role.

To update a role:

On the individual Roles screens, you can change the role name, select different general permissions, select different permissions for each issue type, or change the members who are assigned the role. Click Update Role to save the changes.

To delete a role:

Open the individual role screen by clicking on its name on the Roles screen and click the Delete Role button. Click OK on the confirmation dialog to confirm.