User can find the jobs executed against the targets for which he does not have access.
Picture with example:
Aria Automation Config 8.X
This is by design behavior.
The idea being that an admin can create a job on behalf of a less entitled user against a specific target, limiting the scope of execution. So the user can only run that job against that target.
When Admin creates the JOB and explicitly assigns the target group to it, user can run the Job successful despite not having regular access to the target defined in the job.