Online Help Home > Admin > Setting Up Users and Users Roles
Setting Up Users and User Roles |
|||||||
Overview |
To set up your users in eCredit, as the administrator you:
About access and business roles You assign users to an Access role that determines the eCredit features and capabilities that the user has available when they log in. Users can be assigned multiple access roles to accomplish their tasks. Optionally, you can also assign users to a Business
role. When you assign users to the same Business role, this designates
them as work queue peers who are able to perform the capabilities included
in the role with each other. Business roles can include any of the following
capabilities:
How access roles work User Access roles consist of capabilities that determine the access privileges for the users assigned to that role. There are capabilities for each eCredit feature, enabling you to:
For example, to give a user read-only access to bank references, create a role that has the capability to View Bank Reference list and View Bank Reference detail, but not the capabilities to add, delete, or save bank references. Access roles provided with eCredit eCredit provides seven generic user roles: Admin, Source Admin, Sales Rep, Credit Analyst, Collector, Strategist, and Dispute Resolver. Using the Admin role, the subscriber system administrator can change these generic roles, or add new roles to meet the requirements of your workflow. Click here to see a description of what each role includes. Reports as role capabilities Each eCredit report has an associated capability that must be included in a user's role to enable the user to generate that report. You view these report capabilities by selecting Reports from the Applications Modules list on the Role Details screen. You can include the capability to generate any or all of these reports in a role, giving you control over which users can generate each report. The three standard credit reports are included in the Credit Analyst and Collector, but not the Sales Rep role. If a user creates an ad hoc report, that report is automatically created as a capability and automatically added to the user's role. To enable another user to generate that ad hoc report, add that report as a capability to the user's role. If you want only a subset of users assigned to a role to generate a report, create a separate Access role that includes the capability to generate the report, and add that role to only the users you want to generate the report. Role capabilities determine the landing screen when you select customers You can make the Customer Snapshot the first screen that appears when users select a customer by giving the user two capabilities: View Customer Snapshot and Make customer snapshot default landing screen. To give the user access to the Customer Snapshot, but have the Basic screen first appear when users select customers, give the user the View Customer Snapshot capability without the Make customer snapshot default landing screen capability. Having the default landing screen as a role capability gives you the flexibility to assign the landing page to targeted users. Password requirements When an administrator adds a user, or when a user changes their password, the password must meet the following requirements:
When your password expires you must change the password or you are not able to continue using the application. About the source Admin role When you add a source , you must create a user for the source administrator. We recommend that you limit the Source Admin role to the administrative capabilities included in the generic Source Admin role. This ensures that the credit policies for the subscriber organization are consistently applied across sources. If you are the administrator for a source that originates credit requests for the eCredit subscriber, the administrator for the subscriber determines your administrative capabilities and the roles available to you for user assignment. | ||||||
Related topics |