Settings & access

A secure foundation for your academy’s everyday work.

School storage

School records are saved in the app’s built-in key-value store, privately scoped to each signed-in account. Authentication and storage isolation are enforced by the platform.

A real relational database is a Pro feature. For a shared production school system, upgrade to Pro for a managed database, or connect your own Supabase project for free from the Database panel.

Current limit: staff and parent accounts do not share one school dataset. Do not use this account-isolated workspace as the school’s production system until a shared data layer is connected.

M-Pesa configuration

Add these server-only secrets in Functions → Secrets. Start in sandbox, then switch to production after Daraja approval.

MPESA_CONSUMER_KEY

MPESA_CONSUMER_SECRET

MPESA_SHORTCODE

MPESA_PASSKEY

MPESA_CALLBACK_URL

MPESA_ENV (sandbox or production)

MPESA_SIGNING_KEY (32+ random characters)

Use your registered HTTPS callback URL. Status is verified directly with Safaricom before a payment is marked completed.

Not checked

Permission guide

Administrator

All modules, school records, and owner-managed staff access.

Teacher

Attendance and competency assessment records.

Bursar

Fee invoices, payments, and expense vouchers.

Parent

Read-only private learner views and M-Pesa payment requests.

The owner assigns staff roles. Server functions check the authenticated account before approving mutations or initiating payments.

Staff login accounts

Owner-managed access, temporary passwords, and session revocation

Sign in to manage access

Only the academy app owner can create and manage staff accounts.