Admin Dashboard

​

Introduction

The Admin Dashboard is an area of the Edge Infrastructure Services console available only to cloud-service and support (CS) administrators. It provides cross-enterprise visibility and controls that are not available to standard enterprise roles such as SysAdmin or SysManager. You access it from the user profile menu in the top-right corner of the console. The dashboard has two sections, accessible from the left navigation panel:

• Entitlements (under Platform): cross-enterprise usage and limits.
• EVE-OS Images (under Images): base EVE-OS images across the enterprise, with import and management actions.

​

Access

The Admin Dashboard and all content within it are visible only to users with the CS admin role. This role requires the srAll enterprise scope with Update permission on accessEnterprise. Standard enterprise roles (SysAdmin, SysManager, SysOperator, and so on) do not have access and do not see the Admin Dashboard entry in the profile menu. To open the Admin Dashboard, select your user avatar in the top-right corner of the console and select Admin Dashboard.

​

Entitlements

The Entitlements section lists usage and limits across all enterprises. It shows what each enterprise is entitled to use and how much of each entitlement the enterprise has consumed. To view entitlements, open the Admin Dashboard and select Entitlements from the left navigation panel. To view the details of a specific entitlement, select the row.

​

Entitlement details

The detail page opens with the enterprise’s usage and limits: third-party integrations, edge nodes, and users. Each shows the configured limit, and the third-party integrations card offers a Show breakdown control that lists usage by integration. Following the limits, the Feature Flags section shows which platform features the enterprise is entitled to use. Each feature card shows one of three statuses. Only features that are provisioned on the enterprise’s entitlement record appear on the detail page. If none are provisioned, the section shows “No feature flags are provisioned for this enterprise.” The Kubernetes Orchestration card appears only on Rancher-managed deployments.

​

Feature flag inheritance

Edge Infrastructure Services evaluates feature flags at two levels. Both levels must be enabled for a feature to work:

• Root enterprise: the base configuration. A feature disabled here is disabled across all child enterprises.
• Child enterprise: the setting for the specific enterprise. A child can enable a feature only if the parent has it enabled.

A feature the parent has disabled shows the Disabled by Parent status and the message “This feature is disabled from Parent Enterprise. Please contact administrator.” Its toggle is unavailable in the edit dialog, and Edge Infrastructure Services saves the feature as inactive. To make the feature available, enable it at the root enterprise first, then enable it on the child enterprise. The root enterprise’s own record is not gated against itself, so its feature cards always reflect its own settings.

​

Edit entitlements

Select the edit action in the entitlement detail page header to open the edit dialog. The dialog lists every feature flag in the catalog, including features that are not provisioned for the enterprise. An unprovisioned feature is labeled “Not provisioned for this enterprise” and its toggle is unavailable, so the dialog can show more features than the detail page does.

​

EVE-OS Images

The EVE-OS Images section lists all EVE-OS base images available across the enterprise. Use it to review image inventory, import new images, set a default image for a given architecture, or delete images that are no longer needed. To open the EVE-OS Images list, open the Admin Dashboard and select EVE-OS Images from the left navigation panel.

​

Search and filter

The toolbar provides a name search and two filters: The list shows the following columns for each image: Name, Image Format, Image Architecture, Image Status, Data Store, and Image Size. An LTS badge in the Name column marks LTS images. A Default badge marks the image that is currently the enterprise default for its architecture. Both badges also appear next to the image name on the image detail page, and an image can carry both. You can customize column visibility and width from the toolbar.

​

Import an EVE-OS image

Users with the app Create permission can import a new EVE-OS image from the EVE-OS Images list.

1. Open the Admin Dashboard and select EVE-OS Images.
2. Select Import EVE-OS image.
3. Complete the import dialog and confirm.

​

View image details

Select any row in the EVE-OS Images list to open the image detail page. The detail page displays two sections. Identity includes: ID, Name, Title, Description, Origin Type, Image Format, Image Architecture, Status, Image Type, Support Type, created date and user, and last-updated date and user. Details includes: Data Store, Projects the image is accessible to (or All projects), Image Relative URL, Image SHA256 checksum, and Image Size.

​

Image status reference

​

Set a default EVE-OS image

Setting an image as the default makes it the fleet-wide base EVE-OS default for its architecture. This affects all nodes of that architecture that do not have an explicit image override. Set as Default appears only for a Ready image that is not already the default for its architecture. The console hides the action on the image that carries the Default badge, because that image is already the default. Setting the default requires the app Update permission.

1. On the EVE-OS Images list or the image detail page, open the … (More actions) menu.
2. Select Set as Default.
3. Review the confirmation and confirm.

The Default badge moves to the image you selected, and the console clears the badge from the previous default. To change the default later, set a different image as the default. There is no separate action to clear the default.

​

Delete an EVE-OS image

1. On the EVE-OS Images list or the image detail page, open the … (More actions) menu.
2. Select Delete.
3. Review the confirmation and confirm.

Deletion requires the app Delete permission.

​

Next Steps