TAC HRTAC HR
The lobby of a large company headquarters with employees moving through
By company size

HR Software for Large Companies

Permissions scoped by branch and department, isolation of each company's data, and a read API and signed web notifications for the systems you connect

A large company does not only ask about attendance, but about each manager's limits, about separating each company's data, and about linking HR to the systems it already has. TAC HR answers with permissions scoped by branch and department, isolation of each company's data, and a read API and signed web notifications for partners and developers.

Today's reality

What happens in a large company without clear limits

  • 01Companies and branches multiply and responsibilities spread, so it is not enough for a user to be a manager: the system must know which branch and which department they see
  • 02An internal auditor asks who changed what and when, and people search through messages and copies and find no clear trace
  • 03The company's other systems need staff and attendance figures, so they are copied by hand from reports and arrive late and out of line
  • 04Hundreds of employees' data is moved from scattered files, so a broken row enters the database and is only found after payment
  • 05Information security requires that sign-in is governed, the device is bound and backups are encrypted, not just promised
With the platform

What changes with large scale

  • Permissions by branch and department

    The company creates admin groups with their permissions and gives each account a scope of one or more branches or departments, so an HR officer sees only their branches' staff and a payroll accountant the run they review.

  • An audit log of every change

    Every change passes through one audit entry point with who made it and what it was before and after, and management and the internal auditor review it from the activity screen.

  • Isolation of each company's data

    Each company's data is isolated from the others, a session claiming a company other than its owner's is rejected, and every admin account is bound to its own company so it cannot see another company's data.

  • A read API

    Scoped keys read employees, attendance and a payroll summary. They are stored only hashed and shown once, and the company is taken from the key, not from the request.

  • Signed web notifications

    Events reach you when they happen with a signature that covers the timestamp, so an old call is not replayed, on an https address alone, so you update your system without asking each time.

  • Sign-in and backup security

    A sign-in attempt limit stored in the database, device binding that is strict by default for everyone, and encrypted database backups in separate storage.

Inside the platform

Answers to the questions HR, finance and information security teams ask

A large company asks questions a small business does not: who sees what and why, how we prove who changed what, how our figures reach our other systems, how we make sure our data does not mix with anyone else's, and what happens to our backups. This page answers each of them with what TAC HR actually does and what it does not, so HR, finance and information security teams can carry it into the decision meeting without reading between the lines.

01

Who sees what

An admin account is given a scope of one or more branches or departments, and branch and department combine with an or: whoever is assigned to the Jeddah branch and the Finance department sees the staff of either. An empty scope means the whole company, which belongs to the holder of the full permission. The company creates admin groups with their permissions and copies, edits and deletes them, so each manager gets what belongs to their screen and action. Run visibility is a separate choice: all admins with the permission, or only the approval chain's members, its creator and the system admin, and the payment permission does not bypass it. Every change goes through one audit entry point with who made it and what it was before and after, so what left no trace did not happen.

02

Several companies and data isolation

One account may hold several companies, and each company has its own commercial registration, its number with the Ministry of Human Resources and its payroll IBAN, so the wage file comes out under its own header. Each admin account is bound to its company, and the session takes its authority from the live row, not from the cookie alone: a payload claiming a company other than its owner's is rejected, and an account with no company inside a multi-company account is not guessed a company but has its session rejected. Each company's data is isolated from the others in every query. What needs a unified view of several companies on one screen is not something this page promises.

03

The read API

Keys are created with scopes from three: read employees, read attendance and read the payroll summary. A key is stored only hashed, not encrypted, so we can never read it, and it is shown once at creation, and whoever loses it revokes it and creates another. Its scope is read from its row, not from the request, and the company is taken from the key, not from the request either. There are no pay fields in the employee read. The request limit is 120 a minute per key. It is read-only, so your external system pulls and does not write. As for accounting, the export is a journal entry file with your company's account codes that you import into your software.

04

Web notifications and import

