Source
API, monitoring as code & team administration — found from sitemap — Better Stack Uptime
Checked for Better Stack Uptime on 1 Nov 2026
- Page
- https://betterstack.com/docs/uptime/okta-sso/scim-setup-instructions/
- Checked
- 1 Nov 2026, 10:24 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:e6517cd89cbe371dedf791ac2a5510812139c157b578af970dcd670001fc44a1
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
SCIM provisioning Report an error
“Set up SCIM for automatic user provisioning and profile synchronization from Okta to Better Stack.”
-
SCIM prerequisite SSO Report an error
“User provisioning using SCIM requires a working Single Sign-On (SSO) setup with Okta.”
-
SCIM supported features Report an error
“Create users Update user attributes Deactivate users Sync password Group push Import users and groups”
-
SCIM bearer token Report an error
“In your Okta SSO settings in Better Stack, click Enable provisioning in the Provisioning section. Copy the Bearer token.”
-
SCIM group push teams Report an error
“We also support pushing user groups from Okta. Each group will create a new team in Better Stack with the assigned users.”
-
SCIM group deprovision warning Report an error
“Deprovisioning an Okta group from the Better Stack application will permanently delete the corresponding team and all its resources in Better Stack.”
-
SCIM user deactivation behavior Report an error
“When you deactivate or remove a user from the SCIM integration in Okta, we automatically remove them from your Better Stack organization.”
-
SCIM cross org user retention Report an error
“If the user belongs to another organization, their account is not deleted completely—they are only detached from your organization and teams. Reconnecting the user via SCIM will re-add them.”
-
SCIM last admin removal blocked Report an error
“SCIM requests to remove your organization's last admin return HTTP 400 with the detail "At least one user must be an admin."”
-
SCIM username format Report an error
“For Application username format, select Email.”
Scores citing this record
- The Agency Developer API, monitoring as code & team administration
- The Customer Support Lead API, monitoring as code & team administration
- The E-Commerce Operations Manager API, monitoring as code & team administration
- The SaaS Platform Engineer API, monitoring as code & team administration
- The Information Security Officer API, monitoring as code & team administration
- The Skeptic API, monitoring as code & team administration