Planning domain

A planning domain gives an administrator a perimeter — the data they manage — and rights — the actions they can carry out on it. On an account that gathers several campuses, programs or institutions into a single timetable, each planner works on their own share.

As long as an administrator has no domain, they keep full access to the account.

The perimeter

The perimeter is described by dimensions, from the broadest to the finest: campuses and subjects on one side, then the timetable, its sites and their classrooms, its classes and their groups. Each dimension is constrained by a criterion — exact value, prefix, contained value, numeric threshold — and a lesson enters the perimeter when it satisfies all the constrained dimensions.

The rights

The rights say what the planner does with their perimeter: create, edit or delete the entities and the lessons, and, for fine-grained editing, the position on the grid, the teacher, the classroom, the modality, the videoconference link, the status, the duration, the comment and the generation. The principle is subtractive: everything is granted; you untick what the domain forbids.

Reading always stays open: a domain limits what is written, never what is seen.

Domain or custom role

A custom role decides which operations an administrator carries out — which modules, for viewing, editing or deleting. A domain decides which data they act on. Both can be given to the same person and complement each other.

Several domains

An administrator can be given several domains, each with its own perimeter and its own rights. They add up without merging: an action is allowed as soon as one domain covers it.