Scoped permissions
Read and action access follows the user’s account, workspace, role, and object context.
Access is explicit; integrations do not become back doors.
Use scoped roles, deny rules, expiring API keys, device controls, MFA, audit evidence and tenant-safe search across REST, AI and MCP surfaces.
Walk through this workflowWhat changes
Use scoped roles, deny rules, expiring API keys, device controls, MFA, audit evidence and tenant-safe search across REST, AI and MCP surfaces. The workflow remains permission-aware, reviewable, and available to both people and governed Schoolbooks AI.
Why did fee income move this week?
Prepared answer
The movement is concentrated in two receipt batches and one approved fee adjustment.
3 linked records No entry changed
The workflow
Follow the work, not the org chart.
Each stage carries its evidence and status forward, so the next person receives context instead of another handoff problem.
- 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.
The friction this removes
- 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 that stay visible
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 boundary
Useful automation should make 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.