HumaRun is loading.
Skip to content
Security

Access follows responsibility.

Keep each organization's records apart, give every person only the access their role needs, and see each security setting as it truly is.

All modules
Security settingsConcept · sample
Illustrative
  1. Multi-factor authenticationAuthenticator codes and an organization policyOptional
  2. Single sign-onSAML 2.0 or OpenID Connect on verified domainsOptional
  3. Session timeoutEnds after eight hours, or 30 minutes unusedIn force
  4. Audit trailWho changed what, and whenIn force
  5. Privacy toolsData packages, corrections, consent and erasureAvailable
  6. External AI modelsHumaRun uses no external AI modelNot used
Sample figures, not a live screen

Four layers of protection, each one plainly stated.

What protects your organization's records, and how.

Organizations kept apart

Each organization's records are separate from every other organization's, and each person works within the records and actions of their role. Salary, bank details and restricted HR notes each need a permission of their own.

Audit history

Changes to records, approvals and payroll are kept with who made them and when, and people with the audit permission can export that history. The database itself refuses any edit or deletion of it.

Sign-in protection

Sign-in can ask for a code from an authenticator app, a session left unused for 30 minutes ends, and members can continue with Google or use single sign-on on your verified domains. With multi-factor sign-in on, payroll finalization, payroll payment approvals, exports of employee, report or audit data and changes to roles ask for a fresh code.

Privacy tools

A person downloads their own data package and asks for corrections, consent is recorded for the purposes you define, a second reviewer applies an erasure under your organization's own retention rules, and privacy incidents are kept in a register with their deadlines.

Every security setting, as it truly is.

The security overview shows each setting as it truly is and links to the page that changes it. Only people who manage the organization or its members can open it.

Security settings in HumaRun: every setting with its current state, with invented sample data.
A real HumaRun screen, shown with invented sample data.

Who can do what to which settings.

Each person looks after their own sign-in; every setting that reaches other people needs a permission of its own.

Your security settingsWhat each role may change
Illustrative
What an employee, an administrator and an organization owner may do with the security settings
EmployeeOwn accountAdministratorGranted permissionsOrganization ownerWhole organization
Protect their own sign-inAllowedAllowedAllowed
See the security overviewNot allowedNeeds its own permissionAllowed
Change roles and member accessNot allowedNeeds its own permissionAllowed
Require multi-factor sign-inNot allowedNeeds its own permissionAllowed
Set up single sign-on and SCIMNot allowedNeeds its own permissionAllowed
Export the audit historyNot allowedNeeds its own permissionAllowed
AllowedNeeds its own permissionNot allowed

What this module covers.

What works today, and the controls that come with it.

Included

  • Roles and scopes that decide which records and actions each person reaches
  • Dated delegation of the approvals assigned to a person, to a colleague with the same authority
  • A history of changes to records, approvals and payroll, with who made each one and when, exported by people with the audit permission
  • A security overview of each setting as it truly is, for people who manage the organization or its members
  • An alert when your account signs in from a new device, and a way to say it was not you, which ends that sign-in
  • Continue with Google for sign-in and sign-up, linked by the provider's own account identifier and never by email address alone
  • A privacy incident register, kept without edits or deletions, that tracks each notification deadline and asks for the reason when one is late
  • A preview of who gains or loses each permission before a role changes, with separation-of-duties warnings, and every role version kept and restorable
  • Role assignments with a start, an expiry and a review date, and recorded access reviews
  • Privacy requests for access, correction, portability, restriction, objection or erasure, recorded and decided by your privacy reviewers
  • Sign-in with an authenticator app code and recovery codes, and a policy that requires it for everyone or for chosen roles
  • A fresh code, entered within ten minutes, before payroll finalization, payroll payment approvals, exports of employee, report, payroll or audit data, compensation money approvals and changes to roles, members or sign-in settings
  • Sessions that also end after 30 minutes without use, and a list of your own signed-in devices to sign out one by one
  • Signing out another member's device, with a recorded reason
  • Single sign-on with SAML 2.0 or OpenID Connect, including Google Workspace and Microsoft Entra ID; your administrator tests the connection before switching it on, and accounts are never created automatically at sign-in
  • Verified domains, SCIM provisioning and an SSO-required rule that keeps a break-glass owner
  • The database itself refusing any edit or deletion of the audit history
  • Corrections, and consent for the purposes your organization defines
  • A personal data package that each person downloads for themselves within seven days
  • Erasure applied by a second reviewer, only under a retention rule your organization recorded, after employment has ended and with no legal hold
  • Uploaded files encrypted in each organization's own folder, and served only after a clean malware scan
  • National ID numbers and IBANs sealed with a data key before they are stored

Controls built in

  • Each organization's records kept apart from every other organization's
  • Salary, bank details, restricted HR notes and sensitive documents, each on a permission of its own
  • Passwords stored as salted scrypt hashes, with every session signed out when a password changes
  • Sessions that end after eight hours or at sign-out

Tell us who needs access, and to what.

Tell us how your team handles access in a free demo request.