SmartApps Governance and audit

Audit-grade by default: the record of who decided what, when, on which data.

Every instance writes an append-only log of the person, the step, the values, the decision, the notifications and the acknowledgement of each write-back, with the version of the app.

6 h 14 min
for a three-stage certification: data engineering, finance lead, external auditor
showcase estate
0
follow-up questions from the auditor after signing
showcase estate
5
log entries the auditor read directly during the quarter's audit, with zero requests to the finance team
showcase estate
12
levels at which data access is controlled
product
47 min
for a documented erasure request across 847 records, signed by the data protection officer
showcase estate
The log

What every instance records

EntryHoldsExample
Stepnode, role, person, start and end time, app versionDecide · buyer · Priya Sharma · 14:05:41 · v3
Readhandler, filter, rows returned, access rules applieddh_po_lines · group 101 · 31 rows · policy PURCH-101
Valuecomponents shown and entered, with their values at the timedd_decision = split · txt_note = 'supplier capacity'
Decisionthe criterion that held and the arrow takendecision: split → re-source
Notificationchannel, recipient, card, buttons pressedTeams · supplier contact · asked · replied 11:30
Write-backinterface, values sent, acknowledgement or errorBAPI_PO_CHANGE · 4500012345 · RETURN S · 14:06:12
Overrideadministrator action with justificationreleased stuck instance · 'system maintenance' · E. Clarke

The log is append-only and hash-chained, so every entry stays as written; a correction is a new entry that refers to the old one. Each entry carries the app version and the hierarchy version, so a decision taken under last year's approval bands is read with last year's bands. Files uploaded during a step are referenced from the log and kept under the retention rule.

Auditors read the log themselves, on an auditor screen that shows instances, decisions and configuration history with the same filters a process owner uses. In the showcase estate the external auditor read 5 entries during the quarter's audit and sent the finance team zero requests.

The certification pattern

Three stages, one review pack, an external signature

The showcase estate's SOX certification of a revenue view.

Trigger
Certification dueThe quarterly rule opens the certification instance for the revenue view, with the review pack generated by the platform: column-level lineage to the source tables, the 30-day quality trend, the rules in force, the previous certificate and the hash chain.
09:04
Stage 1 · Data engineeringSchema validation signed on the certification screen.
12:31
Stage 2 · Finance leadBusiness accuracy of the quarter's figures signed from the same pack.
15:18
Stage 3 · External auditorIndependence review completed on the auditor's own screen; certificate issued with its hash; 6 hours 14 minutes end to end.

The pattern is a collaborative app with three levels in series and a rule that the third level is external when the view is in scope for the regulation. The review pack is a set of handlers and a generated screen. The same pattern serves a data product publication (with a hard block below a trust score), a policy change (with an automated impact analysis as stage 2) and a schema change on personal data (with legal and the data protection officer as stages).

View certificationdata engineering → domain lead → external auditor when in scopesequence enforced
Policy changeproposer → automated impact analysis → domain owner → affected ownersimpact attached before humans decide
Data product publicationowner → quality gate → governance leadhard block below 80 percent trust
Personal-data schema changedata engineering → legal → data protection officerDPO signs before deployment
Access

Rules inherited from each source, applied at read time

A person sees in an app what the source systems allow them to see. The data handler applies the source's own policy when it reads: rows by organisation, plant or region; columns masked or hidden; values redacted. On top, the app adds the level's or the role's scope. The log records, for every read, which policies applied, so the answer to 'what could this person see on that day' is in the record.

Configuration rights are separate from run rights: who may edit an app, who may publish, who may switch write-back on per object, who may override a stuck instance. Each is a role of the platform, logged like everything else. The trust center sets out the access model, the AI boundary and the certifications.

RightWhoLogged as
See rows and columnsfrom the source policy plus the role scoperead entry with policies applied
Act at a stepthe role or level, alternates, delegatesstep entry with both names under delegation
Edit the definitionconfigurator role for the appdefinition change with version and note
Publish and promoteprocess owner; application team at the gatepromotion entry with approval
Switch write-back onapplication team, per object, after a test writewrite-back enablement entry
Override an instanceadministratoroverride entry with justification
Configuration as a record

Definitions are versioned and logged like data

Every change to a hierarchy, a screen, a handler, a criterion or a variable is a versioned entry with the person, the time and the note. Retiring a level or a screen is a flag with its dependents listed; the definition stays readable. The history of an app answers an auditor's question about a rule the same way the log answers a question about a decision: what was the rule on that date, who changed it, and why.

Global variables carry the values regulations care about, such as approval bands, so a change to a band is one logged entry that every app inherits from its effective date.

ChangeA configurator edits a criterion and writes a note.
Terms on this page

Decision logThe append-only record of every step, value and decision in every app instance, with the person, the time and the acknowledgement of any write-back.
VersionA published state of an app. A new version keeps the old one available for running instances and records what changed and who approved it.
Hash chainEach log entry carries a hash of the previous one, so any change to an earlier entry is detectable.
Review packThe evidence a certification stage needs, generated by the platform: lineage, quality trend, rules in force, previous certificate.
Effective dateThe date from which a changed rule or band applies; instances read the values in force on their own dates.
Questions

Can the log be exported for an audit?

Yes: per app, per instance or per period, as files with the hash chain, or read directly on the auditor screen.

Who can delete a log entry?

Nobody. A correction is a new entry that refers to the earlier one. Retention rules and erasure requests remove personal data by rule, with the removal itself logged.

How are personal data and erasure handled?

Personal fields are tagged in the catalog; an erasure request runs as an app that finds every occurrence, removes or masks it and records the run. The showcase estate completed one across 847 records in 47 minutes with the data protection officer's signature.

Which certifications does the platform hold?

The trust center lists the current status and dates of SOC 2, ISO 27001 and the SAP program, and how to request the security packet.

See a SmartApp built on your data

Bring one process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.