Skip to content

Toolora system documentation

Toolora is a multi-tenant operations platform for Swedish painting and service companies. It manages customer relationships, quotes, projects, work orders, time reporting and financial follow-up. Customer, worker and subcontractor interfaces provide access to the information each actor is authorized to use.

The documentation describes business rules, application components and operation. System architecture explains the browser and API data paths. Identity and access explains the authorization boundaries.

Area Scope
Purpose and boundaries Product responsibilities and environment boundaries
Landscape and architecture Components, data paths and external dependencies
Domain model and vocabulary Customers, projects, agreements and publication
Identity, companies and authorization Identity, company membership and resource authorization
End-to-end business workflows Commercial work, execution, review and settlement
User interfaces Office workspaces, portals and interaction states
Frontend implementation Routes, query state, mutations and browser configuration
API and application services Privileged operations, policy, contracts and services
Data model and database Records, RLS, transactions and schema changes
Files, documents and communication Storage, conversation audiences, originals and document intake
Finance and reconciliation Billing basis, deductions, payments, costs, time and reports
Integrations and shared services Accounting, mail archive and external outcome recovery
AI, assistant and MCP MCP contracts, authorized context and reviewed proposals
Background work and change feeds Schedulers, processing outcomes, checkpoints and stalled work
Import, history and data quality Source identity, historical replay, reconciliation and cutover
Security and information handling Trust boundaries, credentials, personal data and logs
Infrastructure and runtime Runtime services, configuration and release directories
Development, testing and delivery Local development, test levels, pull requests and publication
Monitoring, diagnosis and recovery Health, workflow diagnosis, recovery and incidents
Decisions, limitations and system status Source ownership, limitations, release status and evidence

Documentation coverage identifies the depth available for each area. The topic map records detailed subjects and their addresses. The continuation plan explains the proposed writing order. Evidence and coverage explains source revisions and scenario results. Authors follow Documentation structure and Writing style.

The static edition contains local navigation, search and diagrams. The archive’s README.txt explains how to serve it locally. Repository source links require separate GitHub access. Browser printing supports individual pages.