Sometimes there are top secret shows that require that even their jobs don’t show up for people not working on them in the queue.
Would this kind of centralized enforced filtering be possible to implement?
In the User Group Permissions, we currently have the option to prevent users from seeing other users’ jobs, but it sounds like what you would need is an option to prevent users in one group from seeing jobs belonging to other user groups that they don’t belong too?
If that’s the case, we can definitely put it on the wish list.
Cheers,
Ryan
Yes, basically. Coupled with active directory login users, this could make us be able to prevent users seeing others’s jobs.
Other option would be to show the jobs, but obfuscate certain fields (job name, pool etc)
I like the idea of obfuscating as users really need to see that other jobs exist in the queue and the slaves are busy processing a ‘real’ job, instead of some voodoo magic jobs in the queue, which nobody seems to know anything about or can see…
Ooh, active directory login users… does this mean D7 will support LDAP for user authentication as well?
I referred to the ‘use system user for deadline user’ feature, hoping that would work magically with AD logins 
Just to confirm, do you want user group permissions to be able to control which columns a user can see, or do you just want it to mask the data in specific columns? If it’s the latter, then the user can still see all columns for their jobs, but for jobs that aren’t their own, it would just be masked out.
Yep, masked out!
Cool. Now we just need to figure out what to mask the data with. Probably don’t want to leave it blank. Could go with something arbitrary like XXXXXX or ******. Thoughts?
I would say don’t use too many characters, or characters that take up too much space, or things could get really visually cluttered. Maybe *** or —