Skip to main content
Connect Bonusly to Oleria to extend visibility into your employee recognition and rewards platform. Oleria reads accounts and admin-role standing from the Bonusly REST API using a Personal Access Token, so accounts with elevated Bonusly access are visible alongside the rest of your identity and access graph.

​
What Oleria discovers

Once connected, Oleria continuously discovers and maps the following from Bonusly:
  • Accounts - every user in your Bonusly account, including the profile fields exposed by the Bonusly Users API. Archived accounts are included, so a leaver who still exists in Bonusly remains visible.
  • Admin roles - Member, Tech Admin, and Global Admin, derived from the admin flags on each user’s account.
Bonusly is a peer-recognition and rewards tool, not an identity or HR system of record. Oleria doesn’t import Bonusly user groups. Bonusly also exposes no audit-log or activity API, so no activity is discovered.

​
Prerequisites

  • A Bonusly Global admin or Tech admin account, to create a company-wide Personal Access Token
  • Admin access to the Oleria workspace
Either admin tier works. Bonusly reserves some token scopes (finance:administer, awards:administer) for Global admins only, but the user:read scope this integration requests is available to Global admin and Tech admin accounts equally.

​
Generate a Personal Access Token in Bonusly

1

Open API & Tokens

Sign in to Bonusly as a Global or Tech admin, then select Company -> Integrations -> API & Tokens.
2

Create a token

Select Create token and give it a recognizable name, for example Oleria Integration.
3

Set the expiration

Choose an expiration of up to 365 days - Bonusly’s maximum token lifetime. Bonusly emails a reminder 30 and 7 days before the token expires.
4

Grant the read scope

Grant the token the user:read scope. This is the only scope Oleria needs to discover accounts and admin roles. To let Oleria deactivate and reactivate users, also grant user:administer.
5

Copy the token

Copy the token now.
Bonusly displays the plaintext token only once and stores only a hash afterward. If you lose it, you must create a new token and update the connection in Oleria.

​
Connect Bonusly to Oleria

1

Open the integration

Go to your Oleria workspace, select Integrations -> select Bonusly, then select Connect.
2

Complete the connection form

Provide the following:
3

Confirm the connection

Select Authenticate to validate the credentials. Find the newly connected Bonusly instance on the Connected tab of your Oleria Integrations page.

​
Remediation actions

The token must belong to a Global or Tech admin. Bonusly refuses these actions when an HRIS or SCIM integration manages your users, and it does not let you deactivate the last admin. Oleria has no role actions for Bonusly, so change admin status in Bonusly.

​
Verify the integration

Confirm the Bonusly instance appears on the Connected tab of your Oleria Integrations page. After the first sync completes, you can review the discovered accounts and admin roles in your Oleria workspace.
The token expires after at most 365 days. Before it does, mint a replacement in Bonusly and update it in Oleria by editing the integration - an expired or revoked token will cause the sync to fail.

​
Known limitations

  • No groups - Oleria doesn’t import Bonusly user groups, such as teams, departments, locations, or custom groups.
  • No fine-grained admin permissions - Oleria derives the three admin tiers from each user’s admin flags. It doesn’t import Bonusly’s fine-grained admin permissions.
  • No MFA or SSO enrollment data - Bonusly exposes no per-user or company-level MFA or SSO field. Oleria reports these as unavailable, not as a false negative.
  • No API-access flag - Bonusly has no per-user API-access indicator, so this field is always reported as not granted.
  • No activity - Bonusly has no audit-log or activity-stream endpoint, so no activity is discovered.

​
Contact us

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