Skip to main content
Connect Splashtop to Oleria to see who has access to your Splashtop team: every user, their role, the groups they belong to, and a trail of joins, departures, and failed sign-ins. Oleria reads this data from the Splashtop Open API using a Web API token, so you can see where access is over-provisioned and act on it directly from Oleria.

​
What Oleria discovers

Once connected, Oleria continuously discovers and maps the following from your Splashtop team:
  • Accounts - every team user, with email, name, role, status, whether two-step verification is on, whether the user signs in through single sign-on, license type, and last sign-in.
  • Roles - Owner, Super Admin, Admin, Group Admin, Member, and Remote User, and which accounts hold each. Oleria shows only the roles your team actually uses.
  • User groups - Splashtop groups that hold users, and their membership.
  • Activity - users joining or leaving the team, and failed sign-ins, including sign-ins blocked by an IP or MAC address allowlist. Admin actions such as role and group changes aren’t in Splashtop’s team history, so they don’t appear in Oleria.
This integration covers who your users are and what role they hold. It does not read your computers or which computers each user can reach, so Oleria does not populate Access Inventory or resource-level Access Graph data for Splashtop.

​
Prerequisites

  • A Splashtop Enterprise plan. Web API tokens are not available on other plans.
  • Team owner access in Splashtop. Only the team owner can create a Web API token.
  • Admin access on the Oleria platform to add a new integration.

​
Create a Web API token in Splashtop

1

Open Web API tokens

Sign in to the Splashtop web console as the team owner. Go to Account Settings -> Web API Tokens -> Manage.
2

Create the token

Select Create API token and choose an expiration date. Grant these scopes:
Copy the token immediately and treat it like a password. These scopes let anyone holding the token read your team’s users and groups, disable users, and change group membership, whether or not you enable remediation in Oleria.
Splashtop tokens expire on the date you choose. Set a reminder to create a new token and update the integration in Oleria before it expires.

​
Connect Splashtop to Oleria

If you connected Splashtop to Oleria earlier using a SCIM Base URL and token, that connection no longer syncs. Remove the old Splashtop instance, create a Web API token as described above, and add Splashtop again so you can choose your region.
1

Open the integration

Go to your Oleria workspace, select Integrations, then select Splashtop.
2

Complete the connection form

Fill in the connection form:
3

Save the integration

Select Authenticate to validate and save the integration. Oleria calls Splashtop to confirm the token works and has the team_users, team_groups, and logs scopes. If a scope is missing, create a new token in Splashtop with all of them and try again.

​
Verify the integration

Confirm the new instance appears on the Connected tab of your Oleria Integrations page. After the first sync completes, you can review the discovered accounts, roles, and groups. Activity syncs on a separate cadence from users and groups, on Oleria’s regular sync schedule.
Splashtop only returns team history from the last year. Events older than that aren’t available in Oleria.
The Region is set when you create the integration and can’t be changed afterward. To move to a different region, create a new integration. If you rotate your API token, edit the integration, paste the new token, and select Update.

​
Remediation actions

Standard integrations are configured read-only. If you enable remediation for Splashtop, Oleria can take these actions with the same token:
A Splashtop user belongs to exactly one group. Adding a user to a group moves them out of their current one, and removing a user from a group moves them to the team’s default group.

​
Contact us

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