| Info |
|---|
This page is a work in progress. If you have questions about the content or questions you’d like us to answer here, please let Cecilia know via Teams or email. Thanks! |
| Table of Contents | ||
|---|---|---|
|
...
Why do we limit who can see records in CHEF?
Unit4, the resource management system, is aware of who reports to who and who is responsible for managing the records for contractors. Access to records is determine by the organizational structure (and record maintenance responsibility) defined in Unit4. Chef is the friendly interface to the resource management system and uses roles related to Unit4 to manage access to records.
CAMP allowed people access to information they didn’t need to do their jobs. To deal with privacy and data security, it is necessary to lock down access to the records per the organizational structureThe resource management system and its sidekick, Chef, are doing a better job of managing the privacy of information.
How do ‘end dates’ work for my RRU resource record and my computer account?
...
| Info |
|---|
Why are we using the CAMP database if CAMP doesn’t exist anymore? Because we’ve just taken the first step in decommissioning CAMP. We could not disconnect the CAMP database from everything at the same time because everything would have broken. We’ve replaced the application called CAMP with the application called Chef. And at the same time, we linked Chef to the (new!) resource management system. But the CAMP database is still connected to Chef. There’s still a lot of work to be done for us to fully disconnect the CAMP database from all other systems. As that work moves along, the information is shared in the directories and in Outlook and Teams will line up with the official information in the Resource Management system. |
...