Skip to content

docs: Add SCIM domain validation requirements and activity logging events #15316

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
inkeep wants to merge 2 commits into
base: master
Choose a base branch
from
+16 −0
Open

docs: Add SCIM domain validation requirements and activity logging events #15316

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
11ac85a
docs: add SCIM domain validation requirements to SSO docs
inkeep[bot] Feb 26, 2026
abfe7f5
Add SCIM activity log events to organization-level events table
inkeep[bot] Feb 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions contents/docs/settings/activity-logs.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,12 @@ These events track changes to organization-wide settings and membership.
| Domain verified | An authentication domain was verified |
| Organization settings changed | Organization name, logo, or other settings were updated |
| 2FA enforcement changed | Two-factor authentication requirements were modified |
| SCIM user provisioned | A user was created or added via SCIM |
| SCIM user updated | A user was modified via SCIM |
| SCIM user deprovisioned | A user was removed or deactivated via SCIM |
| SCIM group provisioned | A role was created via SCIM |
| SCIM group updated | A role was modified via SCIM |
| SCIM group deprovisioned | A role was removed via SCIM |
| *+ many more* | |

### Project-level events
Expand Down
10 changes: 10 additions & 0 deletions contents/docs/settings/sso.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -347,6 +347,16 @@ Before setting up SCIM, you need:
2. SAML SSO configured and working for your domain
3. Identity Provider that supports SCIM 2.0 (e.g., Okta, Entra ID, OneLogin)

### Domain requirements

SCIM can only provision users whose email domain matches your organization's verified authentication domain. For example, if your verified domain is `example.com`, SCIM can only create or manage users with `@example.com` email addresses. Attempts to provision users with mismatched email domains are rejected.

<CalloutBox icon="IconWarning" title="Cross-domain provisioning is blocked" type="caution">

This validation prevents cross-tenant user adoption. Your Identity Provider can only provision users for domains your organization has verified in PostHog.

</CalloutBox>

### Setting up SCIM

1. In PostHog, navigate to Organization settings and go to [Authentication domains](https://app.posthog.com/settings/organization-authentication).
Expand Down