
Build roles from individual permissions, grant them for a company or department with start and end dates, enforce MFA, and keep a change history on every record.
She gets the role’s permissions on that department only, from the start date. Until then the grant shows Starts on Dec 1.
How Mesabrook controls who sees its financial data.
Access roles carry permissions: Executive can read everything, Department Manager runs a department, and Finance and HR manage their own areas. Job titles never grant access.
Can see and change everything in the workspace.
Read and export everything across the organization. No write or admin.
Full operational control of a department: activities, timesheets, invoices, purchases, team.
Financial resources including writes: invoices, purchases, payments, statements, exchange rates.
People resources including writes: employees, contracts, leave, evaluations. Cannot delete employees.
Describes what someone is. It cannot carry permissions.
Choose read, write, approve, delete and export for each module. Deal permissions can be limited to your own deals, your team’s or all deals. KPilot shows who gains or loses access before you save.
See who uses a passkey or an authenticator app, require MFA for an account, or end all of its sessions. Each person manages their own sign-in settings.
Every record keeps a history of who created it, what changed and when. Roles, access grants, exchange rates and workflows keep their own history.
Pick the domains KPilot is allowed to email. Messages to other addresses are held back and listed with the reason. Each customer has its own environment and database.
Each person can see what they can do, where, who granted it, and which approvals come to them.
You have access to Platform Engineering & Operations and to Mesabrook Nearshore, read only.
Yes. Grant the role on the department: every screen, report, brief and Orkestra answer is limited to it by the server.
Yes. Every grant has a start and an optional end, and shows Starts on or Ends on until then.
Yes: passkeys, authenticator apps and Microsoft sign-in through Entra ID. An administrator can require MFA account by account.
Yes. Your access says, in plain words, what each person may do, where, who granted it, and which decisions arrive for them.
Each customer runs in its own environment, with its own database. Email leaves it only to the domains you allow.
Start with Mesabrook’s roles, or set up your own.