Role-based security allows you to create a system that limits access or restricts operations within the application according to a user’s defined role. This is managed during the user setup process. RBS was developed to ensure that unauthorized users do not gain access to privileged or otherwise sensitive information within the Institution's instance of Cayuse.
Please note: Role-Based Security is different than Chartstring Security, which limits Sponsored and Non-Sponsored fund access for Platform-enabled customers.
Assigning Roles
Roles should be assigned based on a user's needed permission level and role titles must be selected from the seven roles listed below. The permissions for each role are configurable at the role level.
| Role Title | Permission Level | This Role is Suggested For: |
| Business Administrator | Mid | Accountant or general research/grant administrator |
| Central Manager | Mid | Institutional Central Office Administrator |
| Global Admin | Low | System Administrator who manages system set-up, adds codes, etc (not active user of application) |
| Other Limited User | Low | Post-doc, grad student or project manager |
| Researcher | High | Principal Investigator, Co-Principal Investigator, and/or Investigator |
| Research Staff Member | Low | Post-doc, research assistant, undergrad, or technical staff |
| Salary Access | High |
This role is similar to a claim and must be combined with another role. Users with this role added will be able to view detailed salary information. Without this role, users will only see summary level data for salary and fringe. |
| Unit Admin | Low | Person who manages user data access, etc. for a specific unit or department |
| Unit Supervisor | High | Supervisor for a unit or subunit, overseeing other Business Administrators and Researchers in unit or subunit |