Participants tab
Participants define who is involved in a project and what role they have in reviews. Use participants to control who can review code, vote on changes, and manage project activity.
To learn how to customize participants for a P4 Code Review project, watch this video or review the instructions following the video.
On this page:
Participant roles
Each participant is assigned a role that defines their responsibilities and permissions:
-
Owner - Has full control of the project, including configuration and deletion.
-
Moderator - Manages reviews, enforces workflows, and takes action on review activity.
-
Member - Participates in reviews and contributes changes.
-
Follower - Views project activity and receives notifications.
If you specify project owners, ensure you are included as an owner. If no owner is specified, ensure you are included as a project member.
Add or update participants
To add or update participants:
-
Open the project you want to configure.
-
Click Settings.
-
Select the Participants tab.
-
Add users or groups to the following project roles:
-
Members
-
Owners
-
Default reviewers
-
Changes take effect immediately.
Using groups
Add groups as participants instead of individual users to simplify management and maintain consistent access control:
-
Simplifies management for large teams
-
Ensures consistent access control
-
Automatically updates permissions when group membership changes
If a user belongs to multiple groups, the most permissive role applies.
Remove participants
To remove a participant:
-
Open the project you want to configure.
-
Click Settings and select the Participants tab.
-
Click the delete icon to remove the user or group from the participant list.
Removing a participant from the project does not automatically remove that participant from existing reviews. If a reviewer was retained through Retain default reviewers, review membership is updated only when Refresh Projects is run on the review.
Vote requirements
Control whether participants are required to vote on reviews.
For a user, set the vote requirement to:
-
Optional - The user can vote on reviews, but their vote is not required.
-
Required - The user must vote for the review to meet approval requirements.
For groups, configure whether one member’s vote or all members’ votes are required.
Workflows use vote requirements to determine whether a review can be approved.
Retain default reviewers
Enable Retain default reviewers to prevent default reviewers from being removed from reviews while the associated project branch remains in scope.
When enabled:
-
Default reviewers added by the project branch are retained on matching reviews.
-
Retained reviewers cannot be removed while they are still retained by an applicable project branch.
-
If project branch settings change, use Refresh Projects on the review to recalculate retained reviewers.
Then link to the more detailed default reviewer page if one exists.
Permissions and behavior
-
By default, project members can edit project configuration.
-
Administrators can restrict changes to project name and branch definitions.
-
A user’s permissions depend on their assigned role.
-
Participant roles influence how users interact with reviews.
For open projects, approval behavior differs. See Open projects.
Notifications
Use the notification options in the Participants tab to control when participants receive email updates.
You can enable the following options:
-
Email members and moderators when a review is requested - Sends an email to all project members and moderators when a new review is requested.
-
Email members, moderators, and followers when a change is committed - Sends an email to all project participants, including followers, when a change is committed.