Permission, explained
Ending a session vs revoking health-data sharing
Learn which ConsentLoom controls end local access, manage the authorized connection, or start a new request with different categories.
Ending the local session
A local session gives this browser temporary access to records through the application’s server. Ending it invalidates that local access. The existence of a consent receipt is a separate matter: closing the workspace does not itself revoke an already completed authorization.
Managing the authorized sharing
The workspace links to the connection provider’s sharing controls. Use those controls when you intend to manage or revoke the registered application’s permission. Read the application identity and purpose carefully, because the current deployment uses a shared registered connection application.
Changing the requested categories
ConsentLoom’s implemented flow asks you to end the current session and reconnect with a new category choice. A new selection is a request that still needs authorization. Changing a checkbox is not, by itself, a modification of an existing receipt.
- To stop using this local workspace, end the session.
- To manage the registered application’s sharing permission, use the sharing controls.
- To request a different scope, reconnect with the intended categories and review the authorization.
Remember copies made outside the session
Revocation affects authorized access. It does not automatically retrieve a file already downloaded or a copy shared elsewhere. Read the privacy notice for the implementation’s retention and copy-handling details. The connection workflow still requires production activation before live use.
Questions about this guide
Does closing a tab revoke the receipt?
No. Local access and the authorized sharing receipt are different controls.
Does revocation apply only to the page I am viewing?
It applies to the registered application’s authorization. The current connection application is shared, so check its stated purpose and identity.