IT and equipment

Every laptop has one holder.And a history that survives the return.

Agents issue and take back kit through the same record HR uses. A second open assignment is refused, and a return closes the row instead of deleting it.

Where equipment tracking goes wrong.

  1. 01

    One laptop, two owners

    A sheet updated by two people says a machine is in two places.

  2. 02

    Returns that erase history

    Clearing the holder field loses who had it, and in what condition it came back.

  3. 03

    Leavers who keep the badge

    The exit is marked complete while the access card is still out.

Scenarios

Questions IT can answer.

How OpenHR answers

Not while Aarav holds it. The refusal names the holder and the date it was issued.

What changes.

  • One answer to "who has it?"Every asset has at most one open assignment.
  • History you can queryWho had a laptop in March stays answerable after it's returned.
  • Kit back before the exit closesAsset clearance waits for the custody table, not a tick box.
  • Damage routed to repairReturns in poor or damaged condition go to in_repair, not back into stock.

Controls.

  • Leave can't go negative

    A tracked balance never drops below zero, and overlapping requests are refused.

  • One holder per asset

    A second open assignment is refused by the service and by a database index.

  • Exits gate on custody

    Asset clearance can't be signed off while kit is out.

  • Audit log

    Every change writes an audit row in the same transaction.

  • Read-only SQL

    run_query accepts SELECT statements only.

  • Self-hosted

    One SQLite file on infrastructure you control.

Questions.

What counts as an asset?

Anything with a tag: laptops, monitors, phones, access cards, peripherals and software seats are all in the sample data.

Does it revoke system access?

No. access_revoked is a clearance step a person signs off. Attri connects it to your identity provider in managed deployments.

Does it have sign-in?

Not yet. The open-source server has no sign-in or roles, and its HTTP transports bind to localhost by default. Keep it off shared networks. API keys with employee, manager and HR-admin roles are planned for v0.2, and Attri adds sign-in and roles in managed deployments.

Let your agents handle the HR admin.Keep the rules on the server.

Run OpenHR on a demo company in minutes, or have Attri deploy it inside your environment with sign-in, roles and approval rules.