User Roles for Document Development
Document-specific roles and associated permissions exist for each e-doc within KC. These are related to the roles of those users involved in completing the preparation of the document, and submitting the document for review and approval. Only after documents are prepared and approved are they then submitted elsewhere – to an external system (for example, Grants.gov) or to another group of users (for example, an IRB Committee). When performing a custom document search on a specific document type that supports user role bound searches in KC, you will be given the option to select the roles that you want to constrain your search by. These roles are always relative to the currently-logged-in user. Roles to ensure that only specified users can view or change all or parts of an electronic document.
Table 4: Role Descriptions > Proposal Development Document Example
|
Prop. Dev. Role |
Description |
|
Aggregator |
The Aggregator is an assigned role in KC that allows the user to make changes to any part of the proposal. In the paper world, this is the person who puts the parts of the proposal together and submits the proposal to the Office of Sponsored Projects (OSP). Additionally, this person assigns roles for completing the proposal. While the OSP may have the system role of Initiator for a Proposal Development Document, the Aggregator may also edit it electronically. Typically, this Initiator is a member of the staff that is associated with the faculty department or college who assembles the proposal. |
|
Budget Creator |
Creates the Budget Document that is associated with the Proposal document. Typically, this is a member of the institution’s administrative staff (as opposed to faculty) who is a department or business office manager who might confer with Office of Sponsored Projects. However, some Principal Investigators (faculty members) create their own budgets. |
|
Narrative Writer |
Creates the proposal narrative. Typically, faculty or students write proposal narratives and enter them within KC, but they may also have administrative staff enter it on their behalf. |
|
Viewer |
Reads Proposal documents (cannot create new or edit existing). |
|
Approver |
Approves Proposal documents. Typically individuals with this role work at Dean, Dept. Chair, Research Office or Business Manager levels, but some might also be Fiscal Officers, depending on institutional needs. |
Figure 11 Rights (Permissions) By User Role > Proposal Development Document Example
|
|
For more information on document-specific permissions, assigned roles and user types, see the corresponding topic for each individual e-doc. |
Proposal Roles (Research Project)
Yet another type of role associated with use of KC is a role within the Proposal document that a user (with Aggregator rights that allow for Proposal document access maintenance) is able to assign to other users. These role names exist for the purpose of identification of the individual institution employees (or in some cases, third-party contributors) that will be involved in conducting the research, carrying out the work stipulated in contracts, and ensuring the award conditions are met.
There are three such roles. They are:
Figure 12: Proposal Personnel Role Selection
Table 5: Research Project Proposal Role Definition
|
Research Role |
Description |
|
Principal Investigator |
Faculty members who are requesting money from sponsor agencies to use to conduct research. The individual bearing primary responsibility for all essential aspects of the project or protocol, including programmatic work, compliance with government, sponsor and university policies and regulations, fiscal stewardship of sponsored funds, and all administrative requirements of the project. The Principal Investigator/Project Director/Program Director (PI/PD) is the individual designated by the grantee, and approved by the sponsoring agency, who will be responsible for the scientific or technical direction of the project. If more than one, the first one listed will have primary responsibility for the project and the submission of reports. All others listed are considered co-PI/PD, and share in the responsibility of the scientific or technical direction of the project. The term "Principal Investigator" generally is used in research projects, while the term "Project Director/Program Director" generally is used in education, and service projects.
|
|
Co-Investigator |
May be another faculty member from the same institution, a student (usually a graduate student), a faculty member from another institution, or an employee of an organization other than the PI’s institution. Investigators who share responsibility for the scientific or technical direction of the sponsored project. |
|
Key Person |
An individual (faculty, student or non-employee) who will play a prominent role in the research activities associated with a proposal. The role in which each Key Person will be assigned for the proposed sponsored project. A named contributor (other than the PI) who is integral to the proposed sponsored project, or who makes a significant contribution to the scientific development or execution of the project, including Consultants (if applicable) and mentors on Career awards. This includes Key Personnel and Other Significant Contributors as defined by NIH and Grants.gov. All individuals who contribute in a substantive, measurable way to the scientific development or execution of the project or protocol, whether or not salaries are requested (NIH definition). |
The federal government is making
the switch to the term “PD/PI” for all projects.
Related Information
|
|