Compliance: Audit trail for sensitive guest actions #8

Open
opened 2026-02-09 17:13:19 +05:30 by androidlover5842 · 0 comments

Goal

  • Provide an audit log for sensitive actions (documents + guest profile updates) for accountability.

Scope

  • Log (server-side preferred): who, when, what changed for:
    • guest profile updates
    • document upload/delete
    • signature upload
    • booking guest link/unlink (if supported)

UI

  • Read-only timeline section in booking details or guest screen.

Engineering requirements

  • Do not duplicate permission logic; add explicit policy methods in core/auth/AuthzPolicy.
  • Follow Room DB sync rule: audit entries should come from server/Room, not local-only.

Acceptance

  • Audit entries are visible and consistent across devices.
Goal - Provide an audit log for sensitive actions (documents + guest profile updates) for accountability. Scope - Log (server-side preferred): who, when, what changed for: - guest profile updates - document upload/delete - signature upload - booking guest link/unlink (if supported) UI - Read-only timeline section in booking details or guest screen. Engineering requirements - Do not duplicate permission logic; add explicit policy methods in `core/auth/AuthzPolicy`. - Follow Room DB sync rule: audit entries should come from server/Room, not local-only. Acceptance - Audit entries are visible and consistent across devices.
androidlover5842 added the featurecompliancesecurity labels 2026-02-09 17:13:19 +05:30
androidlover5842 added this to the TrisolarisPMS Roadmap project 2026-02-09 17:14:53 +05:30
Sign in to join this conversation.