You register an address that receives six events: employee created, employee terminated, request approved, request rejected, payroll paid and punch rejected. Rejection is an event like approval, because an outside system waiting on a decision is not helped by knowing only about approvals. The signature covers the timestamp, not the body alone, so whoever captured an old call gains nothing by replaying it a month later, and the address is https only. In import the system reads a file of up to five thousand rows and checks each row on its own with a preview before any write, so a bad row does not sink the whole file, and nothing is written until the admin confirms.

05

Security and continuity

The sign-in attempt limit is stored in the database, not in the memory of one instance, so it is not bypassed by reaching another instance, and a legitimate user is not locked out: the counter clears at the first successful sign-in. Device binding is strict by default for everyone: signing in from a phone other than the bound one is blocked and a device change request is shown to management. The app rejects spoofed locations, emulators and modified devices before every punch. Database backups are uploaded only encrypted with a private key to a storage container for backups alone, and decrypting them is measured by a test that encrypts, then decrypts, then compares the bytes, because a backup that does not decrypt is not a backup.

Inside the interface

The run as finance reviews it along its approval chain

HR Software for Large Companies
The users and permissions page with a list of accounts showing each user's role, department, branch, status and last sign-in date, and in front of it a cost centers card split by department with each department's share of the total payroll due
The right services

The eight services on your company's structure

All services
An operating day

How the rollout is built on your company

  1. 01

    Defining the structure

    Admin groups are created, each manager gets their scope of branches and departments, and the approval routes for each request type and the automatic approval limits are set

  2. 02

    Moving the data

    Employee files are imported with a preview of every row before saving, so a broken row never enters the database, and app accounts are created from the employee files, each employee told their password

  3. 03

    Running and connecting

    Read keys are created with their scopes and web notification addresses are registered, so your systems receive signed events as they happen

  4. 04

    Review

    The internal auditor reviews the activity log, finance reviews the run along its approval chain, and information security reads the security page

The numbers

The limits your systems read

Limits set in the system itself that the test reads from their source, not approximate figures. The effect of the platform on your company is something you measure after rollout.

3 scopes
The scopes of a read key: employees, attendance and a payroll summary, and the key's scope is read from its row in the system, not from the request, because a key that says what it can do is not a key
6 events
Reach your systems signed: employee created, employee terminated, request approved, request rejected, payroll paid and punch rejected, so a rejected request does not stay pending at an outside system
120 requests
The API limit per minute for each key, so a repeated call does not choke the system, and what is above the self-serve size in employees or reps is offered through the sales team

Limits of what the platform offers large companies

The API is read-only, so it does not write into the system, and it reads employees, attendance and a payroll summary with no employee pay fields. Connection to accounting and resource-planning systems is through an API, web notifications and a journal file, not a ready connector for each system. Every admin account is bound to one company. The wage file is a detailed table that comes out after the checks and is not sent to any body, and GOSI is calculated and not paid from the system. The system does not decide what approvals your company's policies require, so you set them. The mobile app is for employees, and management is on the web in Arabic.

Industry questions

What large companies ask before deciding

Can an account hold more than one company?

Yes. One account holds several companies, each with its own registration, its Ministry of Human Resources number and its payroll IBAN, and each company's data is isolated from the others. Every admin account is bound to its own company and cannot see another company's data.

What permissions are available?

Admin groups the company creates, copies and edits, with permissions expressed as a module and an action, and each account limited to a scope of one or more branches or departments combined with an or, with an audit log of who did what, when, and what it was before and after.

What does the API read?

Employees, attendance and a payroll summary, with scoped keys whose scope is read from their row, and with no pay fields in the employee read. It is read-only, with a limit of 120 requests a minute per key, and it does not write into the system.

How do I learn of an approved request in my system?

You register an https address for web notifications, so a Request approved or Request rejected event reaches you with a signature that covers the timestamp, so you verify its source and an old call that is replayed is not accepted.

Request a demo on your company structure

We show you the permissions and connection on your own company structure, and start with the question your information security or finance team is holding up the decision on today.