Institutional structure
Advanced trust-school-campus governance requirements: inherited policy and recorded local exceptions, subject to scoping
SquareCampus EnterpriseRun every campus.
Run every campus.
Govern them as one.
For trusts, school groups and standalone institutions with deeper governance, identity or audit requirements. Define central policy, campus accountability and the controls your institution needs in one agreed operating scope.
The licensing model is published on the pricing page; figures are issued in a written proposal after institutional discovery.
Institutional governance
One institutional policy
Identity · Authority · Audit requirements
Campus A
Local scope
Campus B
Local scope
Campus C
Local scope
Central governance. Defined local responsibility.
Illustrative governance model. The proposal confirms available controls and deployment scope.
The Enterprise dimension
Institutional governance, across the operating model.
Enterprise is selected for the governance requirement. Discovery establishes the available capabilities, institutional boundaries and delivery scope for each dimension.
Command
Trust-level command-view requirements, scoped against available reporting capabilities
Governance
Advanced approval and exception-ownership requirements across workflows and campuses, scoped during discovery
Identity
Identity governance: multi-directory requirements, group-to-role mappings, SSO enforcement policy and lifecycle controls, scoped during discovery
Auditability
Advanced policy controls and audit-export requirements; institution-owned data and supported portability apply to every plan
Intelligence
Governed AEGIS access requirements and allowances, confirmed against available capabilities
Deployment and integration
Managed cloud, private-cloud or on-premises eligibility, enterprise integrations and implementation governance
This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when.
Identity and authority
Institutional sign-in. SquareCampus-governed access.
The identity provider establishes who a person is. SquareCampus decides what that person may do: institution membership, campus scope, roles, workflow privileges, record access and operational permissions are governed inside SquareCampus and are never derived from an email address or domain alone.
Enterprise is differentiated by identity governance rather than by having SSO. Identity requirements across several campuses or directories, directory-group to role mappings, SSO enforcement policy, joiner-mover-leaver lifecycle controls, identity migration and identity audit controls are scoped as Enterprise requirements during technical discovery.
Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation.
Standard sign-in authenticates identity only. It does not require access to email, files, Teams, SharePoint or other Microsoft 365 data.
Review identity and accessYour Microsoft environment
Stays under your administration
- Your administrator approves SquareCampus in your Microsoft Entra ID tenant.
- Staff sign in with their existing institutional Microsoft accounts.
- Your MFA, Conditional Access and user-assignment policies continue to apply.
SquareCampus authorisation
Governed inside the School OS
- SquareCampus validates that the sign-in came from your approved tenant.
- It resolves the person's institution membership and campus scope.
- It applies role, record and workflow permissions defined in SquareCampus.
- A secure SquareCampus session is issued.
Available separately on any plan
Microsoft Entra ID verifies who the user is. SquareCampus determines what the user may access and perform. Single sign-on is chosen by the institution, never required.
Chosen by requirement
Enterprise control is not reserved for large institutions.
Enterprise is selected by governance requirement, not merely by enrolment. A standalone school may require institution-managed identity, advanced approvals, executive visibility, stricter auditability or governed intelligence even without operating a large campus network.
Identity governance beyond single sign-on: enforcement, group-to-role mappings, lifecycle
Deeper approval chains and exception ownership
Board or trustee command views
Stricter access governance and audit exports
Most institutions are well served by Starter or Pro. Enterprise exists for institutions whose governance, identity or audit requirements genuinely sit above them — not as a safer version of the same product.
The shared foundations
A complete core. A common security baseline.
Every plan starts with the core
Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise.
Starter, Pro and Enterprise support multi-campus operations with campus-level administration and role-aware workflows. Advanced centralised institutional governance is a separate dimension; campus count alone does not require an upgrade.
Implementation and support are included in every plan, and every institution gets the same rollout: there is no paid fast track. SquareCampus is designed to need little or no training. Only a custom SLA, such as 24×7 cover or guaranteed response times, is quoted.
Institution-owned data and defined terms
Tenant isolation, secure authentication, role-based authorisation, protection of institutional records, essential security logging and privacy safeguards are baseline requirements in every plan. Advanced identity governance and expanded audit controls are separately scoped; fundamental security is not a premium feature.
The institution owns its institutional data in every plan. We earn continued adoption through operational value, with supported data exports and documented offboarding rather than artificial lock-in. Export scope, available formats, access arrangements and assistance are confirmed for the deployment; retention and deletion follow the agreement, the DPA and applicable obligations. Export formats and timing are established before commitment.
Your plan does not determine your legal retention obligations. Storage and archive arrangements are specified in your proposal and order form. How retention works
Define the operating scope
Bring the governance question.
Share your campus structure, identity requirements, approval boundaries and audit expectations. We establish the supported scope and deployment responsibilities, then document the commercial terms in a written proposal.
Everything optional is priced in the proposal before you sign, and usage beyond the allowance is prepaid, so the proposal you sign is the bill you get.