Public sector · Public safety and CAD
Mark43 user provisioning with Okta
Cloud records management and computer aided dispatch software for police and public safety agencies. The vendor documents SCIM provisioning; the plan it needs is not published.
More local government apps →What Okta covers for Mark43, 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 Mark43 account lifecycle.
Not in the Okta Integration Network.
StitchOps covers 8 of 8 capabilities for Mark43.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | No SAML or OIDC in the OIN. | Enterprise password management signs users in to Mark43 with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares Mark43 logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the Mark43 account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes Mark43 roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes Mark43 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 Mark43. | Changes the Mark43 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 Mark43 accounts. | Pulls the Mark43 user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside Mark43. | Step level evidence for every action StitchOps takes in Mark43. |
Single sign on
Okta, from the OIN
No SAML or OIDC in the OIN.
StitchOps
Enterprise password management signs users in to Mark43 with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Mark43 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 Mark43 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 Mark43 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 Mark43 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 Mark43.
StitchOps
Changes the Mark43 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 Mark43 accounts.
StitchOps
Pulls the Mark43 user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Mark43.
StitchOps
Step level evidence for every action StitchOps takes in Mark43.
Okta coverage from the Okta Integration Network, read October 24, 2026. Mark43 has no OIN listing. StitchOps for Okta →
SCIM and Okta status
What Mark43 supports today.
Mark43 documents SCIM provisioning for Mark43. The plan or license it needs is not published, so 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
- Mark43
- Deployment
- Cloud (SaaS)
- Data it handles
- CJIS
Data tags describe the data Mark43 handles, not a certification StitchOps holds.
Last verified 2026-10-20.Sources:Product pageSCIM documentationOkta Integration Network
More local government apps →Every public sector app →What the SCIM tax is →
What StitchOps automates in Mark43.
StitchOps creates, updates and removes Mark43 user accounts and roles, 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 Mark43 account with the right role when your HR system or Okta says someone starts.
Movers and leavers
Change Mark43 roles when someone changes jobs, and remove access the day they leave.
Password rotation
Rotate shared and service logins in Mark43 on a schedule and after every offboarding, and update your vault in the same run.
Access review evidence
List who can sign in to Mark43 on a schedule, compare it to your directory, and keep step level evidence for auditors.
Common questions.
Does Mark43 support SCIM?
Mark43 documents SCIM provisioning for Mark43. The plan or license it needs is not published, so ask the vendor before you count on it.
Can Mark43 accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Mark43 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 Mark43 in the Okta Integration Network?
No. As of October 24, 2026, the OIN has no listing for Mark43. Okta can sign users in only through a custom app if Mark43 supports SAML or OIDC, and has no connector to manage Mark43 accounts.
Can Okta deprovision Mark43 users?
Not through an OIN connector. StitchOps removes Mark43 accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate Mark43 passwords when someone leaves?
StitchOps logs in to Mark43, 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.