Workspace-level clarity
Keep teams, records, policies, and reporting relevant to each operating unit.
Multi-entity reporting
One view for the campus; a governed view across the group.
Built for multi-campus groups, operators, and leadership teams.
Use financial and operational reports by workspace, period, cost centre and dimension while account-wide roles retain deliberate boundaries.
Already have a workspace? Log in
What changes
Compare the organization without flattening the operating context of each workspace.
Use financial and operational reports by workspace, period, cost centre and dimension while account-wide roles retain deliberate boundaries. The workflow remains permission-aware, reviewable, and available to both people and governed Schoolbooks AI.
Comparable group reporting
Review consistent metrics across campuses, branches, or entities.
Deliberate central access
Grant group visibility without exposing every record to every user.
Schoolbooks / Reporting & multi-workspace operations Live workspace
Current outcome
Compare the organization without flattening the operating context of each workspace.
Evidence connected Permissions respected
How the work moves
A complete path, not another disconnected tool.
Each stage carries context and responsibility forward, so the next person receives a decision-ready record.
- 01
Set the context
Start from the organization, workspace, period, people, and policies that govern the work.
- 02
Capture once
Record the source event and evidence where it happens instead of recreating it downstream.
- 03
Review the exception
Keep the routine path fast while routing conflicts and incomplete evidence to a person.
- 04
Complete with history
Advance the workflow without erasing the earlier state, approval, or responsible actor.
Friction removed
- The same record is entered again when work moves between teams.
- Important context lives in private spreadsheets, messages, or memory.
- Managers can see a total but cannot follow it back to the decision.
- Automation often removes the review point instead of improving it.
Controls retained
Scoped permissions
Read and action access follows the user’s account, workspace, role, and object context.
Durable evidence
Source records, comments, approvals, and reversals remain available after completion.
Shared capability
The interface, REST API, AI tools, and MCP use the same server-owned business rules.
The AI boundary
Useful automation makes accountability clearer.
AI may
- Find permitted records and summarize the current state.
- Prepare drafts and proposed next actions.
- Explain exceptions and link the evidence used.
AI must not
- Bypass the current user’s permission.
- Approve its own restricted action.
- Invent missing operational or financial facts.
Ready when you are
Start with reporting & multi-workspace operations. Expand without starting over.
Continue exploring
Security, roles & integrations