Public sector · Safety and filtering
Securly Filter user provisioning with Okta
Cloud web filter for K12 schools that applies browsing policies to student devices and reports activity. SCIM support is not published.
More K12 apps →What Okta covers for Securly Filter, 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 Securly Filter account lifecycle.
Not in the Okta Integration Network.
StitchOps covers 8 of 8 capabilities for Securly Filter.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | No SAML or OIDC in the OIN. | Enterprise password management signs users in to Securly Filter with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares Securly Filter logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the Securly Filter account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes Securly Filter roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes Securly Filter 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 Securly Filter. | Changes the Securly Filter 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 Securly Filter accounts. | Pulls the Securly Filter user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside Securly Filter. | Step level evidence for every action StitchOps takes in Securly Filter. |
Single sign on
Okta, from the OIN
No SAML or OIDC in the OIN.
StitchOps
Enterprise password management signs users in to Securly Filter with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Securly Filter 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 Securly Filter 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 Securly Filter 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 Securly Filter 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 Securly Filter.
StitchOps
Changes the Securly Filter 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 Securly Filter accounts.
StitchOps
Pulls the Securly Filter user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Securly Filter.
StitchOps
Step level evidence for every action StitchOps takes in Securly Filter.
Okta coverage from the Okta Integration Network, read October 20, 2026. Securly Filter has no OIN listing. StitchOps for Okta →
SCIM and Okta status
What Securly Filter supports today.
Securly Filter 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 20, 2026.
- Vendor
- Securly
- Deployment
- Cloud (SaaS)
- Used in
- K12
- Data it handles
- FERPA, COPPA
Data tags describe the data Securly Filter handles, not a certification StitchOps holds.
Last verified 2026-10-20.Sources:Product pageOkta Integration Network
More K12 apps →Every public sector app →What the SCIM tax is →
What StitchOps automates in Securly Filter.
StitchOps keeps Securly admin access and policy groups current, and pulls the admin list for access reviews. The StitchOps worker runs inside your environment, and your data never leaves your network or key vault.
Joiners
Create the Securly Filter account with the right role when your HR system or Okta says someone starts.
Movers and leavers
Change Securly Filter roles when someone changes jobs, and remove access the day they leave.
Password rotation
Rotate shared and service logins in Securly Filter on a schedule and after every offboarding, and update your vault in the same run.
Access review evidence
List who can sign in to Securly Filter on a schedule, compare it to your directory, and keep step level evidence for auditors.
Common questions.
Does Securly Filter support SCIM?
Securly Filter does not publish SCIM support, so we list it as Not published. Ask the vendor before you count on it.
Can Securly Filter accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Securly Filter 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 Securly Filter in the Okta Integration Network?
No. As of October 20, 2026, the OIN has no listing for Securly Filter. Okta can sign users in only through a custom app if Securly Filter supports SAML or OIDC, and has no connector to manage Securly Filter accounts.
Can Okta deprovision Securly Filter users?
Not through an OIN connector. StitchOps removes Securly Filter accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate Securly Filter passwords when someone leaves?
StitchOps logs in to Securly Filter, 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.