How do I restrict access to a specific Dispatch Job?
How to lock down a job so even those who would normally have access are restricted.
Sometimes, it becomes necessary to restrict access to which users can even see a Dispatch job's information on your system. If this becomes the case, follow the steps below.
- From the nav bar, click the Administration link in the Modules menu.
- Find and click on the Edit User Access link.
- Click the link Manage Pages - Special Cases and on the resulting page find and click the link to Add Page.
- Enter the following information:
- Page Type: Select the type "Other Page" from the drop down.
- Description: enter a description of the file (e.g. the Dispatch Job's number and/or reason it was restricted) so it will make sense moving forward.
- Path: enter '/person/dispatch/jobPage.asp'
- Querystring: enter 'jobNumber'
- Querystring Value: enter the job number here (just digits, no spaces or letters)
- Click the Save button.
- The Dispatch Job's file is now restricted. ANY user who tries to look it up will get a "Back. You don't have access to this page" message.
- To assign access so selected users can either view or edit this page; find the entry in the table on the Manage Pages - Special Cases menu.
- Click Edit
- Click a box next to a user group to activate the drop down beside it OR enter a person's Last Name into the relevant field and click Find, then select their details from the pop up.
- In the access level drop down, there are three choices: None (this will default), Read Only, and All.
- None: This means the user does not have access to view the page.
- Read Only: This means the user can see the page, and use any links to view information or the items in the Dispatch Menu (unless locked separately), but cannot make any changes to the Job's information.
- All: This gives the user full access to work with the Dispatch Job's page normally.
- Once all relevant access has been assigned, click Save to finish.
NOTE: If a user runs a Dispatch search, they may still see some information that is visible in the row found on the search return. The only way to prevent this would be to prevent them from using the search as well, which isn't usually feasible. To keep notes private in this case, we recommend that after the initial Job Details are entered, add a note that says "See Ongoing Dispatch Notes for more information" and then enter any additional notes for this job into that area. That will keep restricted users from being able to see anything but the generic note via a search return and keep confidentiality intact.