Smart IT roles and permissions
Smart IT has its own broadly defined concept of roles, which are described in the following table. These roles are referred to later in this topic when describing permissions and should not be confused with the BMC Remedy ITSM functional roles described elsewhere in the BMC Remedy ITSM documentation.
Related topics
Permission groups and application access (BMC Remedy ITSM documentation)
How roles map to permission groups (BMC Remedy ITSM documentation)
Configuring company access for people(BMC Remedy ITSM documentation)
Knowledge-Centered-Service-user-roles-and-permissions
User permissions (BMC Knowledge Management)
Struct Admin group permissions (BMC Remedy AR System documentation)
Smart IT roles
Smart IT role name | Related jobs | Example activities |
---|---|---|
IT Admin | An administrator who configures Smart IT or performs other application related administrative functions. | IT Admins manage the following aspects of Smart IT from the Configuration menu:
|
IT Agent | Any Smart IT user who performs one or more of the following jobs in your organization:
| IT Agents perform the following kinds of activities in Smart IT, with the required permissions:
|
Change Agent | Any Smart IT user who performs one or more of the following jobs in your organization:
| Change Agents perform the following kinds of activities in Smart IT, with the required permissions:
|
Problem Agent | Any Smart IT user who performs one or more of the following jobs in your organization:
| Problem Agents perform the following kinds of activities in Smart IT, with the required permissions:
|
Knowledge Author | Any Smart IT user who performs the following activities in your organization:
Note: IT Agents and Problem Agents often also have Knowledge Author permissions. | Knowledge Authors perform the following kinds of activities in Smart IT, with the required permissions:
|
Asset Manager | Any Smart IT user who performs the following activities in your organization:
| Asset Managers perform the following kinds of activities in Smart IT, with the required permissions:
|
Smart IT basic access requirements
The following sections describe the basic permissions required to access the Smart IT interface.
Type of access | Description |
---|---|
Smart IT user | A Smart IT user is anyone who accesses Smart IT with one of the following roles: IT Agent, Change Agent, Problem Agent, Knowledge Author, or Asset Manager. A user must have the necessary permissions to perform the duties described in the Smart IT rolestable. Make sure you review the necessary permissions for each Smart IT role to ensure you assign all of the required permissions for a particular Smart IT role. Additionally, users accessing Smart IT should have access to records belonging to one or more companies. Company access is defined in each user's People record, under Access Restrictions in the Login/Access Details tab. Smart IT uses access restrictions to determine what company information is displayed on the Dashboard and in the Consoles. Basic access requirements for a Smart IT user might look like the following examples:
For more information about access restrictions, see "Configuring company access for people" in Related topics. |
Smart IT administrator access | A Smart IT administrator (IT Admin) is anyone who performs Smart IT configuration or administration activities. IT Admins have access to the Knowledge Template Styles and Screen Configuration options in the Configuration menu. For minimum access permissions, see IT Admin permissions. |
Smart IT user and administrator access | Anyone who needs to access Smart IT as a user and who also needs to work as an administrator must have access restrictions defined, Smart IT user permissions, and IT Admin permissions. Basic Smart IT access requirements for someone working as both a Smart IT user and as an administrator might look like the following examples:
|
Multiple Smart IT roles | People who fulfill multiple roles within an organization need multiple permissions. For example, Ian Plyment is a second level service desk agent who needs to look at incident tickets and to create change requests when required. This means that Ian needs both IT Agent and the Change Agent permissions. Ian also needs to publish knowledge articles and so he also has Knowledge Author permissions. Ian's access and permissions look like the following example:
|
Permissions for Smart IT roles
This section outlines the permissions needed to access Smart IT, organized according to the Smart IT rolesdescribed earlier in this topic. In some cases, there are several permissions from which you can choose. Select the permission that best matches the person's function in the organization. For example, if a manager needs one of the Change Agent permissions, you might give that person Infrastructure Change Master permissions, rather than Infrastructure Change User permissions.
Rules for granting permissions
The following rules apply to all Smart IT roles:
- When there are multiple permission categories for a particular Smart IT role, the user must have one permission from each category. For example, Change Agents must have at least one permission from both the BMC Change Management and BMC Asset Management categories.
- A user ID can have more than one permission from each category.
- The specific permissions that you assign depends on the specific role the person fulfills in your organization.
- If the user fulfills more than one role where Asset permissions are required, you need to assign Asset permissions only once.
- Users with Asset permissions can update their own profiles.
Depending on the Foundation – Contact permissions, the user is able to create new customers in Smart Recorder and update profiles for other people. For more information, see Foundation module permission groups.
IT Admin permissions
An IT Admin must have AR System Administrator permissions to perform screen configuration (for example, adding custom fields to Smart IT views) and to create knowledge template styles.
In addition, if an IT Admin provides administration for support groups in BMC Remedy ITSM, that person needs Contact Organization Admin permissions. For more information, seeFoundation module permission groupsin the BMC Remedy ITSM documentation.
IT Agent permissions
The following table lists the required permissions for IT Agents:
Category | Permission | Additional information |
---|---|---|
BMC Service Desk: Incident Management | At least one of the following permissions is required:
| None |
BMC Asset Management | At least one of the following permissions is required:
| With the optional Receiving User permission, IT Agents can also scan assets, compare them with a purchase order, and mark them as received. |
Task Management System | At least one of the following permissions is required:
| None |
(Only if installed) | At least two of the following permissions are required (one from each type):
Examples
| When BMC Service Request Management is installed on your system, the IT Agent login ID must have at least two BMC Service Request Management permissions. You must grant these permissions when BMC Service Request Management is installed, even if the person to whom you are granting the permissions does not use the BMC Service Request Management application. |
For example, depending on the IT Agent's exact role in the organization, you might need to assign the following permissions:
- Incident User
- Asset Viewer
- Task Manager
- Work Order Master (only if BMC Remedy Service Request Management is also installed)
- SRM Administrator (only if BMC Remedy Service Request Management is also installed)
Change Agent permissions
The following table lists the required permissions for Change Agents:
Category | Permission | Additional information |
---|---|---|
BMC Change Management | At least one of the following permissions is required:
| A user with Change Master permission can create a change request. |
BMC Asset Management | At least one of the following permissions is required:
| With the optional Receiving User permission, Change Agents can also scan assets, compare them with a purchase order, and mark them as received. |
Problem Agent permissions
The following table lists the required permissions for Problem Agents:
Category | Permission | Additional information |
---|---|---|
BMC Problem Management | At least one of the following permissions is required:
| None |
BMC Asset Management | At least one of the following permissions is required:
| With the optional Receiving User permission, Problem Agents can also scan assets, compare them with a purchase order, and mark them as received. |
Knowledge Author permissions
The following table lists the required permissions for Knowledge Authors:
Category | Permission | Additional information |
---|---|---|
BMC Knowledge Management | At least one of the following permissions is required:
| None |
BMC Asset Management | At least one of the following permissions is required:
| None |
Knowledge Viewer permission
From Smart IT 19.02, users with Knowledge Viewer permission can search, view, share, follow, and unfollow Knowledge Articles in the Knowledge Console. This gives users the opportunity to discover and learn more. Users with the Knowledge Viewer permission will not be able to create, edit, and delete a Knowledge Article. This permission is given in the CTM:People form of Remedy IT Service Management. For detailed instructions on how to add permission, seeAdding people information.
Asset Manager permissions
The following table lists the required permissions for Asset Managers:
Category | Permission | Additional information |
---|---|---|
BMC Asset Management | At least one of the following permissions is required:
(Optional) To receive assets, you must have Asset Viewer, Asset User, or Asset Admin permissions, and the following permission:
| None |
Knowledge-Centered Service (KCS) user roles and permissions
This section outlines the user roles and permissions needed to access KCS features supported in Smart IT. To use KCS-defined features, you must use Smart IT 1.3.01 and later version that is compatible with BMC Remedy IT Service Management 9.1 and later. The following KCS-defined user roles are supported:
User role | Description |
---|---|
KCS Candidate | KCS Candidates search for relevant knowledge articles when resolving support tickets. They can use existing knowledge articles, propose amendments to them, or create new articles where no relevant article already exists. |
KCS Contributor | KCS Contributors review, enhance, and complete articles created by other users to suit a wider audience, flag articles that need improvement, and unflag articles after improvement. KCS Contributors also create and validate articles, without review by a KCS Coach. |
KCS Publisher | KCS Publishers publish content to an external audience such as users of BMC Digital Workplace, and they modify published articles. |
KCS Coach | KCS Coaches monitor, maintain, and improve the knowledge health of an organization by generating various reports and guiding users to adopt good knowledge management processes. A KCS Coach thereby helps to improve the KCS maturity level of an organization. |
Permissions introduced with KCS in BMC Knowledge Management are explained in the User permissions topic.The permissions assigned to each KCS role are listed in the Knowledge-Centered-Service-user-roles-and-permissions topic.