Workcenter and submitted job security

We're going live on E1 9.0 next month and are trying to find a way to give certain users access to others users submitted jobs and workcenter messages. For example, we want the A/R group to have access to submitted jobs and workcenter messages for all users in the group. We haven't been able to find a way to do this (I searched this and other forums) and wondering how others with this requirement have handled the issue.
Thanks for your help.

what about setting queues for specific groups and use row security by queue?

For the WSJ screen I have copied the program and added a processing option to the custom version to pass in the user id and then grant access to this program for certain individuals. This help when people need to see output from the night jobs so we pass in the id that runs the nightly jobs.

You can grant access to a user id for other user ids in P01135. We have a large number of scheduled jobs that submit under user SCHED and have granted access to the Personal In Box for SCHED to a number of users that monitor those jobs. In our case, only CNC has the security to set up the access.

Vicki,
That is exactly what we need for workcenter - don't know why our consultants didn't know about this but they will. The best news is that no mods are required. Thanks everyone for your quick replies.

Can you clarify on the solution that you implemented?

We have a situation where our a few Finance Roles want wide open access to Work with Submitted Jobs (WSJ) to view other Finance users jobs/reports. Which is easy enough....just set column security to only allow those roles access to change the user ID field.

The problem is that we are also implementing Payroll, and of course that dept requires complete lock down of WSJ so only selective Roles can view other people's jobs (Finance roles not included). So the two conflicting requirements has us stuck without a solution. We thought of setting Row security at the job queue level since Finance and Payroll jobs process in separate queues, but Row security does not work on system tables without some questionable effort at the jdekrnl level (per Oracle solution doc).