You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Audit log: per-area read access and views by person #119
Follow-up to #90. Today the audit log in common_audit_events is read through one dashboard permission, audit:read, which shows every area at once. That's acceptable to start with only if audit:read stays with roles that already hold every per-area read permission. This issue is about reading it properly.
Per-area read access
Permissions per area, either audit:read:<area> or reuse each area's own read permission (web:content:write, tg:audit:read, esign management, …). audit.list should return only the areas the reader can see.
Redaction per area for the fields an area's own permissions would hide, for example Azure member contacts and e-sign recipients. The stacked meta-option work on feat(audit): record every change in a central audit log #90 limits what is stored; this is about who sees what is stored.
Views by person
"What was done to me / by me" under me, built from the events whose actor or target is the viewer. It also helps with data-subject access requests.
A per-person timeline across areas, only if someone needs it, put together when it's read: the central log, tg_audit_log and people_activity, matched by IdP sub (Telegram IDs resolved through the access snapshot). Each area keeps its own store and permissions; nothing is copied.
Query performance (when volume calls for it)
The area filter uses ilike 'web.%', which the btree index on action can't serve. Store the area in its own column, or index action with text_pattern_ops.
Text search runs ilike over five columns. Add pg_trgm indexes if it gets slow.
Activity