Role Setup

The setup of security access for different user roles is managed on the Roles screen within Aspire, which is available under Administration in Manage User Roles. You must be assigned a System Admin role with a System Admin permission to manage the specific permissions available to each role.  

In Aspire, there is a difference between a Role and Permission. A System Admin permission provides you with specific functions only if you have the permission enabled under your User role. It is common to establish a System Admin role, which is given a System Admin permission and other permissions necessary to perform your function. The same applies to the relationship between the Branch Admin role and Branch Admin permission. Descriptions of Aspire permissions are provided in Aspire Permissions. 

In addition to specifying permissions for a role, you can specify a Role Hierarchy Value using a number ranging between 1 and 999 as a system administrator. The role hierarchy value specifies an authority level within the organization relative to other system users. 

The role hierarchy value helps to determine authority for: 

• Approving completed work tickets – A logged-in user can approve a work ticket pending approval if they have greater authority (smaller Role Hierarchy Value) than the person who put the work ticket into Pending Approval status. (They can also approve work tickets with the Approve Work Ticket permission.) 
• Approving proposals – A person can approve proposals for release to customers if they have authority greater than or equal to (smaller Role Hierarchy Value) the person (or role) defined in a workflow to approve proposals. See the Workflow Search List screen for additional information.