Documents in work context
Attach files to the customer, project, employee, learner, or transaction they support.
Files, documents, and e-signing
Evidence stays beside the decision it supports.
Built for teams that create, review, approve, or sign important work.
Attach clean files, comments, assignments, communications and reusable approval workflows to the underlying record with permission-aware history.
Already have a workspace? Log in
What changes
Find the right version quickly and preserve exactly what was approved or signed.
Attach clean files, comments, assignments, communications and reusable approval workflows to the underlying record with permission-aware history. The workflow remains permission-aware, reviewable, and available to both people and governed Schoolbooks AI.
Reusable approval paths
Route reviews by amount, type, team, or policy without rebuilding each flow.
Governed e-signing
Prepare recipients, monitor status, and retain signed evidence and timestamps.
Schoolbooks / Documents, approvals & audit Live workspace
Current outcome
Find the right version quickly and preserve exactly what was approved or signed.
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 documents, approvals & audit. Expand without starting over.
Continue exploring
Reporting & multi-workspace operations