Eternet Portal Documentation
Access Management
Workspace areas
The Access workspace has tabs for users, groups, entities, audit, tokens, and login-related information. User/group and entity operations should be understood in the context of the connected identity and Core APIs.
Access grants
The shared Access Manager lets a dashboard administrator select individual users or groups and assign Read, Write, or Control scopes. These grants are included in the dashboard settings workflow. Backend persistence and enforcement depend on the API contract for the resource being managed.
Interpretation caveat
Some token, audit, or login-history presentation data can be fallback/sample data in the frontend. Before presenting a row as a real security event or persisted credential, verify its API origin and environment.
Identity administration workflow
Access management is the control plane for understanding who can enter the workspace and how selected resources are shared. The Users and Groups areas organize identity records, while Entities provides a way to inspect resources such as devices, vehicles, and hubs. Audit, token, and login-related tabs expose security-oriented information when supported by the connected services. Administrators should use stable identity IDs rather than display names when granting access, because a person’s name or email can change while their identity record remains the same. Group grants are useful when teams need consistent access, but membership changes can broaden or reduce access to every resource shared with that group.
The shared Access Manager is designed for resource-level sharing: it lets an administrator choose individual users or groups and select Read, Write, or Control scopes. Read permits viewing in the intended resource contract; Write represents allowed modifications; Control is intended for operational control actions. The backend remains authoritative for the meaning and enforcement of each scope. The portal’s selection UI should not be described as a universal permission enforcement engine unless the resource API checks those grants for every read and mutation.
Security review and limitations
Administrators should periodically review who has access, why a grant exists, whether the selected scope is least-privilege, and whether group membership is still appropriate. Tokens require particular care: a displayed token record is not the same as a secure secret reveal, and credentials should not be copied into notes or customer-facing documentation. Audit and login events are meaningful only when they originate from the live service. Some views can use fallback or sample rows in frontend code; verify the response path before presenting an entry as a real user, security event, or active credential.
For a reliable access demonstration, select a test user and group, assign a scope to a non-sensitive test resource, save, reload the resource, and verify the grant in the API response. Then test authorization as the selected user: confirm that allowed actions work and prohibited actions fail. This tests persistence and enforcement separately from chip selection. If the backend does not yet persist group grants or scopes for a particular resource, communicate that gap explicitly and avoid implying that the UI alone protects the resource.
Customer value
Centralized access tools help administrators organize users, reduce repetitive individual sharing, and apply clear permission levels to operational resources. They can support onboarding and access review across a growing IoT environment. The value depends on synchronization with the identity provider and consistent API enforcement. Customers should be told which directory is authoritative, how quickly changes take effect, and where administrators can review access history. The portal provides the management interface; authentication and final authorization are enforced by Keycloak and the relevant Eternet backend services.