Keep tenants separated
Organization identifiers and server-side checks scope supported records to the authenticated tenant.
Protect access and serve Quebec
Keep organization data scoped while teams and customers work in English or French.
Serberus combines organization-scoped routes, server permissions, protected authentication and private file access with English and French administrative, technician and key public workflows. Security remains an ongoing operating practice, not an absolute guarantee.
Owner controlRules and results stay visible✓
01Organization-scoped routes and server permission checks02Password hashing, session revocation and optional SMS 2FA03Encrypted secrets, validated webhooks and hashed public tokens04English and French admin, technician and key public flows
What is already in the product
The details that make the workflow useful in real operations.
Enforce permitted actions
Role and technician-scope checks run on the server for supported routes rather than relying only on hidden buttons.
Protect authentication state
Password hashing, signed authentication tokens, token-version checks, password reset and session revocation support account control.
Add a second factor
Organizations can use optional SMS two-factor authentication for supported sign-in flows.
Protect secrets and files
AES-GCM encryption supports organization secrets, while private storage and signed URLs limit supported photo access.
Operate in English and French
Administrative, technician and key customer-facing workflows support both languages, with continued review required for new and less common artifacts.
How the handoff works
Your rules define the guardrails. Serberus carries the routine work.
Every major workflow answers the same five questions: what starts it, which rules apply, what Serberus completes, when it asks, and where the result remains visible.
Trigger
A user signs in, requests an organization record, opens a protected link or selects a language.
Rules
You configure roles, technician scope, optional two-factor authentication, integration secrets and language preferences.
Serberus does
Serberus validates the supported request, applies scope and permission checks, then presents the available localized flow.
When it asks
It asks for stronger authentication, renewed access or administrator action when a protected operation requires it.
Where you see it
See access and language outcomes in account controls, role settings, protected records, audit context and Sentry monitoring.
From office to field
The context travels with the work.
The same request, schedule, customer details, photos, notes, status, and next action stay available as work moves from the office to the site.
Real product screen
Built into Serberus, not staged for the website.
This image comes from the current Serberus application. Interface details may evolve, but the workflow shown here is part of the product surface audited for this site.
Serberus
Put the handoffs somewhere dependable.
Serberus does the heavy lifting, brings the exceptions back to you, and keeps the result visible.