Master data and record management
Vendors, customers, products and employees with controlled changes, duplicate checks and history.
Back office tools
Reconciliations, vendor records, approvals, data fixes: the back office runs on spreadsheets and admin screens nobody wants to maintain. Describe the tool and ToolJet builds it on your ERP, database and sheets, with roles, thresholds and an audit trail from the first version.
| Vendor | Change | Requested by | Status |
|---|---|---|---|
| Northwind Logistics Ltd | Bank account | AP · S. Ito | Second approval |
| Kestrel Energy SA | Payment terms 30 → 45 | Procurement | Approved |
| Bramble & Co | New vendor | Marketing ops | Awaiting documents |
| Helio Health | Address | AP · L. Novak | Approved |
Bank detail changes need two approvers from different teams and a callback note before they apply
Two-person rule, callback field and audit note added · awaiting your review
No engineering ticket needed
Type what you want in plain language. ToolJet generates the pages, queries and logic as a working app. Connect your data, set who can see what, and review the generated logic before publishing. Edit the app on the canvas afterwards.
Built on the systems your back office already runs
Have developers? They can build the same apps fromthrough the ToolJet plugin
Vendors, customers, products and employees with controlled changes, duplicate checks and history.
Match ledger, bank and processor data, assign breaks, track ageing to resolution.
Spend, credit, refund and change approvals routed by amount and risk, with two-person rules where needed.
Guarded edits to production records with approval before write and a full change log.
Owners, notice periods, values and reminders across suppliers and customers.
Close tasks, owners, due dates and sign-off with evidence attached.
SAP, Oracle, Postgres and Google Sheets connect once with scoped credentials. The tool reads and writes in place.
Thresholds, segregation of duties and two-person rules are part of the build, enforced by roles the platform applies.
Start with the process that hurts most at month end. Pilot with the team, refine on the canvas, then move to the next.
On Self-hosted, scheduled workflows chase approvals, flag ageing items and post to Slack or Teams.
In production
Controls auditors recognise
Back office tools handle money and master data. Role and row-level permissions, two-person rules and audit logs come with every app; self-host if the data has to stay in house.
Requesters, approvers and administrators on separate roles, with query-level permissions the platform enforces.
Platform audit logs plus the approval, rationale and before/after records your apps store.
SAML, OIDC and LDAP with directory groups mapped to roles; joiners and leavers handled automatically.
ToolJet Cloud, your VPC, on-premise or air-gapped. Credentials stay server-side.
Security and governance features vary by plan. Workflows and Agent Builder are available on Self-hosted only; BYOK is a Self-hosted Enterprise add-on. Compare plan availability.
Two ways to get there
Self-serve
Start free. Describe the tool, refine it on the canvas, and ship it under your own access rules. Start with one app, then test it with your team before rolling it out.
Start freeProfessional services
When the timeline is fixed or the process is tangled, our engineers build alongside you: scoped delivery, production-ready apps, and knowledge transfer so your team owns the result.
Talk about a projectYes. Writes run as guarded queries with scoped credentials, gated by roles and approval steps you define. Many teams start read-only and add writes once the process is proven.
Define separate roles for requesters and approvers and require a second approver for sensitive changes such as bank details. The platform enforces the roles; the app records who approved and why.
Yes. Describe the process and ToolJet generates a working app on your data; the team refines it on the canvas. IT connects systems and reviews permissions.
No. It builds the tools around it: the queues, approvals and corrections that today live in spreadsheets, while the ERP stays the system of record.
Yes. Self-host on Docker, Kubernetes, Helm or OpenShift in your own environment, air-gapped if required.
See it on your ERP data with an engineer.
Page updated