Home / Insights / Article
Consent Is a Feature.
Consent is useful only when it is informed and reversible. Before a tenant assessment, the customer should be able to see what is requested, why it is needed, what is retained, and how access can...
Product authorization and privacy
Steve Copeland
Founder, SCOUTz
SCOUTz Editorial
Last reviewed: August 13, 2026
On this page
Use the section headings below to scan the evidence, understand the boundary, and take the next step.
Consent is useful only when it is informed and reversible. Before a tenant assessment, the customer should be able to see what is requested, why it is needed, what is retained, and how access can be revoked.
Show before asking
Present the requested permissions and plain-language purpose before authorization—not after the customer clicks.
Keep control reversible
Document how the connection is revoked, what happens to retained results, and which future scans will stop.
Record the decision
Capture who authorized access, the tenant, scope version, time, and reason so both MSP and client can audit the relationship.
Put it to work
Put the permission purpose, retention rule, and revocation path directly beside the authorization action.
Next step: Put the permission purpose, retention rule, and revocation path directly beside the authorization action.
SCOUTz provides security posture evidence and workflow support. It does not provide legal, insurance, or compliance certification advice.
Key takeaway
Put the permission purpose, retention rule, and revocation path directly beside the authorization action.
SCOUTz provides security posture evidence and workflow support. It does not provide legal, insurance, or compliance certification advice.