Understanding permissions is important to grasp before diving into the system, for permissions are the backbone to a user's experience in the STIP Manager. Without the proper permissions, the STIP Manager will almost mirror the STIP Viewer, preventing the user from implementing changes, adding content, or deleting information.
How do I find my permissions?
On the right side of the Main Menu, the user can view five icons in the Utility Bar. The second icon that resembles a person hosts the user permissions. After selecting the icon, the user should be able to view their given permissions under the title "User Role."
Why can't I perform this action?
Most likely, a user does not have the proper permissions to perform a certain action if it is not available on their screen.
What does my permission title mean?
There are two categories of permissions: (1) User Role and (2) Optional Permissions. The User Role is an overreaching title with a variety of actions, and the Optional Permissions are specific actions a user can take in the system. Consider the two tables below to understand both permission types and their capabilities.
| User Role | Optional Permissions Available | Capabilities |
| Highway (FHWA) Approver | Dashboard, Scenarios, Standard Reports, and All Project Detail View | Approve or reject Amendments on the Actions Revisions tab that have been submitted to FHWA for approval; must have 4-digit PIN. |
| Other NCDOT User | Actions Staging, Actions Pre-Approval, Actions Revisions, Code List Maintenance, Dashboard, Scenarios, Standard Reports, User Maintenance, and All Project Detail View | Edit ability of projects. Can limit project access by selecting 1+ divisions. If no division is selected, the user has edit access to all projects. |
| STIP Administrator | None-- all permissions are implied | Edit ability for all STIP Manager modules except Highway (FHWA) Approver and Transit Approver roles; all Administration functions. |
| STIP Unit User | Default to include Actions Staging, Actions Pre-Approval, Actions Revisions, Dashboard, Scenarios, Standard Reports, and All Project Detail View; can add Code List Maintenance and User Maintenance on an individual basis | Edit ability of projects. Can limit project access by selecting 1+ divisions. If no division is selected, the user has edit access to all projects. |
| MPO/RPO User | Dashboard, Code Lists Maintenance, Scenarios, Standard Reports, User Maintenance, and All Project Detail View | Edit ability of projects and Actions Staging tab for assigned MPOs/RPOs. Can limit project access by selecting 1+ MPOs/RPOs. Can also endorse the amendments within assigned MPO/RPO on the Actions Revisions tab for which Federal approval is required. |
| Transit Approver | Dashboard, Scenarios, Standard Reports, and All Project Detail View | Approve or reject Amendments that have been submitted to FTA for approval; must have 4-digit PIN. |
| Optional Permission | Capabilities |
| Actions Pre-Approval | Edit the Pre-Approval tab. |
| Actions Revisions | Edit the Revisions tab. |
| Actions Staging | Edit the Staging tab. |
| Code List Maintenance | Edit the Code Lists administration module. |
| Dashboard | Can view the Dashboard module. |
| Scenarios | Create and view the Scenarios module. |
| Standard Reports |
Access to the Standard Reports interface. |
| User Maintenace | Edit the Users administration module. |
| All Project Detail View | Can see all of the Project Funding/Milestones and Funding Outlay table, even if the Prioritization Status of a project is set to “Will be Reprioritized” or “Not Funded.” |
Comments
0 comments
Please sign in to leave a comment.