Skip to main content
Question

Issue with Custom Roles in Veeam v13 – Job List Not Visible

  • March 31, 2026
  • 3 comments
  • 23 views
C

Hi community,

I’m running into an issue with Custom Roles in Veeam Backup & Replication v13, and I’m hoping someone can point me in the right direction.

I’m trying to create a restricted Backup Admin who should only see and manage specific backup jobs and specific repositories. However, I’m experiencing the following behavior:

  • If I configure the custom role with limited permissions (selected jobs and/or selected repositories),
    → the user does not see any jobs at all.
  • If I grant broader permissions (effectively “Full Access”),
    → the jobs appear, but then the user sees all jobs, not just the intended subset.

I’ve tried several configurations, but the result is always the same:

Either zero jobs are visible, or all jobs become visible when access is unrestricted.

My goal is to allow a delegated admin to operate only a defined set of backup jobs and use only the repositories assigned to them — nothing else.

Has anyone successfully configured granular visibility in v13?
Any examples of working configurations or best practices would be greatly appreciated.

 

Thanks in advance!

    3 comments

    Andanet
    Forum|alt.badge.img+12
    • Andanet
    • Veeam Legend
    • March 31, 2026

    Hi ​@Chrissawi 

    backup job visibility cannot be assigned directly. Visibility is indirect and follows an "all-or-nothing" logic based on the Scope.

    A user with a custom role will only see an existing job if they have visibility permissions for EVERY object included in that job.

    If the user sees "everything" with full access but "zero" with limited access, the issue is almost certainly a mismatch in the objects:

    Open the existing job settings and verify which objects are included (under the Virtual Machines tab).  Go to the user’s Custom Role settings, in the Inventory Scope add exactly those objects (or the parent folder containing them). In the Repository Scope , select the destination repository used by that specific job.

    Please try with these secs and let me know what happens. 

     

    Antonio D'Andrea | VMCE 2021 | VMCA 2022 | VMTSP2024 | Veeam Legend | VUG Italy Leader | Object First Ace | VCP6-DCV | I want it written on my tombstone "Please start a restore to the last valid backup"
      coolsport00
      Forum|alt.badge.img+21
      • coolsport00
      • Veeam Legend
      • March 31, 2026

      Hi ​@Chrissawi - Welcome to the Community!

      As custom roles is new to v13, exact usage on how to create will need some trial & error no doubt. If what Antonio offered as a suggested way to get you sorted doesn’t work, you of course can always reach out to Veeam Support to get further help & explanation on the behavior of how custom roles within VBR v13 work and should be configured based on your needs. 

      And I recommend starting with the User Guide if you haven’t already:

      https://helpcenter.veeam.com/docs/vbr/userguide/configure_roles.html?zoom_highlight=custom+role&ver=13#custom-roles

      Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
        eblack
        Forum|alt.badge.img
        • eblack
        • Influencer
        • April 1, 2026

        In short: The v13 scoping model is workload-centric (VM/source-based), not job-centric. It's designed so delegated users manage their own jobs within a defined workload scope, not operate a subset of centrally-created jobs.

         

        1. Have the delegated user create and own their own backup jobs within their scope. The admin pre-creates the scoped role and user; the delegated user then creates jobs which will automatically be confined to their assigned workload and repository scope. They'll only ever see their own jobs.
        1. Or, use dedicated repositories as the boundary. Put the workloads you want delegated into jobs that target a repository used exclusively for that delegation. Then scope the custom role to that repository. This gives the clearest separation, since the repository becomes the visibility anchor.

         

        I’m sure there are some other options but these are the ones I’ve made use of. 

         

         

         

         

          Terms & ConditionsAccessibility statement