Built so the right people see the right thing.

Hiring data is sensitive. pPULSE keeps it under role-based controls with audit trails and organisation-level isolation.

Five controls that decide who sees what.

Roles, MFA, organisation isolation, audit logs, and workflow controls. Each one is on by default, configurable per organisation, and visible to admins.

Roles and Permissions

Role-based access controls with configurable privileges. Every role defines who can view, move, approve, or make decisions on candidates.

  • Define who can view, move, approve, or make decisions on candidates
  • Stage-level visibility controls. Not every role sees every stage.
  • Permissions configurable per organisation

MFA and SSO

Strong authentication on every account. SSO for the orgs that prefer to centralise identity.

  • JWT and TOTP-based MFA
  • Google OAuth and Microsoft 365 OAuth SSO
  • Enforced MFA for admin and approver roles

Audit Logs

Comprehensive log of every action in the system, categorised by threat level and exportable on demand.

  • Comprehensive log of every action in the system
  • Exportable audit reports
  • Retention policy configurable per org

Workflow Controls

Guardrails on the hiring flow itself. Stage moves, approvals, and offer releases follow the rules you configure.

  • Approval gates before an offer goes out
  • Stage transitions restricted by role
  • Rules configurable per organisation

The essentials, at a glance.

The same controls, summarised: what is on by default and where your data lives.

Role-based access

Every screen and stage filtered by role.

MFA on accounts

TOTP-based MFA, enforced for admins and approvers.

Tenant isolation

Schema-per-tenant PostgreSQL, no shared tables.

Full audit trail

Every action logged with actor and timestamp.

Privacy by design

Access scoped to what each role needs, nothing more.

Ready to simplify your hiring workflow?

See pPULSE move a role from request to joining day, without the manual handoffs.