Orchestrate SaaS access across the employee lifecycle

The majority of Trelica customers use Okta – we're designed to complement rather than duplicate or conflict with Identify Providers. Depending on how much you've invested in Okta, it's likely that in many situations, it's just removing access to apps and not removing actual accounts and licenses. Even for the subset of apps where you've configured SCIM for (de)provisioning it's unlikely that the more granular actions around reassigning resources are supported.

Yes - we have connectors for over 30 HRIS, including popular options such as BambooHR, HiBob, and Workday. Trelica maintains a single profile for a user, which can be populated with data from multiple sources (with options to define the priority of these sources). The upshot is, for example, that if you don't have line managers set in your IdP, no problem: Trelica can pull that data from your HRIS and add it to the user's profile so you have the complete picture.

No - some apps simply don't have APIs that support user management, or indeed any API at all. Many vendors also commercialize API access, so you will need to be on premium plans to access the API or specific features of the API (e.g. SCIM). Automating everything isn't realistic, but Trelica will orchestrate tasks for manual actions where automation isn't possible – that means you still get a single system to manage and track processes, along with a clear audit log in one place.We've created hundreds of integrations and researched several hundred more apps for integration feasibility. During your Trelica trial, we can explain your integration options given your tech stack and the plans you're on.

Okta workflows are powerful and versatile. They can also be expensive and are inherently limited to the subset of your SaaS stack that sits behind Okta. We've also found that you need someone with real expertise to implement Okta workflows – that's great if that person remains within the team and available to you… it's not so good when you lose that resource and are left with a workflow nobody understands or is brave enough to iterate.We've tried to strike a balance with Trelica workflows that allows an IT generalist to achieve the majority of common IT ops objectives with the minimum configuration complexity.

BetterCloud was at the vanguard of the SaaS ops automation movement and remains a flexible workflow solution. Given its very tight focus on automation and lack of broader support for discovery and spend management, we've found that customers are unwilling to pay the ever-increasing subscription fees for what's become a point solution. When migrating customers from BetterCloud, we've also seen situations where workflows feel inherently ‘overengineered’, i.e. users are offered a vast range of options to arrange into what ends up being a rather consistent sequence of actions. We take a slightly different design philosophy: where the user intent is somewhat predictable, Trelica workflows offer prepackaged actions that offer an efficient route to the optimal solution.

Trelica workflows support dozens of granular actions for Google Workspace, from resource transfers to changing group assignments and even exporting email inboxes. We have a similar breadth of functionality for Entra ID, but the Microsoft Graph API has comparatively fewer standardized options, so we fall back to Powershell scripts to fill the gaps.

No. You will receive a couple of emails with tips and links to tutorial videos (and, of course, a meeting link in case you want to speak to us). No bombardment, no unwanted calls. We also have to find SaaS tools to run our business - we like testing things out for ourselves and don’t like being harassed, so we’re committed to selling with the same mindset.