Skip to main content
Freshservice is an IT service management (ITSM) platform for ticketing and asset management. Connect your Freshservice domain to Oleria to bring agent and group access into your identity and access graph, without a dedicated Freshservice-specific integration.

​
What Oleria discovers

  • Agent accounts and profile attributes synced from Freshservice’s directory.
  • Groups and their memberships.
Oleria uses this data for dormant account detection and access reviews, refreshed on Freshservice’s standard sync schedule.

​
Prerequisites

  • Admin access in Freshservice with permission to generate an API key for a service account.
  • Admin access on the Oleria platform to add a new integration.
The exact location of these settings can change over time. If the steps below don’t match what you see, refer to Freshservice’s own API documentation.

​
Get your SCIM credentials from Freshservice

1

Generate an API key in Freshservice

Sign in to Freshservice as an admin, go to Admin → API → API Key, and generate an API key for the integration service account.
2

Copy your SCIM Base URL and Authentication token

Copy both values before you leave the page - you’ll paste them into Oleria in the next section:
  • SCIM Base URL - the HTTPS API endpoint for your Freshservice domain.
  • Authentication token - the API key you generated.
Copy the key now. Many applications display it only once. Store it securely and rotate it per your organization’s security policy.

​
Connect Freshservice to Oleria

1

Open the integration

Go to your Oleria workspace, select Integrations, then select the Freshservice tile.
2

Complete the connection form

Select Continue and fill in the connection form:
3

Save the integration

Select Connect to validate the credentials and save the integration.

​
Verify the integration

Confirm the new instance appears in your Oleria workspace under Connected Integrations with a status of Healthy. Oleria syncs agents and groups from Freshservice on the standard SCIM provisioning schedule once the initial sync completes.
If Freshservice rotates your API key, update the Authentication token in Oleria by editing the integration.

​
Governance actions

Oleria can also invoke lifecycle actions in Freshservice when the key you provide has write access:
  • Enable or disable a user account
  • Add or remove a user from a group
  • Create a new user or group
Many teams start with a read-only key for visibility, then grant write access once they’re ready to automate remediation in Freshservice.

​
Contact us

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