Security Settings

DPS's Security features make it possible for your system administrator to grant or restrict user access to applications, forms, and records in DPS.

To define each user's rights to DPS, the system administrator first creates user roles that reflect your organization's business rules. For example, a "marketing" role restricts a user's access to the DPS features that relate to marketing. The system administrator then assigns each user to a role.

This "role-based" security approach provides flexibility and ensures that users have access to the specific processes and data that they need. When a user logs on, DPS verifies the person's username and password, and identifies the user's role.

When you save users, passwords, and roles, DPS automatically performs a licensed user check. The number of users that you set up must not exceed the number of licenses that your enterprise holds. For example, if you attempt to set up five CRM users, you must have a minimum of five CRM licenses. When DPS calculates the number of employees set up in DPS, DPS does not count employee records that are marked as "Consultant" or "Terminated" in the Employees hub.

Windows Integrated Security

Information will be provided in a future release.

DPS supports Windows Integrated Security, which allows users to log in one time for both Windows and the DPS application. Integrated Security logs a user into DPS based on the user’s Windows domain network login. If a user is not logged into the company network, the user will be prompted for a network ID and password before he or she can log in to DPS.