...
By person - eg. Fred Smith isn’t allowed to be rostered to events
By type of person - eg. All volunteers
By event-type - eg. All festivals
A restriction can be setup to only allow those types of events (eg. Trainees (a type of person) can only attend Training events (a type of event)
By event teams/positions - eg. Any time someone’s rostered as a Team Member
A restriction can be setup to only allow those event teams/positions (eg. Trainees (a type of person) can only attend events as an “Observer”)
By client - eg. Fred Smith isn’t allowed to be rostered to ACME Inc’s events
By venue - eg. Fred Smith isn’t allowed to be rostered to events at the MCG
By length of shift - eg. No-one can be rostered onto shift for more than 12 hours
...
A new recruit, John Smith cannot be rostered more than 2 hours to events
No-one can be rostered to attend events associated with ACME Inc for more than 10 hours at a time
Volunteers (a type of person) can only attend Training events
Volunteers (a type of person) can only attend Training events, if that event is assigned to “ACME Inc”
When setting up rostering restrictions, all of the criteria entered is taken into account when evaluating if a restriction should come into effect or not - eg. if both Member Type, and Event Types, and Client, and Venue are completed, then all of those must match in order for the restriction to be shown.
Leaving a field blank (eg. Client) means the restriction applies to events assigned to any client.
The option to either warn users, or prevent rostering (as shown below) is available.
...