Skip to documentation content

Agiled Documentation

Roles and Permissions

Roles and Permissions

Roles describe a person's school responsibility. Permissions describe exactly what that role may do with a school resource. Together they keep student records accessible to the people who need them and unavailable to everyone else.

Available now. Last reviewed: 15 August 2026.

Predefined roles

Agiled includes School Admin, Principal, Teacher, Staff, Parent/Guardian, and Student roles. The School Admin has broad tenant-level access for one school. A School Admin cannot change the Admin role's permissions, which prevents accidental loss of administrative access.

Permission language

Resource

The type of record or feature, such as Users, Sections, Academic Years, Grades, Subject Allocations, or Documents.

Action

What the role may do, such as Read, Write, Draft, Submit, Issue, or Void.

Scope

Which records the action applies to. Tenant means the whole school; Classroom means assigned classes; Self means the user's own record.

Create a custom role carefully

Use a custom role when a real job needs it

  1. Open Roles & Permissions and create a role with a clear job title.
  2. Start with the smallest useful set of resource/action/scope permissions.
  3. Read the dependency hints in the permission matrix; some write actions require read access to the same resource.
  4. Save and test with a real user account before assigning the role widely.