Admin console
Set the rules once
Administrators manage people, roles, settings and integrations in their own app, separate from the portal. Every sign-in needs an authenticator, and every change is written to the audit log.
Accounts and invitations
Invite people by email, set roles, designations and home offices, suspend and reactivate. Suspending ends every session at once.
Roles you can edit
A role is a bundle of permissions, each with a scope: own, team, region or the whole organisation.
Per-person exceptions
Allow or deny a single permission for one person. A deny always wins, and the page shows their effective permissions.
Authenticator required
Every console user signs in with an authenticator app code, with ten single-use recovery codes for a lost phone.
Settings by section
Working hours and tracking, modules, prospecting limits, reports, tiers, commerce and the inbox, each saved on its own.
Audit with before and after
Every administrative change records who, when, from where and the field-level difference. Filter it, or export a date range.
What the console shapes
Set in the console, felt in the portal
The console has no field screens of its own. These are the portal screens its settings decide.
Roles decide what people see
A person's role and exceptions decide their navigation and their reach. A manager sees their team; a rep sees their own.
Offices and their circles
Pin each office on a map with a geofence from 25 to 5,000 m. Office check-ins then show the office, the distance and inside or outside.
Integrations switch features on
Connect Gmail and Outlook sign-in, an AI service or Odoo, and switch the inbox module on. Until then the portal says what is missing.
Commerce and the tax issuer
Set the legal name, VAT number and seller's address, and choose who issues tax invoices: Zaps, or Odoo with its Saudi e-invoicing.
The specifics
How control is kept safe
- 01No escalation
- Nobody grants a permission or scope wider than their own, or assigns a role ranked above theirs. The console disables those choices before you save.
- 02Always one administrator
- The organisation always keeps at least one active administrator, and reporting lines cannot loop.
- 03Secrets entered, never shown
- Integration keys go into a field that is never pre-filled and are encrypted at rest. Afterwards the console shows only the last four characters.
- 04Integrations with a test
- Odoo, email and calendar sign-in, AI routing, prospecting sources and wallets each have a Test that reports the service's answer.
- 05Tracking with consent
- Working-hours tracking is on or off, with a point interval of 60–300 s and retention of 1–365 days. Each person's consent is always required.
- 06Billing in the console
- Your plan, users billed, status and the next invoice estimate. Invoices download as PDF in English or Arabic, with Pay now on open ones.
longest console session before signing in again
permission scopes: own, team, region, organisation
single-use recovery codes per authenticator
A separate app, on purpose
Administrative permissions exist only in console sessions, so a lost phone signed in to the portal cannot manage anyone. The console hides what you may not do, and the Zaps API refuses it regardless.
Questions
Who can use the admin console?
People whose role carries administrative permissions. A manager without them is refused, and every console user must set up an authenticator on first sign-in.
Can we see who changed a setting?
Yes. The audit log shows the person, the time, the session and the before and after of each field, and exports a date range as Excel or CSV.
Can we add our own domain and logo?
Yes. Workspace & branding sets your display name, colour and logo, and custom domains are verified through DNS records, within your plan's allowance.
See your team's day, the way it happened.
A 30-minute walkthrough on your own process: visits, journeys, quotations and the inbox, in Arabic or English.
14 days free · No card needed · Launch prices from 39 SAR