Administration: the platform stays yours.
A business application that needs its vendor to add a status or an equipment class becomes a dependency. Here, whatever belongs to your organisation is set from the interface.
Users, roles and scopes
An account carries a role and a scope. The role says what you may do; the scope says what you may do it to. A branch manager administers his branch without seeing the others; management sees everything.
| Role | What they can do |
|---|---|
| Technician | Their round, their jobs, recording on site and signing the order |
| Dispatch | Create, qualify, assign and track the tickets in their scope |
| Project manager | Steering a portfolio of customers, projects and teams |
| Commercial | Customer records, quotations, invoices and payments |
| Management | Consolidated read access across every entity and every report |
| Read-only | Consultation, with no write form displayed at all |
A missing permission is not a greyed-out button. When a role may not write, the form is never produced. That is a difference of design, not of display, and it is what holds up against somebody editing an address by hand.
What you change without calling us
Statuses and deadlines
Your statuses, and for each one whether it pauses the contractual clock. This is the setting that determines your figures.
Work types and equipment
Types of work, equipment classes, and the procedures attached to each.
Customers and contracts
Deadline commitments by customer and by priority, which drive the due-date calculation when a ticket is created.
Document templates
Header, wording and footer of the work order, the quotation and the invoice. Your logo, your legal mentions.
Audit log and notifications
Write audit log
Every creation, change and deletion is recorded with its author, its date, and the value before and after. A ticket’s history does not get rewritten.
Activity log
The sequence of actions taken in the platform, by user and by date. It is the first thing you look at when a value moved and nobody knows why.
Internal notifications
Mentioning someone by name in a comment alerts them inside the platform. No outside messaging service is needed for information to move.
Operational alerts
Deadline approaching, ticket with no assignment, stock threshold reached: the signals surface where the work happens.
See the platform run on your own cases
An hour is enough: you open a request, assign it, close it and print the signed work order. Then we look at how your operation fits in: your customers, your sites, your contractual deadlines.