Users, Groups and Permissions

Defining users and groups in PractiTest is very easy.

support_groups_users

Adding a group

To create a new group, enter the group’s name and click the ‘Create Group’ button.

After the group is added you can edit its permissions and add members.

Adding a user

To add a user, just enter the user’s email address and click the ‘Add’ button.
By default, the new user will be added to the Testers group.

Customizing Group’s members and permissions

To edit a group click the “Edit” link next to a group’s name
edit-group

edit-group

1. Adding a member to a group

You can choose to add a single member or a group to be part of another group.
Choose the name of the user or the group and click the ‘Add’ button.

2. Setting group’s permissions

Each group has its own permissions.
To set a group’s permissions, select or un-select the relevant permissions (look at the image above). When you finish, click the ‘Save Changes’ button.

3. Adjusting group icon color

You can adjust the color of your groups' icons to help you recognize them better in the system when entites are assigned to them.

Predefined Groups

There are three predefined groups in PractiTest.
You cannot set their permissions, but you can add or delete as many members as needed to the groups:
  1. Administrator – users under this group have the permissions to do everything within the system. If you can customize the Project settings and permissions (and see this screen), you are probably under the Administrator group.
  2. Testers – ‘testers’ do almost everything within the system. They behave like Administrators for Issues, Requirements and Tests, but their members do not have access to most project customizations such as Permissions, Custom Fields, Workflow.
  3. Developers – ‘developers’ have full grants for Issues -Create, Edit, View Issues and reports, but they may only view tests, runs and requirements; and cannot edit, comment on or delete any of them. Like testers, developers as well don’t have access to most Project customizations.
Notes:
– If a user belongs to more than one group, then its permissions are the Union of all groups permissions that she belongs to.
– If a user is removed from a project or account, the data created by them (issues, tests, etc) is not removed
– A user with permissions that are not included in the Developer license, will be billed according to Tester license plan