For admins: approving Attainmint

Someone on your team asked whether you would approve Attainmint’s read-only connection once it is released. Attainmint keeps a record of a rep’s own sales work: how many calls, meetings, tasks and deal moves they made, and when.

What it would read, and what it would never do

It would

It counts only the connecting person’s own activity, and keeps only the kind of action and when it happened.
The person could disconnect at any time, and you could revoke it from your admin settings, stopping all future access.

It would never

It never keeps customer names, notes, email text or attachments, and never counts other people’s work. Where it has to look at a colleague’s entry to recognise the person’s own action, the platform’s section below says exactly what.
Read-only. It would never create, change or delete anything in your system.

Platform by platform

Salesforce

Built, not switched on

Would read: the connecting person’s own logged calls and emails (completed tasks), meetings (events) and opportunity stage changes.
Scopes: apirefresh_token
How: the person signs in to Salesforce (OAuth with PKCE); Attainmint never sees their password. It sends only read queries (SOQL SELECT, REST API v62.0): the Task and Event rows that person owns, and the OpportunityHistory rows they made. To tell a stage change from another edit (an amount, a close date), it then reads the stage, author id and time of every history row on the opportunities that person changed, colleagues’ rows included; those are compared in memory and never stored. It keeps only the kind of action, its time and a keyed hash of the record id. Salesforce’s api scope itself would allow whatever that person may do through the API; Attainmint never sends a request that creates, changes or deletes anything.
Status: built, not switched on yet. There is nothing to approve yet; this page will say how once it is released.

HubSpot

Being built

Would read: the connecting person’s own new deals and deal stage changes.
Planned scopes: crm.objects.deals.readcrm.objects.owners.read
Status: being built. There is nothing to approve yet; this page will say how once it is released.

Dynamics 365

Being built

Would read: the connecting person’s own phone call, appointment and task activities and opportunity stage changes.
Planned scopes: Dynamics CRM: user_impersonation (delegated)
Status: being built. There is nothing to approve yet; this page will say how once it is released.

Outreach

Being built

Would read: the connecting person’s own calls, emails sent (counts and times only) and tasks.
Planned scopes: calls.readmailings.readtasks.readusers.read
Status: being built. There is nothing to approve yet; this page will say how once it is released.

Until it is released

The scopes above are the minimum Attainmint plans to request. The Salesforce, HubSpot, Dynamics 365, Outreach connections are not available yet; until they are, the person’s browser extension still notes their actions on the sites they turned on, and those counts are labelled as self-observed, never as verified.

More help