Administration and states

Audit log

Who did what, to which record, with the outcome, including the things people were refused.

In the productFictional data throughout. Nothing on this page comes from a real programme.

projectsmanager.ai

ADMINISTRATIONUsers & grants Audit log Sync status Settings

Administratorgrant: tenant

Administration › Audit log

Audit log

EXAMPLE DATA

Who · anyone

Action · all

Outcome · all

Period · last 7 days

WHEN	WHO	ACTION	RESOURCE	OUTCOME
6 Oct 09:41	Director, Textbooks	Confirmed a proposal	Risk log · P-004	OK
6 Oct 09:38	Director, Textbooks	Committed a cost-table upload (5 lines)	Cost lines · costs-2026.xlsx	OK
6 Oct 09:12	Administrator	Created a grant	User · Project officer → project DEDU101	OK
6 Oct 08:57	Field officer	Tried to raise a risk	Risk log · project DEDU101	REFUSED · OUT_OF_SCOPE
5 Oct 17:20	Agent	Proposed an annual work plan	Annual work plan · AWP-26	PROPOSED
5 Oct 16:02	Donor representative	Exported a Project Book	Project Book · DEDU101	OK
4 Oct 15:11	Director, Textbooks	Saved a next-design capture	Next-design capture · pdo1_midterm	OK
4 Oct 14:50	Director, Textbooks	Recorded a decision	Risk log · D-003	OK

THE REFUSED ROW, IN FULL

403 · out_of_scope
project:DEDU101 is outside every extent granted to this user (activity:1.5.1). Its ancestry is project › agency › ministry › country › tenant.

The refusal names the extent and the kind. It does not name a role: nobody is refused because of what they are, only because of where they stand.

EVERY ROW CARRIES TWO REFERENCES

The record's id, which is its real identity, and its human code, which is only a label. Codes may repeat across agencies and may be renumbered; ids do not.

AGENT ACTIONS ARE LOGGED AS AGENTS

A proposal appears here as PROPOSED, with the agent as the actor. When a person confirms it, a second row records who.

Request a demo

On a phone the screen is shown as a small layout preview. Open this page on a larger screen to read it, or read the points below.

What this screen shows

A refusal is logged with the extent and the kind, not a bare error.
Every row carries the record's id and its human code.
An agent's action is logged as an agent's, and a person's confirmation as a second row.

Why it works this way

Codes can repeat across agencies and be renumbered. Ids do not, so the log keeps both.