{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/1d9865333afe452dad8a26b9707ed4ad\" frameborder=\"0\" width=\"1356\" height=\"1017\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1017,"width":1356,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1017,"thumbnail_width":1356,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/1d9865333afe452dad8a26b9707ed4ad-1688058958900.gif","duration":200.7333333333333,"title":"User Roles","description":"Let's briefly discuss the different user roles and their responsibilities within the Cayuse system. \nUser roles are different from research team roles which we will talk about when we create a proposal. \nAll active faculty and staff have been granted base user access which allows you to create a proposal record. \nFor individuals who require elevated access, such as approvers, access will be managed on a per-user basis. \nElevated access can be requested by completing the access request form which you can find the Cayuse implementation website. \nWhen requesting access for individuals involved in the approval process, we recommend getting access for at least one alternative approver in the unit for situations when the primary approver is unavailable. \nThis allows for timely reviews, consistent processes, and eliminates bottlenecks that may arise from an approver’s unavailability. \nI do want to note, that while it’s good practice to have this redundancy built into a unit’s approval process, in practice, each approver in the unit will receive simultaneous notifications when a proposal enters the approval process.Cayuse does not offer a true proxy process. So each approver will get a notification that a proposal needs approving. Again, this requires good communication within the unit. \nIt's important for each unit to have clear expectations and workflows for approval processes in various situations. Clear communication within the unit is key. We suggest communicating regularly with researchers within a unit so they know who the approver is and when it may be different.\nOne final note here: This training is only covering proposal creation and submission. We are not covering approver workflows. That will be a separate training for approvers only."}