Scenario
As an admin or site owner, you want to automate the membership of a mentorship program — for example, making everyone with a "Senior Engineer" title a mentor in an engineering mentorship program, or making every new hire a mentee in a buddy program.
Solution
Make sure a People Segment exists for the people the rule should affect.
For more on segments, see How to use dashboard segments.Make sure the target mentorship program exists.
For more on creating mentorship programs, see How to create mentorship programs.Create a new automated rule with Add/remove users to a mentorship program as the action.
For the full procedure, see How to create an automated rule.Configure the action's fields:
Add or remove — whether the rule adds people to the program or removes them.
Mentorship Program — the program to add or remove people from.
Mentor or mentee — the role the rule manages within the program.
Click Publish.
The rule runs on its scheduled cadence, adding or removing the people in the segment to or from the program in the configured role.
Go deeper
Mentor and mentee are separate roles
A single rule manages a single role within a program — either mentor or mentee. To populate both roles for the same program, create separate rules.
Add and remove are separate rules
A single rule can either add or remove. To bidirectionally manage a program's membership — adding people when they enter a qualifying state and removing them when they leave — create two rules:
An Add rule whose segment matches everyone who should currently be in the program in that role.
A Remove rule whose segment matches everyone who should not be in the program in that role.
The two rules typically operate on disjoint sets of people, so order on the Automated Rules dashboard does not usually affect the outcome. If your Add and Remove segments overlap, expect ordering to matter — see Reference: How automated rules run for ordering mechanics.
Skip behavior
The rule checks each person's current state before acting:
An Add rule skips people who are already in the program in the specified role.
A Remove rule skips people who are not in the program in the specified role.
This means the rule is safe to leave running indefinitely; people in the desired state are not re-processed on every run.
Combining with manual program assignment
The rule operates on program membership globally — there is no distinction between memberships added manually and memberships added by rules. An Add rule skips people who were already added manually; a Remove rule revokes membership from anyone in the segment, regardless of how they originally joined.
If you need to preserve manually-managed program memberships, do not use an automated Remove rule on the same program and role. Alternatively, limit the Remove rule's segment so that manually-managed people don't match.