Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Log-in as a Staff Member.

...

Objects

Wellbeing Observation

Wellbeing Involvement

Wellbeing Action

[PosiEd] Mark a Roll

Allows the user to mark a roll of any class.

Objects

Session

Account (Lookup)

Bell Time (Lookup

Asset (Lookup

Event

Cohort Session

Cohort

Subject Offering

Timetable Structures

Products

Bell Times

Absence Submission

Timetable Periods

Absence Reason

 [PosiEd] Read Day Attendance

...

Objects

Cohort

Cohort Member

Cohort Schedule

Cohort Schedule

[PosiEd] PosiEd Logs

Objects

PosiEd Logs

Permission Set Groups

Add each permission set to each designated permission set group.

...

This will be the base permission for users of General Admin Staff users.

  • [[PosiEd] Edit Accounts

  • [PosiEd] Attendance

  • [PosiEd] Create Cohort/Members/Edit Cohorts

  • [PosiEd] Attendance Managementnt

  • [PosiEd] Mark a Roll

  • [PosiEd] Edit Cohort/MembersRead Cohort

  • [PosiEd] Read School Accounts

  • [PosiEd] Read Student Accounts

  • [PosiEd] PosiEd Logs

[PosiEd] Admin Leader

This will be the base permission for users of Admin Leader.

  • [PosiEd] Edit Accounts [PosiEd] Attendance Management

  • [PosiEd] Create Cohort/Members Edit Cohorts

  • [PosiEd] Edit Cohort/MembersCreate/Edit Kiosk Definition

  • [PosiEd] Create/Edit Timetable Structures

  • [PosiEd] Create/Edit Kiosk DefinitionEdit Accounts

  • [PosiEd] Log Wellbeing Observation

  • [PosiEd] Mark a Roll

  • [PosiEd] Read Cohort

  • [PosiEd] Read School Accounts

  • [PosiEd] Read Student Accounts

  • [PosiEd] PosiEd Logs

[PosiEd] Enrolment Staff

This will be the base permission for users of Enrolment Staff users

  • [PosiEd] Edit Accounts

  • [PosiEd] Create PosiEd Logs

  • [PosiEd] Mark a Roll

  • [PosiEd] Read Student Accounts

[PosiEd] Teaching Staff

This will be the base permission for users of Primary Teaching Staff and Secondary Teaching Staff users.

...

  • [PosiEd] Mark a Roll

  • [PosiEd] Read School Accounts

  • [PosiEd] Read Student Accounts

  • [PosiEd] Read Cohort

...

Automations Required for Sharing Rules Multi-School Setup

Not available yet

Sharing Rules

Account Sharing Rules

...

Asset Sharing Rules

...

Cohort and Cohort Assessment Sharing Rule

...

Day Attendance Sharing Rules

...

Kiosk Definition and Kiosk Reason Sharing Rules

...

Session Sharing Rules

...

PosiEd Log Sharing Rules

...

Wellbeing Involvement Sharing Rules

...

Design Considerations

  • Formula field is not supported in sharing rules

  • We can't use relationship fields in sharing rules

  • We can't use multi picklist in sharing rules

  • We can create a boolean formula field on an object where we can check if the logged-in user has the same school code on the viewed record but we don't have a way to get the updated value of that formula field when being recalculated

    • We could create a trigger on the same object to get the value of the formula field and duplicate that value to a text field but the record should fire an update action - which is not ideal.

  • We can only reference one public group in a single-sharing rule

    • This means we can't set both grade level and school public groups in one setup. If we create a sharing rule for a specific grade level that means it will enable all user under that public group to see records only in their designated level regardless of what school. If we create a sharing rule for a specific school this means all users can see data related to that school regardless of what grade level. We can only choose one or the other, not both.

  • We can only set a maximum of two restriction rules per object.

    • This means that it is not recommended to utilize this feature if a certain organization has more than 2 schools.

  • Restriction only supports one criteria and only supports limited field data types.