# How should I limit permissions when connecting a tool?

Canonical URL: https://help.iagenify.com/faqs/tools/how-should-i-limit-permissions-when-connecting-a-tool

[← Back to Tools FAQs](https://help.iagenify.com/faqs/tools)

HELP CENTER · FAQ Tools 1 min read
# How should I limit permissions when connecting a tool?
Give a connected tool only the access needed for its intended job, such as read-only access for reporting or access to a specific resource rather than an entire account. The right scope depends on the tool’s permission model and the operation it must perform.
IaGenify
Tools

## Choose a narrow permission scope
Review the requested scopes and map each one to a concrete workflow requirement. Avoid granting broad write, administrative, or all-resource access merely because it simplifies setup.
Separate credentials by environment and purpose when supported. This limits the effect of a leaked or misused credential and makes it easier to identify which integration needs attention.
## Review and rotate access
Test the connection with representative operations and confirm that unnecessary actions are denied. Keep a record of the owner, purpose, granted scopes, and any expiration or renewal date.
Revisit permissions when the workflow changes or an integration is retired. Revoke unused access promptly and rotate credentials after suspected exposure, using the service’s documented process. [← Back to Tools FAQs](https://help.iagenify.com/faqs/tools)