Bob-

I apologize for my misuse of terms, or just abusing English, but I was
only trying to speak the vulgate of the "Commons Man."  In fact, the
command for delegating eSNAP access to someone else IS termed "Delegate
PI."  Do not ask me why.

As it turns out, most of the eRA Commons help desk questioned recently
also believed, on first pass, that only a PI could delegate an ASST to
work on their eSNAP.  But I, new to the eSNAP world, actually read the
April 2010 eSNAP manual, and then experimented, discovering that I COULD,
as an SO, perform this delegation for every PI under my realm.  There were
quite a few "No you can't"/"YES I CAN!" conversations with NIH, but as it
turns out, SOs can do it.

As you suggest, this ability to do things in a PI's name does raise
questions.  We have sent a mass email explaining the situation and asked
PIs to tell us if they did NOT want us (in central admin) to delegate on
their behalf to departmental ASSTs.  Not a single PI objected.

This delegation cannot be done en mass but we really didn't want that.  We
simply asked each department for the names of staff members they wanted to
have access to eSNAPs and then delegated, quickly but separately, these
various individuals for their PIs.

Lori has explained the rationale for allowing only PIs to route their
eSNAPs.  Nevertheless, I fail to understand the importance of this
certification.  Final submission of the Type 5 application must be either
by an SO or with the SO's consent.  So what is the issue?  They should let
ASSTs route the applications.

CH

> Charlie,
>
> Your use of terms is a bit confusing.  You did not give admin staff the
role of PI, did you?
>
> Did you in the central office delegate staff with ASST role the right to
work on eSnaps for PIs?  I thought only a specific PI could delegate an
ASST to do this for that PI's projects.  Is it possible for an SO to
delegate eSnap rights en mass?  If the PI does not do the delegation and
does not authorize the submission, then the PI has (could have) no
participation in the process.
>
> How do you do that en mass delegation of the ASSTs, or do you just do it
PI by PI?
>
> Bob
> Robert Beattie
> University of Michigan
>
> Sent from my iPad
>
> On Sep 2, 2010, at 5:54 PM, Charlie Hathaway <xxxxxx@AECOM.YU.EDU> wrote:
>
>> We have delegated PI authority to various administrators to allow them to
>> prepare eSNAP submissions in NIH eRA Commons.  These administrators
have
>> the role ASST.  Can the ASST with delegated access use the "Routing"
feature to e.g. send the application to someone in Central Admin?  It
looks like only the PI can do this, which is of course not very helpful
if
>> we are trying to minimize the administrative burdens on them.
>> Am I not understanding the system?
>> Thanks.
>> Charlie Hathaway
>> ======================================================================
Instructions on how to use the RESADM-L Mailing List, including
subscription information and a web-searchable archive, are available
via our web site at http://www.hrinet.org (click on "Listserv Lists")
======================================================================
>
>
> ======================================================================
>  Instructions on how to use the RESADM-L Mailing List, including
subscription information and a web-searchable archive, are available
via our web site at http://www.hrinet.org (click on "Listserv Lists")
> ======================================================================
>

======================================================================
 Instructions on how to use the RESADM-L Mailing List, including
 subscription information and a web-searchable archive, are available
 via our web site at http://www.hrinet.org (click on "Listserv Lists")
======================================================================