Skip to content
HeySri

Security and procurement

How your records and access are protected.

HeySri runs closed-period reviews on the files you export. This page explains what you control, what is recorded, and how anyone can check a sealed record.

01 · Access

You decide who can do what.

Access is built from roles, scoped keys, and separate workspaces. Each limit is set by your team and can be changed as responsibilities change.

Scoped access keys

A key can carry full access, read-only access, or a named set of permissions. You can set an expiry date and revoke a key when access should end.

Roles and separation of duties

People work through roles such as viewer, operator, approver, author, and integrator. Permissions separate rule authoring from credential management; administrator access can hold both, by design.

Separate workspaces

Records, rules, and registered agents belong to a workspace. A lookup in one workspace does not reach another.

A recorded history of access changes

Issuing a key, approving a rule, and changing a connection are written to a security log with the actor, role, and time.

What you control Who holds each role, which keys exist, when a key expires, and which workspace a team works in.

02 · Records

What is recorded.

Each review produces a decision record. Entries are written as the work happens, and the record is sealed when the review is finished.

  1. Step 1

    Files received

    The exported ledger, goods-received log, or bank clearing file for the completed period.

  2. Step 2

    Rules applied

    Each rule evaluation and lookup is written to the record.

  3. Step 3

    A person decides

    Questions and approvals are recorded with who answered and when.

  4. Step 4

    Record sealed

    The record is sealed and given a reference for the working paper.

  5. Step 5

    Record checked

    Anyone with the reference can check the sealed record on the verification page.

03 · Verification

Anyone can check a sealed record.

Verification does not need an account. Enter the record reference and HeySri reports one of three outcomes.

Intact and signed

The record is unchanged and signed

The record has not changed since it was sealed, and a signing key is attached. The result shows the key used.

Intact, not signed

The record is unchanged, but origin is not proven

The record has not changed since it was sealed. No signing key is attached, so the origin of the file is not proven.

Does not match

The record and its contents no longer match

Verification stops where the mismatch begins and reports the entry at that point.

A passing check has a boundary It confirms the record has not changed since it was sealed. It does not confirm the decision behind the record.

04 · Scope

What a check confirms, and what stays with your team.

Every control on this page is one you can inspect. Your audit procedures and delegation decisions remain yours.

Controls you can check HeySri is not externally certified today, so this page describes the controls directly: what is set, what is recorded, and what you can verify.

A passing check confirms:

  • The sealed record still matches what was sealed.
  • The signing key attached to the record, when one is present.
  • Where a mismatch begins, if the record and its contents differ.

These decisions stay with your team:

  • Whether the decision was commercially or legally right.
  • Whether the approver held authority under your delegation matrix.
  • Whether the input file was complete before the review started.

Verification tells you the record is intact. Your team and your auditor decide what it means.

If your procurement review needs a specific control or document, ask your HeySri contact for current details.