By role Audit and compliance

An append-only log per instance, an auditor screen, and a configuration history you can read as of any date.

For the people who read the record. This page says what SmartApps put in your hands, what stays with other roles, and how a week runs.

A week

How a week runs with SmartApps

Monday
Open the auditor screenOpen the auditor screen: instances of the journal approval app for the quarter, filtered by amount.
Tuesday
Read five log entries for a sampleRead five log entries for a sample: values shown, decision, acknowledgement, app version.
Wednesday
Read the configuration historyRead the configuration history: the approval band as of March, who changed it, the note.
Thursday
Export the log for the period with its hash chain.
Friday
Sign the certification instance as the external stage, from your own screen.
Yours and theirs

What you do yourself, and what other roles keep

Yours

  • The auditor screen across apps, instances and configuration history
  • Exports with the hash chain
  • The external stage of certifications
  • Retention and erasure evidence

Kept by other roles

  • Everything else
Apps you will meet first

Questions

Can an entry be changed after the fact?

The log is append-only and hash-chained; a correction is a new entry that refers to the old one.

Can I see what the approver saw?

Yes: the values shown and entered at the step, the app version, the access policies applied to the read.

How are approvals enforced?

On the engine: levels in sequence, alternates, delegates with both names logged, clocks and escalation; an override is its own logged step with a justification.

See it from your seat

Tell us your role and one process; the demonstration runs the screens you would use, on data like yours.