docs(myorgs): document self-service 3P app access and XAA settings - #1794
Merged
Conversation
Add the third_party_client_access client attribute and the cross_app_access_resource_app Connection Profile attribute to my-organization-api.mdx and connection-profile.mdx, letting Organization admins self-service configure third-party application access and Cross App Access (XAA) Resource App status via the My Organization API and Embeddable UI Components. Cross-link from the existing tenant-admin-facing third-party-applications and domain-level-connection docs. Per-endpoint request/response details are covered by the auto-generated My Organization API reference, updated separately from the OpenAPI spec.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
Summary
Errors per inputErrors in main/docs/authenticate/enterprise-connections/self-service-enterprise-configuration/manage-self-service-enterprise-config.mdx
Run on commit 2ae40f3. |
avanscoy
reviewed
Aug 28, 2026
avanscoy
reviewed
Aug 28, 2026
avanscoy
reviewed
Aug 28, 2026
avanscoy
reviewed
Aug 28, 2026
avanscoy
reviewed
Aug 28, 2026
avanscoy
reviewed
Aug 28, 2026
Co-authored-by: Amanda VS <amanda.vanscoy@auth0.com>
…ise config
Address code review feedback on the 3PA/XAA My Organization API docs: standardize on "Organization Admins" and "Resource Application" terminology, clarify the Connection Profile and My Organization API cross-app-access descriptions ("configure a connection to act as a XAA Resource Application"), revert an unwanted step-title rewording, and fix cross-reference links (promote-connections-to-domain-level.mdx now points to Connection Profile, moved to the end of the article; configure-third-party-applications.mdx keeps its existing target).
Also extend manage-self-service-enterprise-config.mdx: refine the Cross App Access - Resource Application ticket option's wording for new connections, and add the same optional step to the existing-connections ticket flow, between Domain Verification and Provisioning.
avanscoy
approved these changes
Sep 1, 2026
avanscoy
added
main-docs
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
2 participants
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.
Description
Add the third_party_client_access client attribute and the cross_app_access_resource_app Connection Profile attribute to my-organization-api.mdx and connection-profile.mdx, letting Organization admins self-service configure third-party application access and Cross App Access (XAA) Resource App status via the My Organization API and Embeddable UI Components. Cross-link from the existing tenant-admin-facing third-party-applications and domain-level-connection docs. Per-endpoint request/response details are covered by the auto-generated My Organization API reference, updated separately from the OpenAPI spec.