Talaan
A quiet server room with rows of racks and green status lights

Security

Payroll data, guarded like payroll data.

Every role gets its own password and session rules. Every record keeps its history. Every change to the database is in a snapshot within fifteen minutes.

3levels of visibility: all, unit, or own
15minutes between database snapshots
5failed sign-ins before lockout, by default
12months of monthly snapshots kept

Security policies

Rules per role. The strictest one wins.

A default policy covers everyone. A role that handles payroll can have tighter rules of its own, and a person holding two roles gets the stricter of each.

  1. 01Passwords checked before they are savedLength, character classes, reuse history and expiry, plus a list of breached passwords checked offline. The form shows the rules before you type.
  2. 02Sessions that endAn idle timeout, an absolute lifetime and a lockout after repeated failed sign-ins, each set per role.
  3. 03First sign-in changes the passwordA role can require a new password on first sign-in, and an admin's reset ends the account's live sessions.
TalaanDashboardSettingsMessages03AdminLogout
812918
HRIS Management
Parameter Management
Admin Management
RBACRolesUsersAuthorizationsData ScopesSecurity Policies
Manage - Security PoliciesYou are here:Admin ManagementRBACSecurity PoliciesSearch here ...
Displaying 1-4 of 4 resultsPDFEXCELNEW
RoleMin. LengthTwo-FactorLockoutIdle TimeoutAction
Filter...All...All...All...All...
Default8Optional5 tries30 min
HR Manager12Required5 tries15 min
Payroll Officer12Required3 tries15 min
Employee8Optional5 tries30 min
Talaan · All rights reservedDesigned & Developed By Tekhx
Security Policies, as it is in the productFigures illustrative

Who gets in, and from where

A stolen password is not enough.

Each check below is configured by you, and the ones that matter are checked again on every request, not only at the door.

2FA

Authenticator codes

Six-digit codes from an authenticator app, with recovery codes shown once. A role can make it required.

Per roleRequired

TERRITORY

Allowed countries

Limit a role to the countries it works from, checked at sign-in and on every request after. Empty means anywhere.

CheckedEvery request

IP

IP whitelist

Addresses an account may be used from, per user or for everyone, with IPv6, ranges and an expiry date.

ScopeUser or all

IDLE

Idle timeout

A session left alone too long signs itself out. Background refreshes do not count as activity.

SetPer role

LOCKOUT

Repeated failures lock

Too many wrong passwords and the account waits out a lockout before it can try again.

Default5 tries

LEAVERS

Access ends with employment

A completed separation switches the login off and kills every live session, so nobody walks out with a working account.

OnCompleted

Data scopes

Each person sees what their job needs.

Permissions say which screens and actions a role may use. Data scopes say which rows it sees on them.

  1. 01All, unit or ownA role sees every record, only its own unit and the units under it, or only the records assigned to or created by the person.
  2. 02Enforced on the serverThe scope narrows the list and the single record alike, so a link to someone else's record shows nothing.
  3. 03Permissions per actionViewing, creating, editing, deleting, exporting and approving are granted separately, screen by screen.
Hands holding a phone and a small security key beside a laptop

Kept on the record

Nothing changes without a trace.

Change history on every record

Every create, edit and delete is kept with who made it and when, and the History tab reads it back in sentences.

Two people, one record

If somebody saved the record after you opened it, your save is refused instead of quietly overwriting theirs.

Nothing deleted while in use

A record that something else still points at cannot be deleted, and the refusal says what is in the way.

Approvals on the record

One approver, every approving role, or a chain in order. Self-approval is a permission, not an accident.

Database snapshots

Every 15 minutes when something changed. Every snapshot kept for 48 hours, then one a day for 30 days and one a month for 12, and verified on a schedule.

Yours to keep

You own the source code, the API and the database, so your employee data stays where you put it.

A specialist in a headset smiling while she works at a laptop

See it working

Run one cutoff with us.

Bring a payroll you already know the answer to. We load a sample of your employees and compute it in front of you, then you decide.