Approve CommitControl in Salesforce

Why Salesforce asked for an admin

Since September 2025, Salesforce blocks users from authorising a connected app that has not been installed in the org, unless their profile or a permission set grants Approve Uninstalled Connected Apps (or Use Any API Client where API Access Control is on). The System Administrator profile has these by default; standard sales profiles do not. Nothing is wrong with the user's account. It is an org setting, and you decide how to handle it.

What CommitControl reads

CommitControl builds a weekly risk briefing and forecast from your opportunities. A sync reads:

• Opportunities: open deals and recently closed ones, with name, account name, industry, employee count and annual revenue, owner, stage, amount, close date, created date, last activity date, forecast category, description, and won/closed flags.
• Opportunity owners: name, title, and manager name and title.
• Activity metadata from the last 90 days: for Tasks and Events linked to a record, the type, date and linked record only. Subjects, descriptions, bodies and comments are never queried.
• Opportunity contact roles: which contacts are attached to a deal, used only to count the people involved. No contact details are read.

Our code only issues reads. It does not create, update or delete records in Salesforce.

Salesforce has no read-only OAuth scope, so CommitControl requests the standard api scope plus refresh_token and offline_access for the scheduled sync. What it can see is limited to what the connecting user's profile and sharing rules can see. If you want to narrow it, have the connection made by a user whose access covers only the opportunities that should be forecast.

Data is stored in AWS Europe (Frankfurt). OAuth tokens are encrypted at rest. The full detail, including sub-processors, is on our security and data processing pages.

Three ways to let them connect

1. Install the connected app for your org

Installing CommitControl's connected app is the route most admins prefer, because the policy then sits with you.

1. In Setup, open Connected Apps OAuth Usage.
2. Find CommitControl in the list and choose Install.
3. In the app's policies, set Permitted Users to suit you: all users may self-authorise, or admin-approved users only, in which case add the right profile or permission set.

Then ask your sales leader to choose Connect Salesforce again in CommitControl. If CommitControl is not in the list, email us and we will walk you through it.

2. Grant the permission to the person connecting

Create a permission set with Approve Uninstalled Connected Apps (or Use Any API Client if API Access Control is on in your org) and assign it to the sales leader. Salesforce recommends granting this sparingly, so option 1 is usually the better fit.

3. Connect it yourself

Connect together on a call or at one screen. Your sales leader starts Connect Salesforce in CommitControl, and you sign in on the Salesforce screen with your own login and approve it. The connection then uses your Salesforce access, so read the note on scope above before choosing this.

Before you start

• Your Salesforce edition needs API access: Enterprise, Unlimited, Performance and Developer editions include it, and Professional Edition needs the API add-on.
• CommitControl currently supports orgs with up to 5,000 open opportunities in scope. Above that, the sync stops rather than publish a partial forecast. If your org is larger, email us before connecting.

Removing access

A workspace owner or admin can disconnect from Integrations in CommitControl, which deletes the stored tokens. You can also revoke access from Salesforce Setup at any time, and syncs stop from that point.

Questions

Email hello@commitcontrol.com and a person who works on the product replies, usually within one business day. If your security team has a questionnaire, request the security pack.