Tag Archives: Personnel

May 2012 SAGE Maintenance Release

New Features

  • The Security and Export compliance questions have been revised, and a new one has been added concerning access to classified national security information. Answering “Yes” to the new question will generate a new Security Reviewer approver node on the approval graph.
  • The SAGE Budget export now contains data formatted to simplify data entry for the SF424 forms. You will find this information following the usual export data.
  • When adding an ad hoc approver or watcher, a new validation checks for any mismatch between the Role chosen and the level of the associated organization code.
  • When OSP marks an eGC1 as eligible for an Advance Budget Review, the eGC1 owners will automatically receive an email message.
  • When users look up personnel, the results will contain the employee identification number. This will allow users to quickly differentiate between personnel with similar names.
  • You may now delete an eGC1 sooner. You must have read/write access, it has been more than six months since the eGC1 has been completed, and the eGC1 is in Withdrawn or Returned status.


  • If you create new budget and complete all of the steps until you reach the access page where you add and remove an admin/budget contact, you will see the full budget navigation instead of the wizard.
  • Hyphenated names now display properly.
  • Advance budget is marked as ineligible when a user copies an older eGC1.

April 2012 SAGE Release

New Features

  • Budget and eGC1 Preparers, formerly known as Creators, may be updated by anyone with Read/Write access. This allows you control who gets notifications for an eGC1.
  • Users can enter or update access information once, and it will display on the centralized access page shared by both an eGC1 and its connected SAGE Budget.
  • Users with global edit access for an eGC1 will also have read/write access to the connected budget.


  • A validation message will be displayed if a user attempts to add a person a second time on the eGC1 PI and Personnel page.
  • All new approval snapshots will be in PDF format; the HTML option has been removed.
  • Personnel from older eGC1s who showed up as duplicate owners will now be displayed once.

This article covers both UW and non-UW Multiple PIs.

UW Multiple PI

You may only use the Multiple PI role when specifically allowed or required by the sponsor instructions. For additional information on research team roles, review the UW Research Personnel page.

When including one or more Multiple PIs:

  • Identify the UW Contact PI as the “Principal Investigator” on the eGC1
  • List all multiple PIs on the Personnel page of the eGC1 and choose “Multiple PI” from the drop down list

SAGE will add the Multiple PI to the Approval Flow and send an “approval required” email notification at the appropriate time. If the person selected does not already have an ASTRA role for SAGE,  a warning message of “no access: ASTRA permissions required” will display in red once you select the Multiple PI role. You will need to give them access, so that they can approve the application.  There are two non-PI researcher ASTRA roles that could be used.

As part of the approval process, the UW Multiple PIs are required to certify the PI Assurance Statement. The image below shows the assurance statement in the approval dialog.

The statement reads:

Principal Investigator/Program Director Assurance: I certify that the statements in this eGC1 and the related sponsor application are true, complete and accurate to the best of my knowledge. I am aware that any false, fictitious, or fraudulent statements or claims may subject me to criminal, civil, or administrative penalties. I agree to accept responsibility for the scientific conduct of the project and to provide the required progress reports if a grant is awarded as a result of this application.

The approval/agreement reads:

I am the PI and I have read and agree with the PI Assurance Statement. I understand that approving this eGC1 electronically is equivalent to my signature.

P I approval with assurance statement

Non-UW Multiple PI

In most cases a non-UW multiple PI will not have a UW NetID. Therefore, the certification will be handled manually following the Non-UW Multiple PI Assurance Statement Instructions described below. Note: the eGC1 PI is responsible for securing and retaining assurance statements for non-UW Multiple PIs in their local files.

If the Non-UW person has an “affiliate” NetID, they can be added to the PI, Personnel, & Organizations page of the application.  SAGE will not include them on the approval graph,  but you could add them to the graph as an ad hoc approver and give them access to SAGE with a non-PI researcher ASTRA role.

Non-UW Multiple PI Assurance Statement Instructions

The following steps describe the paper process.