TEJVONTechnologies Pvt. Ltd.
Back to Insights
Backend · Access control 1 min readOctober 2026

Super admin, teacher, editor: designing roles for a learning platform

A learning platform is run by several kinds of people. Getting their permissions right is most of what makes the admin side usable.

T

Surendra — Tejvon

Senior Android & BLE Engineer

A learning platform is not run by one person. On Indus Hindi there are super admins who manage the platform, teachers who work with learners, editors who look after content, and more. Each needs to do their job without being able to break someone else's.

We designed access around roles from the first day. Each role has a defined set of permissions, and every admin section checks those permissions on the server. Hiding a button in the interface is a convenience. The real rule lives where a user cannot bypass it.

Two decisions made this manageable. Permissions are attached to roles and never to individual people, so adding a new teacher is one assignment and not a checklist. And each admin section is built for the role that uses it, so an editor sees content tools and not platform settings.

The super admin area is deliberately strong. It is where roles are assigned and where the whole platform can be supervised, so it is also the most protected part of the system.

Role design is easy to postpone and expensive to retrofit. Deciding early who can do what shaped the data model, the API and the admin screens together.

Topics

BackendAccess control

Working on a similar challenge?

Let's discuss the architecture before you build.

BLE system design, OTA reliability, and connected product engineering — this is what TEJVON does every day.

Book a Technical Consultation