Skip to main content

Pentaho+ documentation is moving!

The new product documentation portal is here. Check it out now at docs.hitachivantara.com

 

Hitachi Vantara Lumada and Pentaho Documentation

Manage users

Parent article

You can assign any or all roles to any user profile. For example, you can configure your users to create and apply tags to files and fields by assigning Steward and Analyst roles respectively for the applicable domains.

You can also create custom roles to set as a default role for users. For example, you can create a custom user role that can search data and metadata and also create HIVE tables from HDFS files. You can then set this role as a default for all new users.

Add a user

Lumada Data Catalog user profiles include the user name that Data Catalog uses to authenticate the user and the role or roles that determine user access to data and metadata. For more information about using roles to manage user access to Data Catalog metadata, see Role-based access control (RBAC).

Perform the following steps to add a user:

Procedure

  1. Navigate to Manage, then click Users.

    Users tile
  2. Click Add a New User.

    Add a new user The Add a New User dialog box displays.Add a New User dialog box
  3. Enter the information for the user.

    User names must start with a letter and must contain only letters, digits, hyphens, or underscores. No white spaces are allowed. Also, make sure the name strings do not match any Data Catalog reserved names.
  4. Click Create.

    The user is created with a Guest role.

    To assign an additional role or a different role, see Assign a role.

Assign a role

In Lumada Data Catalog, you can assign roles and allow users to execute tasks according to their responsibilities. You can assign multiple roles to a user, and the role with the least restrictive access dictates the user's access privileges.

By default, Data Catalog assigns the Guest role to all new users, giving the user read access to all tag domains and virtual folders. You can also set additional roles as default roles. Refer to Set a role as default for more information.

Perform the following the steps to assign a role:

Procedure

  1. Navigate to Manage, then click Users.

  2. Select the user to whom you want to assign a role, and click the Roles tab.

    Assign a role
  3. Click Add a new Role.

  4. In the ROLE field, start typing the name of the role in the field and select the best match from the list that displays.

    The role is assigned.

Next steps

To add more roles to a user, repeat the steps above for each additional role.

Remove a role

You can remove assigned user roles from user accounts. Each user needs to have at least one user role, so Lumada Data Catalog displays an error if you try to remove a user's only role.
NoteTo remove dynamic roles mapped using LDAP group mapping, you must update the group-to-role-map.json file. See Dynamic group to role mapping for more details.
Perform the following steps to delete an assigned user role:

Procedure

  1. Navigate to Manage, then click Users.

  2. Select Roles.

  3. On the row for the role you want to remove, click the More actions icon and select Revoke from user.

    Removing a role The role is removed from the user.

Edit a user

Perform the following steps to edit a user in Lumada Data Catalog:

Procedure

  1. Navigate to Manage, then click Users.

  2. Click the user you want to edit.

    The user's details are displayed.

    User Settings tab

  3. Make the changes you want on the Settings tab.

  4. (Optional) To assign a role, see Assign a role. To remove a role, see Remove a role.

  5. Click Save.

    The user information is updated.

Delete a user

Perform the following steps to delete a user.
NoteYou can delete a user if the user is no loner needs to access Lumada Data Catalog. You cannot delete a default user.

Procedure

  1. Navigate to Manage, then click Users. You can also go to the Settings tab on the page for the user.

    Delete a user

  2. Click the More actions icon and select Delete.

    The user is deleted.