Create a workgroup in Tidal for the agency, dept., etc. Add necessary staff to that group. Change the ownership of those jobs to that group.
Only the members of that group will be able to see or touch those jobs.
To take it one step further, create Security Policies that will allow you to grant more or less permissions to staff inside that group.
For example, we have several different state agencies on our Tidal system. They want to make sure no other agency can see or touch their stuff, and they also have some staff who are 'admins' and create/modify jobs, calendars, etc., and others who are just operators and may only need to view certain items or re-run a job.
We created a workgroup called Agency1 and placed all members of that agency in that workgroup. We then created a security policy called Agency1Admins and added the 'admins' from that agency to that security policy. A second policy was added called Agency1Users and the lower level users from that agency were added.
Jobs are placed in Job Groups owned by the agency to help keep things neat.
The result is that only Agency1 staff can see the objects (jobs, calendars, events...) owned by that workgroup. Agency1Admins can create/edit/delete items owned by the workgroup, and Agency1Users can see everything owned by the agency, but have a more limited set of tasks they can perform.