Skip to main content

Users

PaletteAI VM Launchpad integrates with Keycloak for user identity. It stores users you create on the Users page in Keycloak and manages their VMO role and Kubernetes access on your behalf. This guide covers viewing, creating, editing, resetting passwords, and deleting users.

Prerequisites​

  • A cluster created using VM Launchpad. Refer to Install VM Launchpad for guidance.

  • An account with the Platform Admin VMO role, or membership in a group mapped to Platform Admin.

Users Page​

From the left main menu, select Settings > Access Management > Users to view all users in the appliance.

The Users table lists the following columns.

ColumnDescription
UsernameThe Keycloak username.
EmailThe email address on the account.
NameThe first and last name on the account.
EnabledA check mark indicates the user can sign in.
GroupsGroups the user belongs to. Each group appears as a pill.
CreatedThe date VM Launchpad created the user.
ActionsRow actions to edit, reset the password, or delete the user.

Select a column header to sort. Use the Filter rows search box to filter by any field.

Create Users​

VM Launchpad creates one or more users in a single guided flow that also assigns their VMO role and namespace scope.

  1. From the left main menu, select Settings > Access Management > Users.

  2. Select Create User. The Onboard users wizard opens on the Who step.

  3. Complete the following fields for the first user.

    FieldDescription
    UsernameRequired. Must be unique.
    EmailRequired. Must be a valid email address. Refer to the note that follows.
    First NameOptional. The user's given name.
    Last NameOptional. The user's family name.
    PasswordRequired unless Temporary is selected. Must meet the password policy.
    Verify PasswordMust match Password.
    TemporarySelect to force a password reset on first sign-in. Bypasses the password field.

    Passwords must meet the following requirements. Violations appear as inline validation, and Next remains unavailable until you resolve them.

    • At least 15 characters

    • At least one digit

    • At least one special character

    info

    The email address is required because the Kubernetes API server in a VM Launchpad cluster identifies users by their email claim. Accounts without a verified address cannot be granted access. This also applies to users federated from an LDAP directory. Refer to Federate LDAP Users with Keycloak.

  4. (Optional) To onboard more users at the same time, select + Add another user and repeat the previous step. Each user has its own row in the wizard.

  5. Select Next to open the Role step. Select a VMO role to assign to every user in this wizard run, or select Skip to onboard users without a role.

    RoleDescription
    Platform AdminFull control of Virtual Machine Orchestrator. All permissions, all namespaces.
    EditorBuild VM workflows and templates. Packages, templates, and dashboards (read and write).
    OperatorDay-to-day VM operations. Templates and dashboards (read and write), monitoring, storage (read).
    ViewerRead-only access. Templates, packages, and dashboards (read).

    If any user in this wizard inherits a VMO role from a group, no role card is preselected on the Role step and an amber banner names the inherited role. Refer to Group-inherited roles on the role cards for details.

  6. Select Next to open the Scope step. Choose the namespace scope for the selected role. A scope is required when a role is assigned.

    OptionDescription
    Cluster-wide accessGrants access to all namespaces through a Kubernetes ClusterRoleBinding.
    Select NamespacesChoose one or more existing namespaces. VM Launchpad creates RoleBindings scoped to those namespaces only.
    Create New Namespace(Optional) Enter a namespace name and select + Create to create a namespace and add it to the current scope.
  7. Select Next to open the Review step. Review the actions the wizard performs for each user.

  8. Select Apply. Each action has its own progress indicator, and VM Launchpad lists any failures after the operation completes.

  9. Select Close to return to the Users page.

VM Launchpad selects the matching Kubernetes ClusterRole automatically based on the VMO role you assign. The mapping is fixed.

VMO RoleKubernetes ClusterRole
Platform Adminspectro-vm-admin
Editorspectro-vm-power-user
Operatorspectro-vm-user
Viewerspectro-vm-viewer

Edit a User​

  1. From the left main menu, select Settings > Access Management > Users.

  2. In the Actions column, select the pencil icon for the user you want to edit. The Edit User modal opens.

  3. The table below lists the fields you can edit.

    FieldDescription
    EmailThe email address on the account.
    First NameThe user's given name.
    Last NameThe user's family name.
    EnabledClear the checkbox to disable the account without deleting it. Disabled users cannot sign in.
    GroupsAdd a group by selecting it from the list. Remove a group by selecting the × on its pill.
    VMO RoleSelect one of the role cards to assign a VMO platform role. The selected card is outlined.
    NamespacesSelect Cluster-wide (all namespaces) or select one or more specific namespaces to scope the Kubernetes bindings.
    info

    The Username field is read-only after a user exists. To use a different username, delete the user and create a new one.

  4. Select Save.

Group-inherited roles on the role cards​

Whenever a user inherits a VMO role from a group, either during creation or after you add a group in the Edit User modal, the role cards behave in two ways about which assignment actually applies:

  • An amber banner appears over the role cards listing the inherited role, for example, Platform Admin is inherited from group cluster-admins.

  • No role card is selected by default. Because group-based roles override any direct assignment, selecting a card as the default would suggest the direct assignment is taking effect when it is not.

Take the banner at its word. A role you set here does not take effect while the user remains in that group. Refer to How Effective Permissions Are Calculated.

How Effective Permissions Are Calculated​

Group membership determines a user's effective permissions whenever any group applies. The role assigned directly to the user is a fallback.

  • If the user belongs to one or more groups that carry a VMO role, their effective permissions are the union of those group roles, and the role assigned directly to the user is ignored.

  • If none of the user's groups carries a VMO role, the role assigned directly to the user applies.

For example, a user assigned Editor directly who belongs only to a group carrying Viewer receives Viewer permissions, not Editor. Removing that group membership makes the direct Editor assignment take effect. A user in two groups carrying Viewer and Editor receives the combined permissions of both.

To reduce a user's effective permissions, change or remove the group mappings that grant them. Editing the user-level role has no effect while any mapped group applies. Refer to Groups to review and edit group membership and role assignments.

warning

Changing a user's roles or groups does not revoke their existing API keys. Revoke the keys as well. Refer to API Keys.

Reset a User's Password​

  1. From the left main menu, select Settings > Access Management > Users.

  2. In the Actions column for the user, select the key icon.

  3. Enter and confirm a new password that meets the password policy.

  4. (Optional) Select Temporary to require the user to set a new password on next sign-in.

  5. Select Reset.

Delete Users​

You can delete a single user or select many users to delete in a single operation.

Delete a Single User​

  1. From the left main menu, select Settings > Access Management > Users.

  2. In the Actions column, select the trash icon for the user, or right-click the row and select Delete User.

  3. Confirm the deletion.

Delete Users in Bulk​

  1. From the left main menu, select Settings > Access Management > Users.

  2. Select the checkbox for each user you want to delete. Use the header checkbox to select every user on the current page.

  3. Select the Delete button in the bulk actions toolbar at the top of the table.

  4. For a single selected user, type the username to confirm. For many users, type delete to confirm.

  5. A progress indicator tracks each deletion. VM Launchpad lists any failures after the operation completes.

warning

Deleting a user removes them from Keycloak, but their existing ClusterRoleBindings and RoleBindings may remain until you explicitly revoke them. Remove the bindings on the Groups page or through the Kubernetes API if you no longer need them.

Palette-Managed Environments​

When VM Launchpad runs in a Palette-managed environment, the UI may hide user creation. In that case, the parent platform manages user lifecycle. VM Launchpad displays users for viewing and for access policy assignment only.

Next Steps​

  • Group users together and manage their VMO role and Kubernetes access in one place. Refer to Groups.