The layer under every module.
Roles and permissions enforced server-side, single sign-on, your branding on what a client sees, five interface languages, multi-currency, and an activity trail across the work your team does — the parts that decide whether software survives contact with a real team.
Not everyone should see the margins.
A travel designer, an operations coordinator, and a finance manager need different halves of the same booking. Sixteen permissions across eight areas — trips, library, suppliers, contacts, bookings, tasks, finance, settings — each split into view and manage, and every record scoped to your organisation before a query runs.
- Sixteen permissions across eight areas, each split into view and manage
- Checked on the request from a signed token, not hidden in the interface
- Single sign-on, plus email and social sign-in
- Members and invitations managed from settings
B2B invoicing with billing snapshot frozen at finalization.
Your name on it. Not ours.
Clients see your agency, not the software behind it. Set your logo, colours, and typography once and they carry across the web proposal in whichever of the three layouts suits the trip; generated documents carry your logo.
- Logo, colour, and typography set at organisation level
- Three proposal layouts, each fully branded
- Your logo on generated PDFs, vouchers, and invoices
- Partner branding alongside your own where you resell
Your team's language isn't the client's.
Your interface language and the trip's language are separate settings. A French team can build a trip that renders in German for a German client, and price it in a currency neither of them works in — with the exchange rate recorded so the number is defensible later.
- Interface in English, French, Spanish, German, or Portuguese
- Display language set per trip, used by proposals and PDFs
- Multi-currency across suppliers, quotes, and invoices
- Exchange rates recorded on the quote that used them
Who changed what, and when.
Activity is logged across the work your team does, so a disputed change has an answer rather than a theory. Your data stays yours: on request we tell you where it is hosted, and on termination you have thirty days to ask us to return it in a standard format.
- Activity trail across trips, quotes, bookings, tasks, invoices and documents
- Finalised invoices frozen against later edits
- Access control, encryption in transit, separated environments, backups
- Thirty days after termination to request your data back, per the Terms
Every generated document kept.
Platform questions.
Where is our data held?+
What happens to our data if we stop using Abrid?+
Can we restrict who sees pricing and margins?+
Do you support single sign-on?+
Is Abrid SOC 2 certified?+
Can Abrid connect to our accounting system?+
Questions we haven't answered here?
Book a call and we'll go through security, roles, and data handling against your own requirements.
No credit card required to start