Previous Topic

Book Contents

Book Index

Next Topic

Role Mapping

A Role is a profile that describes a certain category of users and describes the tasks which they carry out within Valuemation. Authorizations are then granted to roles and not to Users.

Typical roles would be:

Role

Privileges

Administrator

Access to all customizers and technical objects.

HelpDesk

Access to tickets and related information.

Storeroom

Access to configurations, carry out incoming goods

Purchasing (normal)

Everyday processing of orders and contracts.

Purchasing (manager)

Monitoring budgets.

Dept. Manager

Approves acquisition requests, reads certain reports.

 

 

The Authorizations themselves are granted in the Authorization Manager, but the Roles are defined in the User Manager.

Role Mapping is the process of assigning individual users or whole groups of users to roles (or assigning roles to individual users). Roles themselves change little over time but the people carrying out certain tasks can be subject to much change. Role Mapping allows the Valuemation administrator to react to that change, without changing the definition of the role itself.

Any number of users or groups may be mapped to a role and a user or group may be mapped to several roles. A user can carry out a task whenever the access to the given information or task is permitted by at least one of the roles to which he/she is mapped (either straightly or through a group membership - see Group Mapping).

Valuemation initially has one predefined role which has administrator privileges. Other roles can be created as and when required. When a role is created it initially has the default authorizations. The specific authorizations are then defined in the Authorization Manager.

For more information about working with Role Mapping see Roles and Role Mapping topics.

See Also

Basic Concept

Person Mapping

Group Mapping

Business View Mapping

Client Mapping

Environment

Import from LDAP