Skip to content

Conversation

@AmberAlston
Copy link
Member

@AmberAlston AmberAlston commented Oct 20, 2025

Add note about handling Safe Link users
@AmberAlston AmberAlston requested a review from a team as a code owner October 20, 2025 17:25
@netlify
Copy link

netlify bot commented Oct 20, 2025

Deploy Preview for replicated-docs ready!

Name Link
🔨 Latest commit f753302
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs/deploys/68f6a04706071d0008ec1303
😎 Deploy Preview https://deploy-preview-3602--replicated-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link

netlify bot commented Oct 20, 2025

Deploy Preview for replicated-docs-upgrade ready!

Name Link
🔨 Latest commit f753302
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs-upgrade/deploys/68f6a0475542a600078da142
😎 Deploy Preview https://deploy-preview-3602--replicated-docs-upgrade.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@replicated-ci replicated-ci added type::docs Improvements or additions to documentation type::feature labels Oct 20, 2025
As shown in the diagram above, your licensed customers can access the installation and update instructions for one or more application releases by logging in to the Enterprise Portal. The Enterprise Portal tracks the customer's installation attempts and progress, and shares those insights back to the Vendor Portal. After installing, customers can also upload support bundles in the Enterprise Portal. Support bundles uploaded to the Enterprise Portal are automatically made available to you in the Vendor Portal.

You can enable and disable access to the Enterprise Portal for all customers, or on a per-customer basis. For more information about how to enable access, see [Manage Customer Access](/vendor/enterprise-portal-invite#manage-ep-access).

Copy link
Contributor

Choose a reason for hiding this comment

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

^ unrelated, but I noticed this was down under the Customize section. Moved up to the overview

If you use a custom domain for the Replicated Enterprise Portal and any of your customers use link transformers such as Microsoft Defender Safe Links, then there is a known issue where legitimate URLs in emails generated by the Enterprise Portal can break due to rewrapping. To avoid this issue, request a "Do not rewrite the following URLs" exclusion policy for your custom Enterprise Portal domain.

For more information, see [About the Enterprise Portal](enterprise-portal-about).

Copy link
Contributor

Choose a reason for hiding this comment

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

^ I was thinking this could fit well in the custom domains topic since it sounds like it's specific to using a custom domain. also added a note down in the procedure below that links back up to this known issue

paigecalvert
paigecalvert previously approved these changes Oct 20, 2025
Copy link
Contributor

@paigecalvert paigecalvert left a comment

Choose a reason for hiding this comment

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

I think we might be able to fit this in the custom domains topic instead. LMK what you think of these changes

The other thing I might typically do is add this as a known issue in the release notes, if it makes sense and there's a version where it could be tied to. If not, nbd

@AmberAlston AmberAlston merged commit 4b95c77 into main Oct 20, 2025
5 checks passed
@AmberAlston AmberAlston deleted the AmberAlston-patch-1 branch October 20, 2025 21:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type::docs Improvements or additions to documentation type::feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants