Users

The Users page allows you to manage users who have access to Epicor CPQ. In the Administrative Interface, click Users and Roles > Users to see the list of users. The list of users includes all users who have an email address and password, which includes Company Administrators and Self-Registered users. The special Anonymous User is not included in this list.

Add or delete users using the buttons at the bottom of the users list. As with other lists, click the column headers to sort by that column; enter text into the search bar to filter the list. Click on a user's email address to see their details.

User Properties

Basic Properties
First Name Last Name	Mandatory. The user's name appears in all lists, Snap rules, and other descriptions about the user.
Email	Mandatory. An active email address is required for alerts, to help self-service password resets, and other functionality.
Roles	Specify 0, 1, or more roles to describe this user's abilities in Epicor CPQ.  See the roles section below for more information.
Description	Optional field for your administrative use.
External ID	Optional field for your use, such as an employee number or another unique identifier. Only users with the "Modify Users" permission can edit this field.
License Type	Select what type of license this user has.  More information can be found on the page describing the Dashboard.
Approved	Clear this checkbox to temporarily disable or "freeze" a user's account. Users who are not approved cannot log in. For example, clear this checkbox for a user on maternity leave or a sabbatical, or for a group of users after their testing is completed. Depending on your company settings, self-registered users may need to be approved first.
Allow CRM Single Sign-On	If you are integrated with Salesforce.com, this option will allow transparent authentication for users launching Epicor CPQ from Salesforce.  This box is unrelated to other SSO integrations.
Profile Image	Optional contact information which can be used in Snap rules.
Company Name	Optional contact information which can be used in Snap rules.
Phone Number	Optional contact information which can be used in Snap rules.
Mobile Number	Optional contact information which can be used in Snap rules.

Billing Info / Shipping Info

Optional contact information which can be used in Snap rules.  For example, this data can be used in output documents, to fill in forms with information about the user.

Notifications

Error Logs Pending Approval Quote Approved Quote Rejected

Users can customize how they would prefer to recieve alerts.  If any are specified, user-level preferences override the system-wide notification settings.  For each of these events, a user can be notified with... no alert a notification that is added to the drop-down "globe" list shown in the upper-right corner of the user interface an email that is sent to them both a notification and an alert the system-wide default.

Roles on a user

Users can have one or more roles which determine their access to various system functions. Users will be granted any permissions associated with their assigned roles, and these same roles can be used in Snap rules to control the visibility or access to other features you build.   Some things to remember:

• For all users, roles are additive. 
  Roles give your user permissions, but do not take them away.  For example, if a user has two roles – one which adds a permission, and another which does not – then the user has the permission.
• For channel users, roles cannot extend their permissions beyond their channels. 
  Read the walkthrough on channel management for more information.
• The "Company Administrator" role grants all standard permissions. 
  You do not need to add more roles to a person with the Company Administrator role to grant them more permissions.  However, if you also use Roles in your own code, you may want to add those roles to system administrators so they can see the same custom features as your users.  For example, you may have a page in a configurator which is visible only to users with the role "Sales Manager".  Grant the "Sales Manager" role to your administrators so they can also see the page.
• Workflow stages can temporarily override permissions.
  When a quote has been submitted into a workflow, each stage of the workflow can temporarily override the permissions you've defined globally.  For example, you may not allow your sales managers to edit a quote after it has been submitted.  But if the quote enters a special "needs Management Approval" stage where you want to allow your sales manager to adjust the quote, you can grant the permission to edit the quote at just that one stage.

Administering Users

As an administrator, you can easily manage your users with the buttons at the bottom of the user record:

• Reset Password
  If a user can't remember it.  Clicking this button will invalidate their current password and send them an email with instructions to create a new one.  (Note: you users can do this themselves on the login screen.)
• Delete
  To delete the user.  Any objects they've created or modified remain.  On objects where they have performed work, their name remains on the "created by" or "last modified by" attributes of those objects.
• Delete and Anonymize
  Deletes, and additionally removes their name from any work history in compliance with GDPR guidelines.
• Reset Deactivation Timer
  If your company settings define a number of days between logins for any user to stay active, you can easily reset this timer for a specific user.  Their password remains untouched.