ADMIN USERS ONLY
The main preferences governing routing are whether it is on or off for Proposals (top) and Subawards (bottom).
Routing Proposals
Routing is a flexible system for electronically approving the proposal by routing it to each approver in order. The effort to configure and set up the minimum routing system is modest. See Routing for more information.
Note: Routing affects access permissions, and it is not meant to be switched from On to Off once it has been used. This may result in unusual access control behavior. Experimentation should be performed in a test environment.
Proposal Routing Lock
This option locks all data fields and either the related budget attachments or all attachments to an approver once they have approved the proposal as part of the routing process. It only applies if routing is on.
If you'd like to preserve the ability for users earlier in the routing chain to upload attachments to areas other than the budget, select the first option. If you want a routed proposal to be completely locked to modification, select the second option.
Routing Chain Construction
When a proposal is created and routing is enabled, a routing chain can be automatically or manually built from a starting user. The chain can begin with the PD/PI or with the user creating the proposal, whichever is more appropriate for your institutional needs.
Submission
The preferences for submission determine which user level can submit proposals in different scenarios.
Submitting to Grants.gov Without AOR Approval
If routing is Off for proposals, this preference should be set to All users, because proposal approval by an AOR will not occur within the system.
If you are using routing, this preference determines by whom proposals can be submitted without the approval of an AOR. If you require an AOR's approval before submission unless an Admin is involved, select one of the first two options. If you do not always require this approval, then select All users.
Submitting Proposals to Grants.gov After AOR Approval
This preference controls electronic submission capability after an AOR has approved a proposal for submission. Again, if routing is off, this preference should be set to All users. The approval action by the AOR locks all of the proposal's data except the attachments to editing, so other users may submit, but will not be able to further modify the proposal.
- If Admins wish to retain the exclusive right to the submit proposals, select SysAdmin and Pre-Award Admin.
- If Admins wish to delegate the right to the submit to other users, select All users.
Exporting Subawards Before or After AOR Approval
The use of routing and approval for standalone Subawards parallels the use for regular proposals. If you are not using routing for Subawards, these preferences should be set to All users. The major difference is that Subawards are exported for delivery to another Cayuse 424 customer rather than submitted to Grants.gov.
