System Admin - Create a Custom Role

Overview

The Kuali Research system comes with a wide variety of pre-configured roles designed to meet the majority of permissions configuration needs. There are circumstances where a school may want to build a custom role to simplify maintaining their permission structure.

Create a Custom Role

Navigate to All Links on the Dashboard and search for Role and select.  Click the create new button in the upper right hand corner of the screen.

Search for the role type you want to use.  The Following three role types will be used for the majority of custom roles in the system.

• Default: This role type will assign permissions to members of the role with no unit modifier.  For most permissions this will give the user access to the actions controlled by that permission in all documents in the system. The Create ProposalDevelopmentDocument and Modify Award permissions require unit modification to perform as expected, and will not work properly with this role type.
• Unit: This role type requires a Unit Modifier for each membership. A user may be added to these types of roles multiple times so they can be associated with multiple units. A user in a Unit role will be assigned the permissions in that role for each unit they have a membership associated with.
• UnitHierarchy: In addition to the features of the Unit role each membership in a UnitHierarchy role can be flagged as Descends Hierarchy. If this flag is turned on for a membership then that user will gain all permissions for the unit assigned to them, and each unit beneath the unit associated with their membership in the Unit Hierarchy.
• Derived Role: Investigators: The name of this role must match the Proposal Person Role ID of a role in the Proposal/Award Person table. Any Proposal Development permissions assigned to this role will be granted to users with the associated Proposal Award Person role ID. An example of this is the PI role configured out of the box.
• Derived Role: Institutional Proposal Investigators: The name of this role must match the Proposal Person Role ID of a role in the Proposal/Award Person table. Any Institutional Proposal permissions assigned to this role will be granted to users with the associated Proposal Award Person role ID.
• Derived Role: Award Investigators: The name of this role must match the Proposal Person Role ID of a role in the Proposal/Award Person table. Any Award permissions assigned to this role will be granted to users with the associated Proposal Award Person role ID.
• Derived Role: Negotiation Investigators: The name of this role must match the Proposal Person Role ID of a role in the Proposal/Award Person table. Any Negotiation permissions assigned to this role will be granted to users with the associated Proposal Award Person role ID on the Proposal or Award document linked to a Negotiation.
• Derived Role: Generic Unit Administrators: Further details on this Derived Role Type are provided in the Cross Module - Setting Up Roles for Unit Administrator Types article.
• Derived Role: Award Unit Contact: The name of this role must match the name of a Unit Administrator Type. Instead of providing permissions based on the unit of a person's entry in the Unit Administrator table this will provide permissions in Award to anyone listed in the Unit Contacts section with this type. These are document level permissions similar to the permissions granted in the Access section of Proposal Development.
• Derived Role: Proposal Supplemental Info: This role will provide Proposal Development permissions based on a supplemental information field linked to principal name. Further details on this Derived Role Type are provide in the Cross Module Functionality: Supplemental Information Roles article.
• Derived Role: Institutional Proposal Supplemental Info: This role will provide Institutional Proposal permissions based on a supplemental information field linked to principal name. Further details on this Derived Role Type are provide in the Cross Module Functionality: Supplemental Information Roles article.
• Derived Role: Negotiation Supplemental Info: This role will provide Negotiation permissions based on a supplemental information field linked to principal name. Further details on this Derived Role Type are provide in the Cross Module Functionality: Supplemental Information Roles article.
• Derived Role: Award Supplemental Info: This role will provide Award permissions based on a supplemental information field linked to principal name. Further details on this Derived Role Type are provide in the Cross Module Functionality: Supplemental Information Roles article.
• Derived Role: Subaward Supplemental Info: This role will provide Subaward permissions based on a supplemental information field linked to principal name. Further details on this Derived Role Type are provide in the Cross Module Functionality: Supplemental Information Roles article.

Example: Barbara Borst is a member of the Role Create Proposal Development All Units, which is a Unit Hierarchy role. Her membership is associated with BL-IIDC and has the descend hierarchy flag turned on.  She can create proposals with a Lead Unit of BL-IIDC, BL-IIRC, or BL-IICC.  BL-IIRC and BL-IICC are both centers that report up to BL-IIDC on Barbara's Unit Hierarchy.

Once you've found the role type you're looking for press the return selected link next to your role type.

Complete the following fields in your role document

• Description: Enter a description that follows the description naming conventions for your institution.
• Namespace: Enter the namespace that is most appropriate to the permissions you are assigning to this role.
• Role Name: The exact value you entered for Description in your Unit Administrator Setup
• Active: Leave this checked
• Description: Indicate what this role is being used for to make things easier on future administrators.
• Permissions: Any permissions you add to this role will automatically be assigned to members of this role based per the behavior described above in the Role Type breakdown.

You can add members in the Assignees section at this point, or add them later via the Person document.

Once you have proofed your document press the submit button.