docs: Add SCIM domain validation requirements and activity logging events#15316
Open
inkeep[bot] wants to merge 2 commits intomasterfrom
Open
docs: Add SCIM domain validation requirements and activity logging events#15316inkeep[bot] wants to merge 2 commits intomasterfrom
inkeep[bot] wants to merge 2 commits intomasterfrom
Conversation
Documents the email domain matching requirement for SCIM provisioning added in PostHog/posthog#49160. SCIM now validates that provisioned users' email domains match the organization's verified authentication domain to prevent cross-tenant user adoption.
Based on PR PostHog/posthog#49160 which adds comprehensive activity logging for SCIM operations including user and group provisioning, updating, and deprovisioning.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Deploy preview
|
Contributor
|
Vale prose linter → found 4 errors, 75 warnings, 8 suggestions in your markdown Full report → Copy the linter results into an LLM to batch-fix issues. Linter being weird? Update the rules!
|
| Line | Severity | Message | Rule |
|---|---|---|---|
| 2:17 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 19:10 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 30:10 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 51:13 | warning | 'deprovisioned' is a possible misspelling. | PostHogBase.Spelling |
| 54:14 | warning | 'deprovisioned' is a possible misspelling. | PostHogBase.Spelling |
| 67:27 | warning | Use 'project token' instead of 'project API key'. The project token (phc_) is not an API key. | PostHogBase.ProjectToken |
| 77:3 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'Feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 86:3 | warning | Capitalize 'Data Pipelines' for PostHog's product. Use 'Data pipelines' for the general industry concept. | PostHogBase.ProductNames |
| 88:3 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'Data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 89:3 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'Data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 94:3 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'Error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 110:11 | suggestion | Address the reader directly. Use 'you' instead of 'The user'. | PostHogDocs.DirectAddress |
| 154:23 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 156:41 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 163:33 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 175:22 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 181:21 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 183:72 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 183:87 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 185:14 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 185:269 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 185:287 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 191:50 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 204:73 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 214:104 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 216:132 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 220:19 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 230:50 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 241:64 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 241:79 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 249:44 | warning | Capitalize 'Data Pipelines' for PostHog's product. Use 'data pipelines' for the general industry concept. | PostHogBase.ProductNames |
| 249:250 | warning | Capitalize 'Data Pipelines' for PostHog's product. Use 'data pipelines' for the general industry concept. | PostHogBase.ProductNames |
| 253:10 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 271:41 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'Feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 284:105 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 296:10 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 298:78 | warning | 'addon' is a possible misspelling. | PostHogBase.Spelling |
| 300:18 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 304:10 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 306:22 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 308:29 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 323:113 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 334:50 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 349:12 | suggestion | Address the reader directly. Use 'you' instead of 'the user'. | PostHogDocs.DirectAddress |
| 356:50 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 364:22 | warning | Capitalize 'Endpoints' for PostHog's product. Use 'endpoints' for the general industry concept. | PostHogBase.ProductNames |
| 364:68 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 364:177 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 368:29 | warning | Capitalize 'Endpoints' for PostHog's product. Use 'endpoints' for the general industry concept. | PostHogBase.ProductNames |
| 372:35 | warning | Capitalize 'Endpoints' for PostHog's product. Use 'endpoints' for the general industry concept. | PostHogBase.ProductNames |
| 379:6 | warning | Capitalize 'Endpoints' for PostHog's product. Use 'endpoints' for the general industry concept. | PostHogBase.ProductNames |
| 379:32 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 385:22 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 385:34 | warning | Use 'API' instead of 'api'. | Vale.Terms |
| 385:53 | warning | Use 'UI' instead of 'ui'. | Vale.Terms |
| 386:22 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 386:34 | warning | Use 'API' instead of 'api'. | Vale.Terms |
| 386:53 | warning | Use 'UI' instead of 'ui'. | Vale.Terms |
| 388:48 | warning | Capitalize 'Endpoints' for PostHog's product. Use 'endpoints' for the general industry concept. | PostHogBase.ProductNames |
| 392:27 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 394:20 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 394:193 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 396:22 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 396:106 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 400:10 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 400:108 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 404:10 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 406:27 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
contents/docs/settings/sso.mdx — 0 errors, 13 warnings, 6 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 68:81 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 86:81 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 105:96 | warning | 'OAuth' is a possible misspelling. | PostHogBase.Spelling |
| 107:54 | warning | Use American English. Use 'organization' instead of 'organisation'. | PostHogBase.AmericanEnglish |
| 107:121 | warning | 'OAuth' is a possible misspelling. | PostHogBase.Spelling |
| 107:139 | warning | 'OAuth' is a possible misspelling. | PostHogBase.Spelling |
| 111:40 | warning | Use 'URL' instead of 'url'. | Vale.Terms |
| 112:54 | warning | Use 'URL' instead of 'url'. | Vale.Terms |
| 128:40 | warning | Use 'URL' instead of 'url'. | Vale.Terms |
| 145:49 | warning | 'OAuth' is a possible misspelling. | PostHogBase.Spelling |
| 154:139 | warning | 'OAuth' is a possible misspelling. | PostHogBase.Spelling |
| 160:326 | suggestion | Address the reader directly. Use 'you can' instead of 'users can'. | PostHogDocs.DirectAddress |
| 170:58 | suggestion | Address the reader directly. Use 'you' instead of 'the user'. | PostHogDocs.DirectAddress |
| 172:103 | suggestion | Address the reader directly. Use 'you can' instead of 'users can'. | PostHogDocs.DirectAddress |
| 242:39 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 285:24 | suggestion | Address the reader directly. Use 'you' instead of 'the user'. | PostHogDocs.DirectAddress |
| 286:29 | suggestion | Address the reader directly. Use 'you' instead of 'the user'. | PostHogDocs.DirectAddress |
| 287:28 | suggestion | Address the reader directly. Use 'you' instead of 'the user'. | PostHogDocs.DirectAddress |
| 348:58 | warning | 'Entra' is a possible misspelling. | PostHogBase.Spelling |
Piccirello
requested changes
Feb 26, 2026
Member
Piccirello
left a comment
Piccirello
left a comment
There was a problem hiding this comment.
Keep the SCIM domain validation requirements but remove the SCIM activity logging events since they're only available to PostHog staff.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR updates the documentation to reflect changes introduced in PostHog/posthog#49160, which adds security improvements to SCIM provisioning.
Changes
1. SCIM domain validation requirements (
contents/docs/settings/sso.mdx)Added a new "Domain requirements" subsection to the SCIM documentation that explains:
2. SCIM activity logging events (
contents/docs/settings/activity-logs.mdx)Added six new SCIM-related events to the organization-level events table:
This PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.