Role-based permissions
Every role in Raqeem — administration, teacher, parent, student — has precisely defined permissions. Parents see only their children, teachers only their classes, and students only their own data.
One principle governs the platform: every user sees only what concerns them, and enforcement always happens on the server.
Every role in Raqeem — administration, teacher, parent, student — has precisely defined permissions. Parents see only their children, teachers only their classes, and students only their own data.
Each institution's data is fully isolated from the others. In branch networks, permissions are defined per institution, with precise administrative scopes inside each one.
Resources and attachments are protected by the same permission rules, so only those entitled to them can access them.
Every request is verified on the server before it is executed. The interface does not decide permissions — it only reflects them.
Permissions in Raqeem are based on role and scope, and they are always enforced on the server.
Request a live demo and see how Raqeem brings your institution together in one ecosystem.
Request a demo