Security Configuration Overview

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

To define each user's rights to Vision, 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 Vision 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, Vision verifies the person's username and password, and identifies the user's role.

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

Windows Integrated Security

Vision supports Windows Integrated Security, which allows users to log in one time for both Windows and the Vision application. Integrated Security logs a user into Vision 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 Vision.

If you use the Vision cloud offering, Deltek First Vision Essentials, or on-premise Vision, you can use single sign-on functionality, if you sign-up and configure Microsoft Azure Active Directory (Azure AD).

For more information how to set this up, see one of the following guides:

  • Deltek First Vision Essentials Administrator Guide — for customers who access Vision via the Deltek cloud.
  • Deltek Vision Technical Installation Guide — for customers who have Vision deployed on-premise.

Related Topics:

  • Checklist: Setting Up Security
    To set up Vision Security, you complete a series of steps in Security Configuration.
  • Logins and Passwords Overview
    If you are new to Vision, you should become familiar login procedures and know how to change your password.
  • Roles Overview
    Security roles define each Vision user's access rights and determine what actions the user can perform. Vision identifies a user's security role when the user logs in. Each user must be assigned to one role.
  • Users Overview
    Users are individuals who use the Vision application. When you implement Vision security, you must create a user record for each individual who will use Vision. Each user has a unique username.
  • Password Policies Overview
    After you create users, use Password Policies Security to establish the criteria for acceptable Vision passwords. These policies apply when users change their own passwords, which they can do after the initial log in.
  • Windows Integrated Security Overview
    Vision includes an option for Windows Integrated Security, which allows users to log in one time for both Windows and the Vision application.
Parent Topic: Configuration Overview