Decide exactly who sees what.

Kora has 229 permissions in 23 groups. Build roles that match how your organisation delegates, and the same rules apply to every list, report and search.

An engineer at a laptop in front of rows of server monitors.

Same record, two people.

A line manager sees a person's role, manager and leave. Pay and private details need their own permission, and even with it Kora asks for the viewer's PIN first. That includes Super Admins.

Line manager

AE
Amaka EzeSenior Analyst · Finance
Manager
Tunde Bello
Leave left
14 days
Salary
No access
Bank details
No access

HR, with pay access

AE
Amaka EzeSenior Analyst · Finance
Manager
Tunde Bello
Leave left
14 days
Salary
PIN required
Bank details
PIN required

Roles built from 229 permissions.

Fixed seat types like Admin, Member and Viewer can't express how most organisations delegate. In Kora you build each role from individual permissions, so the person who requests an invoice doesn't have to be the person allowed to issue it.

  • Performance31
  • Payroll24
  • Billing24
  • Recruitment13
  • Budget13
  • Business Development12
  • Inventory12
  • Vendors12
  • Kora AI11
  • Procurement10
  • Projects9
  • Employee Data9
  • Staff work7
  • Assets7
  • Holiday Management6
  • Ticketing6
  • Learning & Development5
  • Employee Relations5
  • Reporting4
  • Administration4
  • Attendance2
  • Helpdesk2
  • Operations1

The controls, one by one.

Sign-in

Admins decide how people get in. Each setting applies to the whole workspace.

Two-factor sign-in
Codes from an authenticator app, with one-time recovery codes as a backup.
Required for everyone
Admins can make two-factor sign-in mandatory.
Sign-in methods
Password, email magic link and Google, each switched on or off by an admin.
Company domain only
Accept sign-ins only from addresses at your own email domain.
Session timeout
A shorter timeout takes effect on the very next request.
Signed-in sessions
People can see where they are signed in and sign any session out.

Access

Roles decide what each person can open. Kora applies them when it fetches the data, so a hidden record never reaches the browser.

Project scoping
Without organisation-wide access, people see only the projects they are on the team of.
Reports follow the same rule
Reports filter by the same project access as the project lists.
Role changes apply at once
Editing a role clears its saved permissions, so the change applies on the next request.
No self-approval
Nobody can approve their own purchase request.

Data

Sensitive data gets extra protection. Every change leaves a record of who made it.

Encrypted employee fields
Private employee fields are encrypted with AES-256-GCM.
Encrypted connections
Tokens for Microsoft, Google, Slack and Zoom are stored encrypted with AES-256-GCM.
PIN for pay data
Viewing another person's pay or private documents needs a PIN. Repeated wrong PINs lock it.
Audit log
Every create, update and delete is recorded with who made it, their role and when. Secrets are removed before saving.

More reasons

Go through the controls with us

We'll build roles that match your organisation and show what each person can open.