Our earlier RBAC model, was more restrictive enforcing a clear compartmentalization of users from each other and basic roles only. With the new RBAC model, we have added more roles, depicting the real-life hierarchies and responsibilities.
A job can now be shared with other users by making them Co-Authors of the job. Co-authors should have the same (or higher) role and same (or larger) asset scope assigned to them for administration so that they can edit/ operate the job equivalent to the creator (owner).
If you want to temporarily allow additional users to edit/ manage a job, you can make them Co-Author(s) of the job. This can be done by adding the users to the job under the Job Access options while creating a job.
If you want to permanently transfer ownership of a job to another user, you could achieve that by changing the ownership of the job.
To change the owner of the job, you must have “Change Owner” permission i.e. “Patch Manager” role. You can change ownership of jobs, in bulk or on individual jobs. From the Jobs tab, select a one or more job(s) and then from the Quick Actions menu, choose "Change Job Owner" option. Select the username of the new Job owner and click Apply. A message confirms that the job ownership is transferred to the selected user.
If the new owner has the same (or higher) role but a different asset scope assigned to them, the jobs could execute differently. The endpoints targeted by the job will be limited to the assets that are common between the asset scope of original owner and the new owner. A Patch Manager would need to revise the asset scope of the new user to ensure execution of the job as before the ownership change.
If the new owner has a role lower than Patch Manager OR Patch User, the jobs may not execute at all. If a job, especially a partially configured one, created as an advisory, it has No Owner. Ownership for such a job needs to be established by explicitly assigning an owner to such “Partially Configured Jobs”.