Grants.gov Roles & Privileges
When an applicant organization user registers with Grants.gov, the organization E-Business Point of Contact (EBiz POC) -- or a user with the Expanded AOR role -- can assign the user a core role, a custom role, or no role.
E-Business Point of Contact
The E-Business Point of Contact (EBiz POC) works primarily at the administrative level to (among other tasks) assign roles to organization users once they register with Grants.gov.
Users assigned a core role have a specified list of privileges inside Grants.gov. The Expanded AOR role comes with the most privileges, some of which are administrative. The Standard AOR role allows the user to submit the final application, among other things. The Workspace Manager role, meanwhile, is the most basic core role in Grants.gov. It is the minimum role required to create a workspace and begin work on an application.
Assigning and Using Custom Roles
Users with a custom role can be given any combination of the below privileges. If your organization uses custom roles rather than the core roles in Grants.gov, we encourage you to develop internal training resources based around your custom roles. Why? The Grants.gov Online User Guide uses the core roles (i.e., Workspace Manager, Standard AOR, and Expanded AOR) to explain which users may access and perform actions.
The following table lists the privileges associated with each core role, as well as those associated with the EBiz POC.
|Privilege (Click for Details)||Type|
|Manage Applicants (All Roles)||Expanded|
|Manage Applicants (Basic Workspace Roles)||Standard|
|Manage Participants for Organization Workspaces||Expanded|
|Manage Participants for My Workspaces||Standard|
|Participant Activities for Organization Workspaces||Expanded|
|Submit Applications for Organization Workspaces||Expanded|
|Submit Applications for My Workspaces||Standard|
|Check Application Status for Organization||Expanded|
There are additional actions that can be taken by registered Grants.gov users within a workspace.
Participants in a Workspace
Except for applicants with the Expanded AOR role, users must be added to a workspace (become "participants") in order to complete workspace-level actions. Generally, workspace participants fall into one of three categories: The Workspace Owner typically serves as an administrator for that particular Workspace. Any participant with the AOR role is able to submit the application and is informally called a Workspace AOR. All other non-AOR users added to a workspace are called Workspace Participants; no roles are required to be a Workspace Participant.
The following table lists the actions that each participant type can take within a workspace. Contrast these actions with those available to any user with the Expanded AOR role.
|Action in a Workspace|
|Become a Workspace Owner*|
|Select/Deselect Optional Forms|
|Assign Form-Level Access|
|Complete and Notify AOR**|
* Workspace ownership requires that users/participants have a role with the "Own Workspace" privilege.
** If a Workspace Owner has a "Submit Applications..." privilege, then the Complete and Notify AOR action will not be available to him/her.
Form-level access can be assigned at the organization level by the EBiz POC and/or by a user with the Expanded AOR role.
At the workspace level, access to forms can be assigned by a user with the Expanded AOR role, the Workspace Owner, and/or by any participant who has the Standard AOR role.
The following table lists the three form access levels and notes the type of forms that each grants access to.
|Form Access Levels||Regular Forms||Regular Subforms||Budget Forms||Budget Subforms|
|All Forms in a Workspace|
|All Non-Budget Forms in a Workspace|
|Specific Subforms Only|