SI ASHA OS

Clear access. Shared responsibility.

Si Asha OS checks permissions on the server before reading or changing internal records. Each school’s records stay within its authorized scope, while assigned Country and Foundation leadership can provide oversight.

Protecting your account

Passwords are stored as salted hashes. Sessions use random tokens and an HttpOnly cookie. Sign in with your email and password. New signup accounts receive no Foundation or school access until an administrator verifies the request and assigns scopes and roles. The separate local test accounts are clearly labeled and cannot sign in to production. Sign out when you finish on a shared device and keep your password private.

A traceable history

Operational changes create audit events. Document revisions keep earlier versions. Messages and read acknowledgements are tied to their author.

Development status

This instance is for development review. Hosted security configuration, recovery, backup procedures, approved user provisioning procedures and operational review must be completed before production use. Private staff file uploads are available with encryption, file-type checks, permission checks and logged downloads. Production malware scanning and managed key protection remain to be configured. AI access is not enabled.