OAuth 2.0 Connections FAQ

Get answers for commonly asked questions about platform and engagement connectors

How do we limit the access Productiv gets when authorizing an OAuth 2.0 connector? Does Productiv get access to whatever the user authorizing has access to?

Productiv always requests the minimum scopes required to collect the data necessary for a connector. The OAuth 2.0 protocol allows our application to specify only the scopes necessary for the connector, and the authorizing user can only grant access to those scopes. We will not be able to use any other scopes or change the scopes our application uses without re-authorization from you. For more information on OAuth 2.0 and how it works, we recommend reading this great article from Okta.

Why should I use a service account when authorizing an application through OAuth 2.0 if Productiv only gets limited scopes?

We recommend that you create and use a service account with the required permission to authorize a connector so the connection is maintained when:

• The authorizing user’s permissions change
• The authorizing user leaves the organization

Note: When authorizing the connector, the app may not prompt you with a login if you have signed in recently. In this case it will automatically use the user that was last logged in on your device. If your intent is to use the service account, we recommend you log out of the application before authorizing the connector, or authorize in incognito mode.