Source
Hosting choice, teams & portability — found from sitemap — Netigate
Checked for Netigate on 28 Oct 2026
- Page
- https://support.netigate.net/en/articles/759025-directory-sync-scim-2-0
- Checked
- 28 Oct 2026, 14:35 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:7d6731795fe1b81d501916efe9e3ce9af54db2da7407f62378a596feae24a797
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
SCIM directory sync Report an error
“Directory sync (SCIM 2.0) keeps your Netigate Hub users in sync with your identity provider (e.g. Microsoft Entra ID).”
-
SCIM requires SSO Report an error
“You need SSO already set up before you can enable directory sync - it cannot be turned on for a tenant that doesn't have it configured yet.”
-
SCIM supported idps Report an error
“Microsoft Entra ID (formerly Azure AD) Okta”
-
SCIM any provider Report an error
“Using a provider that isn't listed? Get in touch — if it supports SCIM 2.0, it will most likely work.”
-
SCIM group mapping Report an error
“A single identity-provider group can grant access to multiple products and multiple groups/roles at once.”
-
Roles available Report an error
“Roles are not account-specific - there are always at least three available: Admin, System user, and Standard user.”
-
Mapping draft activate Report an error
“Only once you press Activate does the rule take effect, and everyone currently in that group is provisioned right away.”
-
SCIM externalid recommendation Report an error
“Set externalId to map to objectId - highly recommended, do this before turning provisioning on.”
-
SCIM matching by email Report an error
“Their existing account is matched by email and linked - no duplicate account is created.”
-
SCIM deactivation content reassignment Report an error
“Deactivated immediately, with any content they owned reassigned so nothing is left ownerless”
-
SCIM manual edit lock Report an error
“once a person is picked up by directory sync, they become locked from manual editing in the Hub and in Feedback/Insights user management”
-
SCIM okta removal behaviour Report an error
“Okta — removing a user from the Netigate application marks them as inactive rather than deleting them, which removes their access as expected. Suspending a user in Okta does not send a signal to Netigate, so use removal rather than suspension.”
-
SCIM contact Report an error
“Still have questions? Contact support@netigate.net for more info.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The Academic Researcher Hosting choice, teams & portability
- The Data Protection Officer Hosting choice, teams & portability
- The HR Lead Hosting choice, teams & portability
- The Market Researcher Hosting choice, teams & portability
- The Operations Manager Hosting choice, teams & portability
- The Skeptic Hosting choice, teams & portability