Skip to Content Information Center
Lexmark Cloud Services

Lexmark Cloud Services

Not your product?

Managing users

  1. From the Account Management web portal, click Users.

  2. Do any of the following:

      Create a user

    1. Click Create.

    2. Type the email address, first name, last name, and display name of the user.

    3. Type the department and cost center name where the user belongs.

    4. Set the password manually, or email a link to the user to change the password.

    5. Click Create User.

      Edit a user

    1. Click a user email address.

    2. Do any of the following:

      • Edit the personal information.
      • Change the user password.
      • Assign user roles.
      • Register a badge.
      • From the Printer Login section, click Edit beside Badge Login.
      • Add the user to a group.
      • Set the user PIN.

          • Note:  This setting is available only when the printer login is set to PIN Login or Badge + PIN as second factor. The PIN generation must be set to Administrator manually set.

        1. From the Printer Login section, click Set PIN or Reset PIN.

        2. Enter the PIN, and then click Generate PIN.

      Delete users

    1. Select one or more users, and then click Delete.

      Notes:

      • You can also search for users using the search bar.
      • The activities of a deleted user are still shown in the Analytics web portal, but the name and email address are removed from all the reports.

    2. Click Delete Users.

      Import users

      The Import feature lets you create, update, and delete multiple users in an organization using a CSV or TXT file. You can also create user groups, and then assign a user to those groups.

    1. Click Import Users or Import, and then browse to the CSV or TXT file.

    2. If necessary, email a link to the user to change the password.

    3. Click Import Users.

    Note:  The import log is sent to your email address.

Sample CSV format

EMAIL,OPERATION,PASSWORD,FIRST_NAME,LAST_NAME,DISPLAY_NAME,SHORTNAME,GROUPS,
CUSTOM_ATTRIBUTES,COST_CENTER,DEPARTMENT
jdoe@company.com,CREATE,,John,Doe,Johnny,jdoe,Group 1,"{'key1':'value1','key2':'value2'}"
llane@company.com,UPDATE,password2,Lois,Lane,Lois,llane,,
ckent@company.com,DELETE,,,,,,,

The import file header line must be the following and is case‑sensitive: EMAIL,OPERATION,PASSWORD,FIRST_NAME,LAST_NAME,DISPLAY_NAME,SHORTNAME,GROUPS, CUSTOM_ATTRIBUTES,COST_CENTER,DEPARTMENT.

Line values and their conditions

  • EMAIL—Required for all users. EMAIL values that are in uppercase in the file are converted to lowercase before the operation is performed. For example, JDOE@company.com is converted to jdoe@company.com.
  • OPERATION—Required for all users.

    • Valid OPERATION values

    • CREATE—Creates a user identified by the EMAIL value with the corresponding properties on the line.
    • UPDATE—Updates the existing user identified by the EMAIL value with the corresponding properties on the line. You can use the [delete] action string to remove the first name, last name, display name, and shortname.
    • DELETE—Deletes the existing user identified by the EMAIL value.
  • PASSWORD—Not required for any OPERATION, and can be empty only when “E-mail a link to change the password” option is selected when importing.

    • Note:  Enable the “E-mail a link to change the password” option only when importing files with the CREATE operation.

  • FIRST_NAME—Not required for any OPERATION, and can be empty. The first name of the user. For example, John.
  • LAST_NAME—Not required for any OPERATION, and can be empty. The last name of the user. For example, Doe.
  • DISPLAY_NAME—Not required for any OPERATION, and can be empty. The name of the user that is sometimes used in display prompts or log reports. The DISPLAY_NAME value can be the full name with middle initial or any string. For example, John A. Doe. The DISPLAY_NAME value is not directly associated with the FIRST_NAME and LAST_NAME values.
  • SHORTNAME—Not required for any OPERATION, and can be empty. The SHORTNAME value is used when the organization has a shortname string that also identifies the user in the organization. For example, jdoe.
  • GROUPS—Not required for any OPERATION, and can be empty. Separate multiple groups by using commas and enclosing them in double quotation marks. For example, "Group1,Group2,Group3". GROUPS values that do not exist in the organization are created, and then added to the organization automatically.

    • Note:  A group name must not contain the following characters: ! @ # $ % ^ & * ; + ? / \ [ ]. If these characters are used, then they are replaced with an underscore (_).

  • CUSTOM_ATTRIBUTES—Not required for any OPERATION, and can be empty. The CUSTOM_ATTRIBUTES value is a specially formatted JSON string for user metadata that is stored with the user. The value must be enclosed in double quotation marks. For example, "{'key1':'value1','key2':'value2'}"
  • COST_CENTER—Not required for any OPERATION, and can be empty. The COST_CENTER value is used for quota assignments and cost‑center‑level reporting in the Analytics web portal.
  • DEPARTMENT—Not required for any OPERATION, and can be empty. The DEPARTMENT value is used for quota assignments and department‑level reporting in the Analytics web portal.

Notes:

  • All lines must have the same number of values as the header, including the commas. Follow empty values with commas. For example, jdoe@company.com,DELETE,,,,,,,
  • The file size must not exceed 1MB.
  • Importing a file with CREATE and UPDATE operations with more than one group assignment can take a few minutes.
  • If any line value contains a comma, such as the names, password, groups, or custom attributes, then the value must be enclosed in double quotation marks. For example, llane@company.com,UPDATE,"pass,word2",Lois,Lane,"Lois,Lane",llane,"Group1,Group2",
Was this article helpful?


Related content

Top