Review connected-app permissions before an outreach tool gets access. Identify the account, inspect the grant and plan how the connection will be removed.
Connecting a calendar, CRM or email tool is also an access decision. An outreach app may need to identify a user, read account data or change it. Those are different jobs, even when the setup begins with the same familiar sign-in button.
Before anyone connects a client account, agree on four things: the account being connected, the app receiving access, the work it is allowed to do and the person responsible for removing that access. A short review at setup gives your team a usable record when a campaign, operator or vendor changes.
Start with the account and the job
Write the intended task in ordinary language before opening the consent screen. For example: “Let the booking tool check the approved calendar and create confirmed meeting events.” That is more useful for a permissions review than “connect the sales stack.”
Then confirm the signed-in account. A teammate who manages several clients should not approve access while guessing which account is selected. Ask the client’s account owner or administrator to approve the connection when the team does not have that authority.
Inspect the app’s publisher as well as its display name. Microsoft’s guidance for evaluating consent requests recommends understanding who controls an application and why it requests the proposed access. A recognizable name alone does not answer either question.
Separate sign-in from permission to use data
Do not treat “I can sign in” as a complete description of the connection. Google distinguishes several linked-app relationships, and one app can have more than one relationship with the same account.
| Connection to identify | Question for the review |
|---|---|
| Sign-in connection | Is the account being used to identify the operator, or is there a separate data-access grant too? |
| Access to account data | Which products and actions can the app access: viewing, copying, sending, creating, editing or deleting? |
| Organization-managed permission | Did a user grant access, or did an administrator approve it on the organization’s behalf? |
The exact permission names and combinations depend on the service and app. Do not assume every consent screen offers individual switches for every capability.
For Microsoft Entra applications, delegated permissions act on behalf of a user, while application permissions can operate without user interaction. The distinction matters when asking who must review an integration; it is not a reason for an outreach operator to change tenant-wide consent policy. Use the Microsoft consent guidance with the client’s administrator when that level of access is involved.
Compare the requested actions with the approved task
A tool’s category does not tell you its permission requirements. Read what the requested permission actually allows and ask the vendor about anything the documented workflow does not explain.
Google’s account-access guidance distinguishes basic profile information from access to view or copy data and access to manage it. Management access can include creating, editing or deleting data. Google also advises against sharing a Google Account password directly with a third-party app.
Use a simple decision table during the review:
| Requested capability | Practical question before approval |
|---|---|
| Read availability or account information | Which specific information is needed for the task? |
| Copy or synchronize records | Where will copies be stored, who can use them and how are they removed? |
| Send messages or create events | What triggers an action, which account performs it and how will the team test it? |
| Edit or delete existing data | Why is this necessary, and who approves that level of access? |
| Access unrelated products or resources | Is there a documented requirement, a narrower supported setup or a different tool to consider? |
Illustrative example: A fictional agency is evaluating a meeting-booking app for a client. Calendar availability and event creation fit the proposed job. If the app also requests mailbox access, the reviewer asks which feature requires it and whether that feature is part of the client’s approved workflow. The reviewer does not assume the permission is malicious, necessary or optional without checking the vendor’s explanation.
This is a review method, not a claim about a particular booking product or its available permission settings.
Review existing grants in the right place
A tool’s own “connected” badge is useful context, but also inspect the account provider’s record of the connection.
For Google Accounts, use the linked-apps management instructions. Open the relevant app and its details under the account-data access category. Check all relevant connection types: removing a sign-in relationship is a different action from reviewing or removing the app’s data access.
For Microsoft work or school accounts, My Apps permission management separates permissions the user approved from permissions approved by an administrator. The user can revoke their own consented permissions; administrator-consented permissions require the administrator’s involvement. These instructions are for work or school accounts, not a universal path for personal Outlook.com accounts.
If the account, application or grant is unfamiliar, collect its identifiers and ask the responsible owner to review it. Avoid reconnecting with a different person’s account simply to get past a consent error.
Keep a connection register without storing credentials
The record should let a replacement operator find the correct grant and business owner. It should not become another place to keep passwords, tokens or recovery codes.
Illustrative register using a fictional agency and a reserved example domain:
| Field | Example entry |
|---|---|
| Business purpose | Coordinate approved outreach meetings |
| Connected account | meetings@northstar.example |
| Application and publisher | Record the names shown during the consent review |
| Access reviewed | Record the displayed permissions and the reason for each relevant capability |
| Approval and business owner | Client account owner; agency operations lead maintains the record |
| Review trigger | Vendor change, new requested permission, client handoff or operator departure |
| Removal responsibility | Named account owner; client administrator for administrator-consented access |
| Evidence | Date of review and a reference to the approved setup test |
Keep this beside the campaign’s operating notes. Treat a new consent request as a reason to review the connection again, rather than assuming the original approval covers every later feature.
Disconnect access and handle retained data separately
For a planned tool change, first identify the workflows that depend on the connection and agree when they should stop. Removing permission can break app functionality, as Microsoft’s My Apps guidance explains.
Use a short offboarding sequence:
- Identify the exact app, account and relevant grant with the responsible owner.
- Pause the dependent workflow at the agreed time and preserve the business records the client needs.
- Remove the relevant access through the account provider, or ask the administrator to handle an administrator-controlled grant.
- Verify that the intended connected action no longer succeeds. Do not automatically reconnect when the expected authorization failure appears.
- Review the vendor’s account-closure and data-deletion process separately, and update the connection register with the outcome.
Revoking access is not the same as deleting information the vendor already copied. Google explicitly notes that a developer may still hold previously shared data, and a separate deletion request may be necessary.
Keep app-grant review distinct from human access to a shared inbox and from API-key scope, storage and rotation. A team may need to review all three during the same handoff, but removing one does not document what happened to the others.
This checklist is for reviewing your existing tools; it does not describe an AllProfiles OAuth-management feature. The goal is a connection the client understands, an operator who knows its limits and a clear owner for removing it when the work ends.


