Requests, Inventory, and Deployments (RID) Process Permissions Premium board icon

Process permissions provide an easy way of establishing a routing process for your WebEOC Nexus system. Typically, a user group can send requests to positions in their own agency/organization/department or send requests to a controller—someone who controls the routing of those requests. A controller group can route to other controllers and to positions within their own agency/organization/department.

There are two process permissions that are automatically imported along with the RID board:

Agency: Establishes a relationship among positions for the purposes of filtering requests, inventory, and deployments.

RID Requesting: Used to create a request routing hierarchy. Must be used with the Permissioned Assignment board permission tag when assigning the RID board.

The use of these process permissions is optional.

The following are examples of groups that could be used along with the above process permissions:

  • City A Users

  • City B Users

  • County 01 Users

  • City A Controller

  • City B Controller

  • County 01 Controller

The following table can serve as a reference for assigning process permissions to different groups for creating agencies and a routing hierarchy.

RID process permission configuration
Group Process Permissions Groups
Agency RID Requesting

City A Users

County A Users

County A Controller

City A Controller

City A Controller

City A Users

City A Controller

City A Users

City A Controller

City B Controller

County 01 Controller

City B Users

City B Users

City B Controller

City B Controller

City B Controller

City B Users

City B Controller

City B Users

City B Controller

City A Controller

County 01 Controller

County 01 Users

County 01 Users

County 01 Controller

County 01 Controller

County 01 Controller

County 01 Users

County 01 Controller

County 01 Users

County 01 Controller

City A Controller

City B Controller

In this example, members of the City A Users group can view records from anyone in City A but can only route requests to the City A Controller. Meanwhile, the City A Controller can route requests to anyone in City A, as well as to the City B Controller and the County 01 Controller.

For further information on Creating and Assigning process permissions: