Skip to content

Conversation

@lrzhou25
Copy link
Contributor

By submitting a PR to this repository, you agree to the terms within the Auth0 Code of Conduct. Please see the contributing guidelines for how to create and submit a high-quality PR for this repo.

Description

Describe the purpose of this PR along with any background information and the impacts of the proposed change. For the benefit of the community, please do not assume prior context.

Provide details that support your chosen implementation, including: breaking changes, alternatives considered, changes to the API, etc.

If the UI is being changed, please provide screenshots.

References

Include any links supporting this change such as a:

  • GitHub Issue/PR number addressed or fixed
  • Auth0 Community post
  • StackOverflow post
  • Support forum thread
  • Related pull requests/issues from other repos

If there are no references, simply delete this section.

Testing

Describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If this library has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.

Please include any manual steps for testing end-to-end or functionality not covered by unit/integration tests.

Also include details of the environment this PR was developed in (language/platform/browser version).

  • This change adds test coverage for new/changed/fixed functionality

Checklist

  • I have added documentation for new/changed functionality in this PR or in auth0.com/docs
  • All active GitHub checks for tests, formatting, and security are passing
  • The correct base branch is being used, if not the default branch

@lrzhou25 lrzhou25 added main-docs Changes related to auth0's main docs (https://auth0.com/docs) DO NOT MERGE Only the PR author should merge, even if approved. labels Nov 12, 2025
@lrzhou25 lrzhou25 changed the title Updated TV and added Connected Accounts doc [DO NOT MERGE] Updated TV and added Connected Accounts doc Nov 12, 2025
Comment on lines +193 to +195
<td><strong>Purpose</strong></td>
<td>Enable the connection for Authentication, Connected Accounts for Token Vault, or both. To learn more, read [User authentication vs Connected Accounts](/docs/secure/tokens/connected-accounts-for-token-vault#user-authentication-vs-connected-accounts).</td>
</tr>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Enable the connection for Authentication, Connected Accounts for Token Vault, or both

This article is for authentication only, right? Why are we saying that tenants can enable the "Connected Accounts for Token Vault" option?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@siacomuzzi the intent was to capture all the purpose settings shown to users in the UI here, and if users want to learn more about connected accounts, they can click on the link

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, but is this a generic article about how to configure a connection, or about how to configure a connection for authentication only?

If the latter, we should say that the requirement is to have the Purpose set to "Authentication" or "Both".

But, if this article is a generic article about connection provisioning, feel free to ignore my comment. It confused me that it’s under the “/authenticate/” path.

Copy link
Contributor Author

@lrzhou25 lrzhou25 Nov 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you have a point that this doc + the docs under /authenticate are technically for login. unfortunately, there isn't a better place atm to document all the purpose setting on the main docs. eventually, the docs team will need to come up with a strategy on either updating the connection docs on Marketplace or migrating those connection docs back to the main docs, but for GA, hopefully this is an okay workaround :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor:

Connected Accounts for Token Vault

this should be "Connected Accounts with Token Vault":

image

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@siacomuzzi the actual feature name is "Connected Accounts for Token Vault." i synced with @cristiandouce and understand that the copy will reflect this in a future milestone:
image (2)

@lrzhou25 lrzhou25 merged commit 4046519 into main Nov 18, 2025
9 checks passed
@lrzhou25 lrzhou25 deleted the feat/connected_accounts_for_tv_main_docs branch November 18, 2025 23:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

DO NOT MERGE Only the PR author should merge, even if approved. main-docs Changes related to auth0's main docs (https://auth0.com/docs)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants