Job actions not available for workload administrators with limited RBAC permissions on assets
Note following issues for view and managing jobs with the NetBackup web UI:
A job does not receive an asset ID until it runs, which means a queued job does not have an asset ID. Users that have roles with more granular asset permissions for a workload are not able to view or cancel queued jobs.
This behavior does not affect users with an RBAC role that has full job permissions or a role that can manage all assets for a particular workload.
A job does not receive an asset ID if the asset is not yet discovered. Users that have roles with more granular asset permissions for a workload are not able to cancel or restart a job for the asset.
This behavior does not affect users with an RBAC role that has full job permissions or a role that can manage all assets for a particular workload.
An asset ID is not set for a cloud convert job. Users that have roles with more granular permissions for VMware assets can't view these jobs.
This behavior does not affect users with an RBAC role that has full job permissions or a role that can manage all VMware assets.
Consider a user that has RBAC permissions only for a VMware vCenter or one or more VMs.
The user cannot see queued jobs for the vCenter or for the VMs.
Similarly, the user is not able to cancel any queued jobs for the vCenter or for the VMs.
Consider a user that has RBAC permissions only for a VMware vCenter or an RHV server. This user also has one or more job permissions for these assets, but does not have job permissions for all workload assets.
A new asset is added to the environment, but the discovery process hasn't run yet.
An existing intelligent group is configured so it includes the new asset.
When the backup runs, it includes the new asset in the backup.
The user is not able to cancel or restart a job for the new asset.