Skip to main content
Connect your SurveyMonkey team to Oleria to see who belongs to the team, what role each person holds, and which workgroups they are in. Oleria also reads the team activity log, so you can spot sign-ins, role changes, sharing, and exports.
Oleria no longer connects to SurveyMonkey through SCIM. The integration uses a SurveyMonkey access token instead. If you connected SurveyMonkey before, see Reconnect an existing SCIM integration.

​
What Oleria discovers

Oleria uses this data for dormant account detection and access reviews, refreshed on Oleria’s regular sync schedule.

​
Prerequisites

  • A SurveyMonkey Enterprise plan. A Teams plan can connect only with a draft app, which SurveyMonkey disables after 90 days, so the integration stops syncing unless you upgrade and deploy the app. Individual plans don’t expose team APIs, and Oleria refuses the connection.
  • A SurveyMonkey account that is a team owner or admin. The activity log is available to admins only.
  • Permission to register an app at developer.surveymonkey.com (use developer.eu.surveymonkey.com if your team is in the EU data center).
  • Administrator permission on the Oleria workspace.
SurveyMonkey disables a draft app after 90 days unless you deploy it, and deploying a private app requires an Enterprise plan. Once the app is disabled, Oleria stops syncing until you deploy the app or SurveyMonkey grants an extension. Deploy the app as a Private app, not a public one.

​
Get your access token from SurveyMonkey

1

Register an app

Sign in to the SurveyMonkey developer portal as a team owner or admin, select My Apps, and register an app for your team. SurveyMonkey creates it as a draft app. If your team is on an Enterprise plan, deploy it as a private app.
2

Enable the scopes Oleria needs

Open the app’s Settings page and enable these scopes:
Without groups_read, Oleria can’t read any team members and refuses the connection. If you leave out another read scope, the connection still succeeds, but Oleria skips the data that scope covers, such as workgroups or organization roles. If you want to run workgroup actions, keep workgroups_read and workgroups_members_read enabled, because Oleria refuses the action without them.
3

Copy the access token

On the same Settings page, copy the Access Token. SurveyMonkey says access tokens don’t currently expire, but it may change that, and a draft app’s token stops working when the app is disabled after 90 days. Store the token securely and rotate it per your organization’s security policy.
Use the access token from the app’s Settings page. A token created with the client_credentials grant carries no scopes, and Oleria rejects it.

​
Connect SurveyMonkey to Oleria

1

Open the integration

Sign in to your Oleria workspace and navigate to Integrations -> SurveyMonkey -> Connect.
2

Enter the access token

Oleria detects your team and your SurveyMonkey data center (US, EU, or CA) from the token, so there is nothing else to enter.
3

Authenticate

Select Authenticate. Oleria validates the token and its scopes, then discovers your team’s members, roles, and workgroups and begins the first sync.

​
Verify the integration

Confirm SurveyMonkey appears on the Connected tab of your Oleria Integrations page with a status of Healthy. After the first sync completes, you can review the discovered members, roles, workgroups, and activity in your Oleria workspace. If you change the token in SurveyMonkey, edit the integration in Oleria and enter the new Access Token. A token must belong to the same team as the existing integration. To connect a different team, create a new SurveyMonkey integration.

​
Reconnect an existing SCIM integration

If you connected SurveyMonkey before the native connector, your integration used a SCIM URL and token. Oleria can’t use those credentials with the new connector, and the integration shows an error asking you to reconnect.
1

Get an access token

Follow Get your access token from SurveyMonkey.
2

Edit the integration

In Oleria, open the SurveyMonkey integration, select the option to edit it, and enter the Access Token. Oleria replaces the old SCIM credentials with the token. You can revoke the SCIM token in SurveyMonkey afterward.

​
Remediation actions

Oleria checks the token’s granted scopes before it runs an action, so a missing scope is reported without changing anything.

​
Known limitations

  • No account disabling or removal: SurveyMonkey’s API has no way to disable a team member, remove them from the team, or change their team role. Oleria can only add or remove workgroup members.
  • Daily request limit: SurveyMonkey caps private apps at 500 requests per day. Oleria paces its requests and stops a sync before the last 20 calls of the day so workgroup actions keep working. The limit applies to the whole app, so create a dedicated app for Oleria rather than reusing one that other tools call. If the day’s quota runs out, syncs and workgroup actions wait until SurveyMonkey resets it at 00:00 GMT. SurveyMonkey sells higher limits.
  • Admin token for activity: The activity log needs a token from a team owner or admin. With any other token, the sync fails until you replace it, rather than skipping activity.
  • Activity isn’t linked to surveys: The log names the survey or collector an event acts on only in free text, so Oleria attributes each event to the SurveyMonkey team rather than to a specific survey.
  • Surveys and sharing aren’t inventoried: Oleria shows team members, roles, and workgroups, but not individual surveys or who they’re shared with.
  • No MFA, SSO, or last sign-in fields: SurveyMonkey doesn’t expose these per user. Dormancy comes from sign-in events in the activity log.

​
Contact us

For questions about this integration, contact us at support@oleria.com.