Test and govern access
Review access as part of every release that changes users, authentication, pages, data queries, or workflows.
Before publishing
Write the intended access for each audience.
Review AI-generated changes that affect data or authorization.
Use Preview as an invited user to inspect the app from that user's perspective.
Record the app version, environment, identities tested, and results.
Preview helps reveal differences in the interface. Use actual test sign-ins and data requests to check authentication and enforcement.
Keep ownership clear
Assign an owner for membership reviews, authentication configuration, permission rules, and incident investigation. Recheck access when a person changes responsibilities or leaves, and after changing team or user properties used by rules.
Use the audit trail to review available activity and system logs to investigate errors. Confirm event coverage and retention for your requirements rather than assuming the logs form a complete compliance record.
Review the app version
Use Version History to identify the app state being reviewed. Inspect changes before reverting, record the selected version in your review, and repeat permission tests after a revert. Check database records separately: app version history is not a record-level data backup.
Was this helpful?