Your workspace
API keys
Give an integration a key with the role you choose in each product. It trades the key for a short-lived token, and you can revoke it at any time.
Let your other systems work in OmexaOS, within limits you set.
- A role per product, so a key can do exactly what you allow
- Traded for a token that lasts half an hour
- Shown once; only a hash is stored
- Revoke at any time, and see when each key was last used
Least access by default
A key has no access until you give it a role in a product, and it can never manage people, roles or other keys.
Built to be lost safely
Tokens expire in thirty minutes, keys can be given an expiry, and revoking one stops it at once.
Never treated as a colleague
A key works through the API but never appears in staff lists or receives leads from routing.
Works well with
WebhooksTell your other systems what happens to a lead, as it happens.Your finance, timetabling or student system hears about a won lead automatically, instead of somebody rekeying it.Roles and permissionsPeople see and do exactly what their job needs.New staff are useful on day one and see only what their job needs, which is what data protection actually asks of you.Import and exportBring leads in from a spreadsheet, and take them out again.Move in without losing your history and take your data out whenever you want, so there is no lock-in to argue about later.