Tenant boundaries
School scoped records and actions remain isolated by institution, including across multi school networks.
Security
Every request answersthree questions.
Access in CurriculaIQ is decided by tenant scope, granted permission and reviewable action , in that order, on every request, for every role.
The access decision
Which school?The request begins inside a defined tenant or platform scope.Tenant
Which permission?Access follows granted responsibility, not a role name assumption.RBAC
Which action?Important administrative and data activity remains reviewable.Audit
Boundaries belong in the interface.
Tenant isolation and permission scope are not backend trivia. People need to see which school they are acting in and what their access allows, or they cannot be accountable for it.
Four assurance layers.
Each one is a design constraint the product is built against rather than a policy document written afterwards.
Access control
RBAC permissions align records and actions to responsibility rather than to a job title.
Data protection
Secure handling and encryption practices protect information in transit and at rest.
Operational resilience
Monitoring, backups, change control and response procedures support dependable service.
AI operates inside the same rules.
AI Sprout receives the school context and permissions the person asking already holds , nothing wider.
Scope
Permission aware context
Assistance is scoped to what the requesting person can already see in the product.
Accountability
Reviewable output
Drafted work stays visible as a draft so a person remains accountable for the decision.
Control
School controls
Schools decide which AI capabilities are enabled and for which responsibilities.
Need assurance materials for procurement?
Tell us which security, privacy or procurement documents your review requires and we will route it to the right person.