Permissions version 1 core concepts

Setup

Permission setup is currently restricted to BriteCore staff.

These pages concern the general use of permissions. Specific use cases are documented within their respective areas of domain. For example, the independent claim’s adjuster permission is within the BriteClaims documentation.

Unique URLs

Each BriteCore page has a unique URL.

Agent portal vs. Provider Administrator portals

Restrictions in the Agent Portal begin with agent/.

Restrictions in the Administrative Portal begin with britecore/.

Type ahead

As you begin to type a rule, a list of available URLs and functions appears.

Assume permission is granted

By default, a user is granted access to all of BriteCore. Adding restrictions limits a user’s access.

Restrictions

By URL

Users can be restricted from webpages via URLs. For example, restrict a user from the Claims module via britecore/claims.

Of frontend functions

Users can be restricted from functions, which appear as camelCased verbs. For example, restrict an agent from submitting an application via agent/policies/submitQuote.

Of backend functions

Functions can be restricted server-side.

Of UI elements

Users can be restricted from specific buttons.

Application of restrictions

Restrictions apply to the far right part of the rule expression. A rule of britecore/claims/accounting means the user is only restricted from the Accounting tab of the Claims module; he/she can still access BriteCore and the Claims module.

Locking

When a permission rule is locked, it can’t be deleted by anyone other than BriteCore staff.

Assign permission level

Role permissions

BriteCore is automatically added with the roles of agent, agency, agency group, claims adjuster, employee, and underwriter. After completing the Permission Levels section, you can assign permissions to each role in the Role Permissions section. When you assign permissions to a role, all contacts with that role have the permissions identified in the Role Permissions section. 

Permission level in Contacts module

While you can assign permission levels to a role within Role Permission, permission levels are also managed on a per-contact basis within the Contacts module for all contacts that have login credentials. 

Relationship between role permissions and permission level

When you assign permission levels to a contact that already has an assigned role permission, one of the following occurs: 

  • The contact’s permission level is both the permission level assigned in Role Permissions and the permission level assigned in the Contacts module. This occurs when permission levels are assigned in both areas and the permissions don’t conflict. 
  • The contact’s permission level is the permission level assigned in the Contacts module. This occurs when permission levels are assigned in both areas; however, the permissions conflict. 

If you don’t assign a permission level in the Contacts module, the contact will default to the permissions assigned in Role Permissions. If a users’ permissions are updated, that user must log out of, then back into BriteCore for the new permissions to take effect.Updating A User’s Permissions

Updating a user’s permissions

When you update a user’s permissions, the user must log out of BriteCore and then log back in for the new permissions to take effect.