Assigning employees, devices, and workdesks to business roles
In order for employees, devices, and workdesks to inherit company resources, you must assign the objects to roles.
To add employees, devices, and workdesks to a business role
- Select the Business roles | <Role class> category.
- Select the business role in the result list.
- Select the appropriate task:
- Assign employees
- Assign devices
- Assign workdesk
- In the Add assignments pane, assign objects.
- OR -
In the Remove assignments pane, remove objects.
- Save the changes.
TIP: Use dynamic roles to assign employees, devices, and workdesks to business roles automatically.
Related topics
Assigning business roles to company resources
The default method of assigning employees, devices, and workdesks is indirect assignment. This allocates an employee, a device or a workdesk to business roles. The total of assigned company resources for an employee, a device or workdesk is calculated from their position within the hierarchy, the direction of inheritance and the company resources assigned to these roles.
Indirect assignment is divided into:
- Secondary assignment
You make a secondary assignment by classifying an employee, a device, or a workdesk within a role hierarchy. Secondary assignment is the default method for assigning and inheriting company resources through roles.
IMPORTANT: You use role classes to specify whether a secondary assignment of company resources is possible.
If an employee, device or a workdesk fulfills the requirements of a dynamic role, the object is added dynamically to the corresponding company structure and can obtain company resources through it.
- Primary Assignment
You make a primary assignment by referencing a business role through a foreign key to the employee, device, and workdesk objects. Primary assignment inheritance can be enable through configuration parameters.
You must assign company resources to business roles so that employees, devices, and workdesks can inherit company resources. The following table shows the possible company resources assignments.
NOTE: Company resources are defined in the One Identity Manager modules and are not available until the modules are installed.
Table 14: Possible assignments of company resources to roles
Resources |
always |
Account definitions |
Target System Base Module |
Groups of custom target systems |
Target System Base Module |
Active Directory groups |
Active Directory Module |
SharePoint groups |
SharePoint Module |
SharePoint roles |
SharePoint Module |
LDAP groups |
LDAP Module |
Notes groups |
IBM Notes Module |
SAP groups |
SAP R/3 User Management Module |
SAP profiles |
SAP R/3 User Management Module |
SAP roles |
SAP R/3 User Management Module |
SAP parameters |
SAP R/3 User Management Module |
Structural profiles |
SAP R/3 Structural Profiles Add-on Module |
BI analysis authorizations |
SAP R/3 Analysis Authorizations Add-on Module |
E-Business Suite permissions |
Oracle E-Business Suite Module |
System roles |
System Roles Module |
Subscribable reports |
Report Subscription Module |
Software |
Software Management Module |
Azure Active Directory groups |
Azure Active Directory Module |
Azure Active Directory administrator roles |
Azure Active Directory Module |
Azure Active Directory subscriptions |
Azure Active Directory Module |
Disabled Azure Active Directory service plans |
Azure Active Directory Module |
Unix groups |
Unix Based Target Systems Module |
Cloud groups |
Cloud Systems Management Module |
PAM user groups |
Privileged Account Governance Module |
G Suite groups |
G Suite Module |
G Suite products and SKUs |
G Suite Module |
To add company resources to a hierarchical role
- Select the Business roles | <Role class> category.
- Select the role in the result list.
- Select the task to assign the corresponding company resource.
- In the Add assignments pane, assign company resources.
- OR -
In the Remove In the Add assignments pane, assign pane, remove the company resources.
- Save the changes.
Detailed information about this topic
Related topics
Analyzing role memberships and employee assignments
The Overview of all assignments report is displayed for some objects, such as authorizations, compliance rules, or roles. The report finds all the roles, for example, departments, cost centers, locations, business roles, and IT Shop structures in which there are employees who own the selected base object. In this case, direct as well as indirect base object assignments are included.
Examples
- If the report is created for a resource, all roles are determined in which there are employees with this resource.
- If the report is created for a group or another system entitlement, all roles are determined in which there are employees with this group or system entitlement.
- If the report is created for a compliance rule, all roles are determined in which there are employees who violate this compliance rule.
- If the report is created for a department, all roles are determined in which employees of the selected department are also members.
- If the report is created for a business role, all roles are determined in which employees of the selected business role are also members.
To display detailed information about assignments
Figure 13: Toolbar of the Overview of all assignments report.
Table 15: Meaning of icons in the report toolbar
|
Show the legend with the meaning of the report control elements |
|
Saves the current report view as a graphic. |
|
Selects the role class used to generate the report. |
|
Displays all roles or only the affected roles. |
Setting up IT operating data
To create user accounts with the Full managed manage level, the required IT operating data must be determined. The operating data required to automatically supply an employee with IT resources is shown in the business roles, departments, locations, or cost centers. An employee is assigned a primary business role, primary location, primary department, or primary cost center. The necessary IT operating data is ascertained from these assignments and used in creating the user accounts. Default values are used if valid IT operating data cannot be found over the primary roles.
You can also specify IT operating data directly for a specific account definition.
Example
Normally, each employee in department A obtains a default user account in the domain A. In addition, certain employees in department A obtain administrative user accounts in the domain A.
Create an account definition A for the default user account of the domain A and an account definition B for the administrative user account of domain A. Specify the "Department" property in the IT operating data formatting rule for the account definitions A and B in order to determine the valid IT operating data.
Specify the effective IT operating data of department A for the domain A. This IT operating data is used for standard user accounts. In addition, for department A, specify the effective IT operating data of account definition B. This IT operating data is used for administrative user accounts.
To define IT operating data
-
In the Manager, select the Business roles | <role class> category.
-
Select the role in the result list.
-
Select the Edit IT operating data task.
-
Click Add and enter the following data.
Table 16: IT operating data
Effects on |
IT operating data application scope. The IT operating data can be used for a target system or a defined account definition.
To specify an application scope
-
Click next to the field.
-
Under Table, select the table that maps the target system for select the TSBAccountDef table or an account definition.
-
Select the specific target system or account definition under Effects on.
-
Click OK. |
Column |
User account property for which the value is set.
In the menu, you can select the columns that use the TSB_ITDataFromOrg script in their template. For detailed information, see the One Identity Manager Target System Base Module Administration Guide. |
Value |
Concrete value which is assigned to the user account property. |
- Save the changes.
The IT operating data necessary in the One Identity Manager default configuration for automatically creating or changing employee user accounts and mailboxes in the target system is itemized in the following table.
NOTE: IT operating data is dependent on the target system and is contained in One Identity Manager modules. The data is not available until the modules are installed.
Table 17: Target system dependent IT operating data
Active Directory |
Container |
Home server |
Profile server |
Terminal home server |
Terminal profile server |
Groups can be inherited |
Identity |
Privileged user account |
Microsoft Exchange |
Mailbox database |
LDAP |
Container |
Groups can be inherited |
Identity |
Privileged user account |
IBM Notes |
Server |
Certificate |
Template for mail file |
Identity |
SharePoint |
Authentication mode |
Groups can be inherited |
Identity |
Privileged user account |
SharePoint Online |
Groups can be inherited |
Privileged user account |
Authentication mode |
Custom target systems |
Container (per target system) |
Groups can be inherited |
Identity |
Privileged user account |
Azure Active Directory |
Groups can be inherited |
Identity |
Privileged user account |
Change password at next login |
Cloud target system |
Container (per target system) |
Groups can be inherited |
Identity |
Privileged user account |
Unix-based target system |
Login shell |
Groups can be inherited |
Identity |
Privileged user account |
Oracle E-Business Suite |
Identity |
Groups can be inherited |
Privileged user account |
Exchange Online |
Groups can be inherited |
Privileged Account Management
|
Authentication provider |
Identity |
Groups can be inherited |
Privileged user account |
G Suite |
Organization |
Identity |
Groups can be inherited |
Privileged user account |
Change password at next login |