Public sector · Courts and justice
Tyler Odyssey user provisioning with Okta
Court case management system for state and county trial courts, clerks and justice partners. SCIM support is not published.
More local government apps →What Okta covers for Tyler Odyssey, and what StitchOps adds.
Okta signs users in and manages accounts where the app supports it in the Okta Integration Network. StitchOps covers the rest of the Tyler Odyssey account lifecycle.
Not in the Okta Integration Network.
StitchOps covers 8 of 8 capabilities for Tyler Odyssey.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | No SAML or OIDC in the OIN. | Enterprise password management signs users in to Tyler Odyssey with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares Tyler Odyssey logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the Tyler Odyssey account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes Tyler Odyssey roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes Tyler Odyssey access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal. |
| Password rotation | No password rotation in Tyler Odyssey. | Changes the Tyler Odyssey password on a schedule and the day someone leaves, and updates your vault in the same run. |
| Access reviews | No connector to read or remove Tyler Odyssey accounts. | Pulls the Tyler Odyssey user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside Tyler Odyssey. | Step level evidence for every action StitchOps takes in Tyler Odyssey. |
Single sign on
Okta, from the OIN
No SAML or OIDC in the OIN.
StitchOps
Enterprise password management signs users in to Tyler Odyssey with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Tyler Odyssey logins and their MFA across a team, with credentials kept in your vault.
Joiners
Okta, from the OIN
No account creation in the OIN.
StitchOps
Creates the Tyler Odyssey account with the right role on day one, anywhere a person can log in and act.
Movers
Okta, from the OIN
No account updates in the OIN.
StitchOps
Changes Tyler Odyssey roles and access when someone changes jobs, anywhere a person can log in and act.
Leavers
Okta, from the OIN
No deprovisioning in the OIN.
StitchOps
Removes Tyler Odyssey access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal.
Password rotation
Okta, from the OIN
No password rotation in Tyler Odyssey.
StitchOps
Changes the Tyler Odyssey password on a schedule and the day someone leaves, and updates your vault in the same run.
Access reviews
Okta, from the OIN
No connector to read or remove Tyler Odyssey accounts.
StitchOps
Pulls the Tyler Odyssey user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Tyler Odyssey.
StitchOps
Step level evidence for every action StitchOps takes in Tyler Odyssey.
Okta coverage from the Okta Integration Network, read October 24, 2026. Tyler Odyssey has no OIN listing. StitchOps for Okta →
SCIM and Okta status
What Tyler Odyssey supports today.
Tyler Odyssey does not publish SCIM support, so we list it as Not published. Ask the vendor before you count on it.
- SCIM status
- Not published
- Okta Integration Network
- Not in the Okta Integration Network. Read October 24, 2026.
- Vendor
- Tyler Technologies
- Data it handles
- CJIS
Data tags describe the data Tyler Odyssey handles, not a certification StitchOps holds.
Last verified 2026-10-20.Sources:Product pageOkta Integration Network
More local government apps →Every public sector app →What the SCIM tax is →
What StitchOps automates in Tyler Odyssey.
StitchOps creates, updates and removes Enterprise Justice user accounts and security groups, and pulls the user list for access reviews. The StitchOps worker runs inside your environment, and your data never leaves your network or vault.
Joiners
Create the Tyler Odyssey account with the right role when your HR system or Okta says someone starts.
Movers and leavers
Change Tyler Odyssey roles when someone changes jobs, and remove access the day they leave.
Password rotation
Rotate shared and service logins in Tyler Odyssey on a schedule and after every offboarding, and update your vault in the same run.
Access review evidence
List who can sign in to Tyler Odyssey on a schedule, compare it to your directory, and keep step level evidence for auditors.
Common questions.
Does Tyler Odyssey support SCIM?
Tyler Odyssey does not publish SCIM support, so we list it as Not published. Ask the vendor before you count on it.
Can Tyler Odyssey accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Tyler Odyssey accounts on the plan you already have, triggered by the events your identity provider already sends. It uses an API when one exists and works anywhere a person can log in and act when one does not.
Is Tyler Odyssey in the Okta Integration Network?
No. As of October 24, 2026, the OIN has no listing for Tyler Odyssey. Okta can sign users in only through a custom app if Tyler Odyssey supports SAML or OIDC, and has no connector to manage Tyler Odyssey accounts.
Can Okta deprovision Tyler Odyssey users?
Not through an OIN connector. StitchOps removes Tyler Odyssey accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate Tyler Odyssey passwords when someone leaves?
StitchOps logs in to Tyler Odyssey, sets a new password, confirms it took effect, and updates 1Password, Keeper or the StitchOps vault in the same run.
Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.
Start with one workflow that never had an API.
Fifteen minutes on your top three manual processes. We tell you which one to run first.