Grant platform permissions

Grant platform permissions so Integrations can deploy the new payout connector by Wednesday. Give the integrations service account access to create and read connected accounts, create transfers, and view payouts but not to delete customers or export full payment method details. Record the permission grant in our audit log and notify Chris in integrations when it’s done.

Before granting platform-level permissions, make it easy for security to sign off: summarize exactly which API actions the service account will be able to call, surface any endpoints that return card or bank account details, and call out whether the account can initiate refunds or delete resources. Highlight the minimum change that allows the connector to work so reviewers can spot unnecessary privileges fast.

Integrations asked for platform permissions to create connected accounts and initiate transfers but security is blocking because of data exposure concerns. I don’t know whether the connector truly needs both actions or if we can separate duties. What checks should I run and what permission split will likely satisfy security while allowing Chris to finish the connector this week?

Every release we elevate service accounts to get a feature over the line, and audits later flag those grants as excessive. Which habit should we change so platform permissions are granted only when necessary and automatically revoked after deployment? Recommend a lightweight process for temporary grants, including expiration, owner, and a one-click rollback path for audits.