Skip to content
ConsentLoom

Permission, explained

How to read a consent receipt in ConsentLoom

Inspect authorized categories, returned record counts, source receipts and expiry metadata without confusing a request with a completed authorization.

Compare the request with the returned scope

The categories you selected before connecting describe what you requested. The workspace uses the returned categories and consent metadata after authorization. When checking a connection, read the actual response rather than relying only on the earlier checkbox state.

Separate permission from record count

A category card shows how many records were returned for that category. Zero entries does not, on its own, explain whether the source lacked data, returned an empty category, or could not supply the expected information. A permission to request a category is not a promise of a populated response.

Read the receipt fields literally

Where receipts are returned, the interface displays their category list, source and expiry. The main consent panel also shows the returned status. Expand “Inspect consent metadata” to see the object behind those labels. An omitted field should not be replaced by an assumed duration or source.

Tie future independent operation to a real registration

When a business takes over ConsentLoom, its registered application purpose, allowed categories, server credentials and privacy disclosures should describe that actual operation. A new corporate owner’s name should not merely be inserted into an old consent explanation while the connection configuration remains unchanged.

Why the receipt points back to FinchNode

ConsentLoom displays consent metadata from the FinchNode connection and provides a direct route to its sharing-management page. Keeping that route visible helps a visitor identify where the registered permission is managed, beyond the temporary local session.

Manage authorized sharing with FinchNode

Questions about this guide

Is a selected category already authorized?

No. Selection happens before authorization; the returned consent response is what the workspace can inspect.

Does a zero count prove the category was denied?

No. The count and the permission answer different questions. Inspect the returned consent and source metadata.

Sources and implementation

Browse all public guides →