Skip to content

Enterprise portal docs (draft) #3218

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.

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

Merged
merged 21 commits into from
May 20, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion docs/vendor/custom-domains-using.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Use Custom Domains

This topic describes how to use the Replicated Vendor Portal to add and manage custom domains to alias the Replicated registry, the Replicated proxy registry, the Replicated app service, and the Download Portal.
This topic describes how to use the Replicated Vendor Portal to add and manage custom domains to alias the Replicated registry, the Replicated proxy registry, the Replicated app service, the Replicated Enterprise Portal and the Replicated Download Portal.

For information about adding and managing custom domains with the Vendor API v3, see the [customHostnames](https://replicated-vendor-api.readme.io/reference/createcustomhostname) section in the Vendor API v3 documentation.

Expand Down
2 changes: 2 additions & 0 deletions docs/vendor/custom-domains.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,8 @@ You can configure custom domains for the following services:

- **Replicated app service:** Upstream application YAML and metadata, including a license ID, are pulled from the app service. By default, this service uses the domain `replicated.app`. Replicated recommends using a CNAME such as `updates.{your app name}.com`.

- **Enterprise Portal:** The Enterprise Portal is a web-based portal that provides end customers with a centralized location for managing their installation. By default, the Enterprise Portal uses the domain **`[DOMAIN].replicated.com`**. Replicated recommending using a CNAME such as `portal.{your app name}.com` or `enterprise.{your app name}.com`.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

^ On the About Custom Domains page, add Enterprise Portal to list of endpoints you can alias with a custom domain

- **Download Portal:** The Download Portal can be used to share customer license files, air gap bundles, and so on. By default, the Download Portal uses the domain `get.replicated.com`. Replicated recommends using a CNAME such as `portal.{your app name}.com` or `enterprise.{your app name}.com`.

- **Replicated registry:** Images and Helm charts can be pulled from the Replicated registry. By default, this registry uses the domain `registry.replicated.com`. Replicated recommends using a CNAME such as `registry.{your app name}.com`.
Expand Down
64 changes: 63 additions & 1 deletion docs/vendor/customer-reporting.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,9 @@ As shown in the image above, the **Reporting** page has the following main secti
* [Manage Customer](#manage-customer)
* [Time to Install](#time-to-install)
* [Download Portal](#download-portal)
* [Enterprise Portal](#enterprise-portal)
* [Instances](#instances)
* [Install Attempts](#install-attempts)

### Manage Customer

Expand Down Expand Up @@ -53,12 +55,40 @@ For more information about how to interpret the time to install metrics, see [Ti

### Download Portal

:::note
If the Replicated Enterprise Portal is enabled for the customer, then an **Enterprise Portal** section is displayed instead of the **Download Portal** section. For more information, see [Enterprise Portal](#enterprise-portal) below.
:::

From the **Download portal** section, you can:
* Manage the password for the Download Portal
* Access the unique Download Portal URL for the customer

You can use the Download Portal to give your customers access to the files they need to install your application, such as their license file or air gap bundles. For more information, see [Access a Customer's Download Portal](releases-share-download-portal).

### Enterprise Portal (Alpha)

:::note
The **Enterprise Portal** section is available only for customers with the Enterprise Portal enabled. For more information about how to enable the Enterprise Portal for a customer, see [Manage Enterprise Portal Access](/vendor/enterprise-portal-invite).
:::

The following shows an example of the **Enterprise Portal** section:

![Enterprise Portal section of customer reporting page](/images/customer-reporting-enterprise-portal.png)

[View a larger version of this image](/images/customer-reporting-enterprise-portal.png)

From the **Enterprise Portal** section, you can:
* Click **View** to access the unique Enterprise Portal for the customer
* View the status of the customer's access to the Enterprise Portal
* View the timestamp when the Enterprise Portal was most recently accessed by the customer
* View the number of users with Enterprise Portal accounts
* Click **Invite user** to invite a new user to the Enterprise Portal
* View the number of install attempts made by the customer. The **Customer Reporting > Install Attempts** section includes additional details about install attempts. For more information, see [Install Attempts](#install-attempts) below.
* View the number of service accounts created in the Enterprise Portal
* View the number of support bundles uploaded to the Enterprise Portal

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

### Instances

The **Instances** section displays details about the active application instances associated with the customer.
Expand All @@ -85,4 +115,36 @@ The **Instances** section displays the following details about each active insta
* Instance uptime data, including:
* The timestamp of the last recorded check-in for the instance. For more information about what triggers an instance check-in, see [How the Vendor Portal Collects Instance Data](instance-insights-event-data#about-reporting) in _About Instance and Event Data_.
* An uptime graph of the previous two weeks. For more information about how the Vendor Portal determines uptime, see [Instance Uptime](instance-insights-details#instance-uptime) in _Instance Details_.
* The uptime ratio in the previous two weeks.
* The uptime ratio in the previous two weeks.

### Install Attempts (Alpha)

:::note
The **Install Attempts** section is available only for customers with the Replicated Enterprise Portal enabled. For more information about how to enable the Enterprise Portal for a customer, see [Manage Enterprise Portal Access](/vendor/enterprise-portal-invite).
:::

The **Install Attempts** section includes details about the installation attempts made by users. These insights are based on the customer's activity in the Enterprise Portal.

To track install attempts, the Enterprise Portal creates a unique, _just-in-time_ service account that sends data back to the Vendor Portal when the user starts and completes the installation or takes other actions that are specific to the installation type. These service accounts also provide realtime feedback to the user on their installation progress using checkboxes and status indicators, and allow users to pause and return to an installation attempt.

The following shows an example of the **Install Attempts** section:

<img alt="Install attempts section of customer reporting page" src="/images/customer-reporting-install-attempts-expanded.png" width="700px"/>

[View a larger version of this image](/images/customer-reporting-install-attempts-expanded.png)

The **Install Attempts** section includes the following details about each installation attempt:
* The installation status (succeeded, stalled, or failed)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

^ what are the possible statuses for install attempts?

Copy link
Member

Choose a reason for hiding this comment

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

seems right

* The date and time when the installation attempt was started
* The email address of the user that initiated the installation attempt
* Installation environment details:
* **OS** or **K8s**: The operating system of the VM or bare metal server. Or, the distribution of Kubernetes running in the installation environment.
* **Mode**: If the installation is online (internet-connected) or air gap (offline).
* **Registry**: If the image registry used is online (accessed over the internet) or offline (a local registry is used). For air gap installations, the registry is always offline. Users can also optionally use a local image registry in online installations.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

^ this was a guess of what online/offline meant for the Registry field. I figure it has to do with if they have a local registry configured?

Copy link
Member

Choose a reason for hiding this comment

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

@pandemicsyn details?

Copy link
Member

Choose a reason for hiding this comment

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

i looked, this seems right

* Installation progress details, including when the installation was started and completed as well as other progress indicators that are specific to the installation type. For example:
* For installations with Helm, the Enterprise Portal reports when your image registry was accessed and when application images were pulled, as shown below:
![Helm install attempt progress details](/images/customer-reporting-install-attempts-helm.png)
[View a larger version of this image](/images/customer-reporting-install-attempts-helm.png)
* For installations with Replicated Embedded Cluster on VMs or bare metal servers, the Enterprise Portal reports when the installation assets were downloaded, as shown below:
![VM-based install attempt progress details](/images/customer-reporting-install-attempts-vm.png)
[View a larger version of this image](/images/customer-reporting-install-attempts-vm.png)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

^ I wasn't sure about the different install characteristics that determine which progress indicators are included

for example, I saw "registry login" and "images pulled" show up on certain installs, and it looked like those were all helm installs, but could use confirmation

same with "assets downloaded". those are just for EC, I guess?

Copy link
Member

Choose a reason for hiding this comment

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

yep, that's right

67 changes: 67 additions & 0 deletions docs/vendor/enterprise-portal-about.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
# About the Enterprise Portal (Alpha)

This topic provides an overview of the Replicated Enterprise Portal.

## Overview

The Enterprise Portal is a customizable, web-based portal that provides a centralized location where your customers can:
* View application install and update instructions
* Manage their team members and service accounts
* Upload support bundles
* View insights about their active and inactive instances
* And more

Your customers can access the Enterprise Portal outside their application installation environment at a custom domain that you specify, making it easier for teams to manage instances and get support.

For information about using the Enterprise Portal, see [Access and Use the Enterprise Portal](enterprise-portal-use).

The following shows an example of the Enterprise Portal dashboard:

![Enterprise Portal dashboard](/images/enterprise-portal-dashboard.png)

[View a larger version of this image](/images/enterprise-portal-dashboard.png)

## Limitations

* The Enterprise Portal is Alpha. The features and functionality of the Enterprise Portal are subject to change.

* Air gap instance records do not appear in the Enterprise Portal until the vendor uploads a support bundle for that instance. For more information, see [View Active and Inactive Instances](/vendor/enterprise-portal-use#view-active-and-inactive-instances) in _Access and Use the Enterprise Portal_.

## Comparison to the Download Portal

The Enterprise Portal is the next generation version of the Replicated Download Portal. Compared to the Download Portal, the Enterprise Portal not only provides access to installation assets and instructions, but also allows users to track available updates, manage their team and service accounts, view the status of their instances, view license details, and more. These features are designed to make it easier for your customers to manage their instances of your application from a centralized location outside of the installation environment.

You can migrate existing customers from the Download Portal to the Enterprise Portal by enabling the Enterprise Portal for their license. For more information, see [Manage Enterprise Portal Access](enterprise-portal-invite).

For more information about the Download Portal, see [Access a Customer's Download Portal](/vendor/releases-share-download-portal).

## About Customizing the Enterprise Portal

You can configure the Enterprise Portal to use a custom domain, add links and contact information, customize the look and feel of the Enterprise Portal, edit the content of invitation and notification emails, and more. Customizing the Enterprise Portal helps ensure that your customers have a consistent branding experience and can access application- and vendor-specific information.

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

For information about how to set a custom domain for the Enterprise Portal, see [Use Custom Domains](/vendor/custom-domains-using).

## About Instance Reporting with the Enterprise Portal

This section describes the instance reporting functionality of the Enterprise Portal.

### Active and Inactive Instances

The Enterprise Portal provides insights to end users about their active and inactive instances, including the application version installed, the instance status, computed metrics like the first and most recent times the instance sent data to the Vendor Portal, and more. For more information about the instance insights available in the Enterprise Portal, see [View Active and Inactive Instances](/vendor/enterprise-portal-use#view-active-and-inactive-instances) in _Access and Use the Enterprise Portal_.

![active and inactive instances](/images/enterprise-portal-instance-status-details.png)
[View a larger version of this image](/images/enterprise-portal-instance-status-details.png)

### Customer Reporting

The Enterprise Portal sends insights back to the Vendor Portal, which are surfaced on the **Customer Reporting** page. For more information, see [Enterprise Portal](/vendor/customer-reporting#enterprise-portal) in _Customer Reporting_.

These insights include details about the customer's install attempts. The Enterprise Portal tracks and reports on install attempts by creating unique, _just-in-time_ service accounts. These service accounts allow the Enterprise Portal to send data back to the Vendor Portal when the user starts and completes the installation or takes other actions that are specific to the installation type. The service accounts also provide realtime feedback to the user on their installation progress using checkboxes and status indicators, and allow users to pause and return to an installation attempt. For more information, see [Install Attempts](/vendor/customer-reporting#install-attempts) in _Customer Reporting_.

The following shows an example of the **Install Attempts** section:

<img alt="Install attempts section of customer reporting page" src="/images/customer-reporting-install-attempts-expanded.png" width="700px"/>

[View a larger version of this image](/images/customer-reporting-install-attempts-expanded.png)
104 changes: 104 additions & 0 deletions docs/vendor/enterprise-portal-configure.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,104 @@
# Customize the Enterprise Portal (Alpha)

This topic describes how to customize the Enterprise Portal, including using a custom domain, changing the branding, editing the content of invitation and notification emails, and adding custom documentation.

## Manage Enterprise Portal Settings

You can edit the settings for the Enterprise Portal to use a custom domain, provide custom links and contact information, customize the look and feel of the Enterprise Portal, and more.

To manage Enterprise Portal settings:

1. In the Vendor Portal, go to **Enterprise Portal > Settings**.

![Enterprise Portal settings page](/images/enterprise-portal-settings.png)

[View a larger version of this image](/images/enterprise-portal-settings.png)

1. Edit the settings as desired:

<table>
<tr>
<th>Field</th>
<th>Description</th>
</tr>
<tr>
<td>URL</td>
<td>The URL where customers can access the Enterprise Portal. You can change the URL to use a custom domain. For information, see [Use Custom Domains](custom-domains-using).</td>
</tr>
<tr>
<td>Title</td>
<td>The title of the Enterprise Portal. The title is displayed at the top of each page in the Enterprise Portal and is also used in email notifications.</td>
</tr>
<tr>
<td>Page overview</td>
<td>An overview of the Enterprise Portal.</td>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

^ I don't think I saw where this appears in the Enterprise Portal

Copy link
Member

Choose a reason for hiding this comment

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

it doesn't yet... i should decide if we're going to include it :)

</tr>
<tr>
<td>Support portal link</td>
<td>The URL for the portal that your customers can use to get support. This link is provided on the Enterprise Portal **Support** page.</td>
</tr>
<tr>
<td>Contact email</td>
<td>The email address that customers can use to contact you. This email address is provided on the Enterprise Portal **Support** page.</td>
</tr>
<tr>
<td>Logo</td>
<td>Upload a custom PNG logo for the Enterprise Portal. The minimum size for the logo is 160px by 160px.</td>
</tr>
<tr>
<td>Favicon</td>
<td>Upload a custom favicon for the Enterprise Portal. The favicon is displayed in the browser tab.</td>
</tr>
<tr>
<td>Background</td>
<td>Select or customize the background for the Enterprise Portal.</td>
</tr>
<tr>
<td>Colors</td>
<td>Set the primary and secondary colors for the Enterprise Portal.</td>
</tr>
</table>

1. Click **Save**.

## Configure Invitation and Notification Emails {#configure-customer-emails}

You can customize the invitation and notification emails that are sent to your customers.

To configure customer emails:

1. In the Vendor Portal, go to **Enterprise Portal > Customer emails**.

![Enterprise Portal customer emails page](/images/enterprise-portal-customer-emails.png)

[View a larger version of this image](/images/enterprise-portal-customer-emails.png)

1. For **Email Sender Verification**, in **From email address**, add the email address that you want to use as the sender for all system notifications sent to your customers, then click **Continue**. Adding a sender address helps ensure that your emails are delivered and are not marked as spam.

After the domain is verified automatically, the email address is displayed under **Verified Sender Address**.
1. For **Customer Emails**, customize the subject line and body of the emails that are sent to your customers for various system events.

![Enterprise Portal edit emails pane](/images/enterprise-portal-customer-emails-edit.png)

[View a larger version of this image](/images/enterprise-portal-customer-emails-edit.png)

## Customize Documentation

The install and update instructions available in the Enterprise Portal are automatically generated based on the install types and options enabled in the customer's license. For more information about managing the installation types and options, see [Manage Install Types for a License](/vendor/licenses-install-types).

You can also customize the documentation that is displayed in the Enterprise Portal by including a link to your installation instructions or by adding your own pre- and post-installation instructions.

To customize documentation:

1. In the Vendor Portal, go to **Enterprise Portal > Knowledge Base**.

![Enterprise Portal knowledge base page](/images/enterprise-portal-knowledge-base.png)

[View a larger version of this image](/images/enterprise-portal-knowledge-base.png)

1. In the panel on the left, select the installation type.

1. Customize the documentation for the selected installation type as desired:
1. In the documentation links section, add a link to your installation documentation. The link is displayed on the Enterprise Portal **Install** page.
1. In the documentation content section, add pre- and post-installation instructions in markdown format. Click **Preview** to see a preview of your changes.
1. Click **Save changes**.
Loading