Fortify on Demand (FOD) role and permission model

Fortify on Demand (FOD) uses role-based access control (RBAC) to determine what actions users can perform within an application.

Each role grants a defined set of permissions. Higher roles inherit permissions from lower roles.

For a complete list of permissions granted to each role, see FOD roles and permissions reference.

Role hierarchy

FOD roles follow this permission inheritance model:

View-Only
↓
GT-Report-Upload-And-Generate-SAST-and-DAST
↓
GT-Application Security Tester
↓
GT-Security Lead
↓
GT-Manager

Each role includes the permissions of the roles above it.

A user is automatically assigned the GT-Manager role in FOD if they are a:

Project Admin (PA) in at least one SHIP-HATS project within the subscription.

This applies even if:

GT-Manager users does not appear in the Manage Users page.
GT-Manager access cannot be removed directly from within FOD user management.
To remove or grant the GT-Manager role, a Subscription Admin must update the user’s Project Admin role.

The role GT-Report-Upload-And-Generate-SAST-and-DAST is reserved for the FOD Service Account and should not be assigned to regular users.

Not all FOD roles can be assigned through Console.

The following roles are available for manual assignment:

As a result:

Some users may have roles that are not displayed for manual editing in Console.
GT-Manager access must be granted or removed by updating the user’s Project Admin role.
The scan role (GT-Report-Upload-And-Generate-SAST-and-DAST) cannot be assigned through Console.