User accounts, groups, and permissions for BMC Digital Workplace Catalog
User accounts
You create user accounts manually or by running a script to copy the user database from Remedy ITSM. After you create the user account, you can entitle the user to view and request catalog items, or promote the user to an administrative role.
User groups
The user groups are automatically created when you run the script to copy the user database from Remedy ITSM. BMC Digital Workplace Catalog groups are unique and do not share any relationship with permission groups that other applications use. The group names include the company, organization, and department attributes of the user records.
You can grant permissions to multiple users that belong to a custom user group to view and request service catalog items.
People groups
Create and manage people groups that end users can add as collaborators. Do not create people groups if you want your end users to add only individual users as collaborators to their requests. Your end users will still be able to create one default group for their personal use.
Permission levels and groups
When you create a user account, you can specify the capabilities of the account by assigning a permission group. The following table lists the permission levels that you can assign to users accounts:
For more details about the BMC Digital Workplace Catalog permission groups, see Assigning BMC Digital Workplace Catalog roles to user accounts.
User account fields
When you create user accounts, you must provide the information in the following table. If you are creating user accounts by using Remedy Mid Tier, specify the field name. If you are passing a JSON text file into a shell script, specify the key name.
Field name | Key name | Examples | Description |
|---|---|---|---|
Full Name | fullName | Hannah Hannah Administrator | Specify the full name of the user. |
Login Name | loginName | When viewed in Remedy Mid Tier, the login name is shown without the tenant domain. Example: hannah_admin When user accounts with the shell scripts method are created, the login name field shows the tenant domain as an environment variable. Example: hannah_admin@${rx_tenant_domain} | Specify the name that the user specifies to log in to Remedy ITSM applications. The Login Name field is case sensitive. For example, following are login names a user would enter when the user's login name is Bob, and the company is calbroservices.com:
|
Email Address | emailAddress | hannah_admin@calbroservices.com | Specify the email address used by the account. This address does not need to match the user's login name. |
License Type | licenseType | Fixed Read | Specify the license type for this user. A Fixed license type is an extended license for administrators and service agents who can manage services in BMC Digital Workplace Catalog. A Read license type goes for end users who can only request services from the catalog in BMC Digital Workplace. In Remedy Mid Tier, the Read license type is shown as Restricted Read. |
Group List | groups | Administrator sbe-catalog-admins ["Administrator", "sbe-catalog-admins"] ["sbe-myit-users"] | Specify the permission group memberships to assign to a BMC Digital Workplace Catalog user account. When you assign permissions by using Remedy Mid Tier, add the permission group name as additional entries in the Group List field. When you assign permissions by using a script, enclose the permission group names in an array. For details about permission levels, see Permission levels section on this page. |
Password | password | Passw0rd! | Specify a password with a minimum of 8 characters and a maximum of 30 characters. The password must include all of the following characters:
To enable a user to view and request services through self-service, the user's credentials must match the Remedy ITSM user account. When adding users from Remedy ITSM by running the automated user transfer script, you must enable the cross-reference blank password setting in the Remedy Mid Tier configuration. Then, for these users to be able to log in, you must enable Remedy Single Sign-On. For more information, see the following topics:
At this time, only BMC Digital Workplace Catalog administrators who can access the user form in Remedy Mid Tier can change user passwords. |
Status | (Not used) | Current | When you create users by using Remedy Mid Tier, set this field to one of the following values:
|
(Not used) | forcePasswordChangeOnLogin | false | When you create users by using scripts, leave the value set to false. |
Example permissions and fields for a system notification user
BMC Digital Workplace requires a service level user that runs background tasks such as sending push notifications to end users when BMC Digital Workplace Catalog requests are being processed. You must create the user account that will perform these actions, and provide the credentials for this user when you enable the enhanced catalog. These notifications are sent to the BMC Digital Workplace application. To send notifications by email, you must also complete the configuration described in Configuring-email-notifications.
The following table shows an example of the fields used to create the system notification user. You should specify unique login credentials when creating the system notification user in your environment:
Example permissions and fields for an enhanced catalog administrator
The administrator who maintains the sections in the enhanced catalog must also be a service catalog administrator in BMC Digital Workplace Catalog. When you follow the installation process steps to create a tenant, the process creates the first service catalog administrator user account for you.
The following table shows an example of the fields used to create the first service catalog administrator user account. You should disable this account and specify unique login credentials when creating additional users in your environment.
Example permissions and fields for a service agent
A service agent who reviews user requests must be a service agent in BMC Digital Workplace Catalog.
The following table shows an example of the fields used to create a service agent.