Eternet Portal Documentation

Dashboard Administration

Dashboard operations

The settings manager loads dashboard records through the Eternet API, supports create/edit/delete workflows, and protects default dashboards from deletion. It uses the shared Access Manager to select users or groups and assign scopes.

Access payload

The portal maps grants to subject type and identifier plus a list of scopes. The server’s accepted schema and persistence are authoritative; successful UI selection is not proof that every backend resource persists or enforces the grants.

Distinction from Dashboards

This settings page is the administration path. The separate Dashboards experience currently contains a manager that explicitly uses a mock API for its list/create/delete flow; do not conflate those two pages.

Creating and editing a dashboard record

The settings page is the administrative workflow for dashboard definitions. An administrator can create a dashboard by supplying a display title and path, open an existing record for editing, and save changes through the configured Eternet dashboard API. Dashboard structure follows the familiar model of a title, path, sections, and cards. Default dashboards are identified by their owning scope and are protected from deletion in the interface. This helps preserve resource dashboards that are generated for devices, hubs, or vehicles while still allowing custom dashboards to be managed.

The editing form includes an Access Manager. It loads user and group choices, lets the administrator select one or more subjects, and records Read, Write, or Control scopes for each grant. The selected grants are presented back in the form before the administrator submits the dashboard. The output describes the intent of the access configuration; the backend contract determines whether it is persisted and enforced. A customer presentation should not promise that a scope blocks an operation until the service has been tested with users who have and do not have that scope.

Access behavior and validation

Access grants are composed of a subject type, stable subject ID, and one or more scopes. A user grant targets an individual account; a group grant allows a team to be managed collectively. When reading existing dashboard records, the portal can normalize several legacy field shapes and falls back to read access for legacy user lists that do not contain explicit scopes. This compatibility behavior helps display older records, but it does not eliminate the need to verify the exact payload expected by the backend. Differences in field naming, accepted scope values, and group support can affect whether changes survive a reload.

For a reliable test, create or edit a non-critical dashboard, add a test user and a test group with clearly differentiated scopes, submit the form, inspect the API response, reload the page, and verify the grants are still present. Then sign in as those subjects and check both allowed and denied actions. Also test a default dashboard to confirm the UI prevents deletion, and test API errors to ensure the user receives a clear failure rather than a false success notice.

Customer value and scope

Dashboard administration provides a path to tailor views for teams and protect them with resource-level sharing rules. It can help separate operator, analyst, and administrator responsibilities while retaining a shared data model. The portal does not substitute for backend authorization, identity lifecycle, or organization policy. In customer discussions, describe the management workflow, the payload semantics, and the verification process. State clearly that final access behavior depends on the dashboard service enforcing grants at the API boundary.