## 4.4.2 Recommendations 

To properly set up the security of the Records Manager system, you must understand the concepts behind Records Manager security as discussed earlier. In addition, we provide some recommendations for the Records Manager security setup. 

These setup recommendations also reflect how our sample scenario used in this book is set up. 

## Recommendation for user and user group setup 

For every Content Manager user who has to declare records, you must import a Content Manager user ID into Records Manager. This user needs the File Plan Administration function access right. 

## Recommendation for permissions setup 

Every user who has to declare records into a specific component needs View access to all components mentioned above in the hierarchical file plan, and View, Add, and HostRetrieve access permissions to the component itself. 

## 4.5 Content Manager Records Enabler security 

## 4.5.1 Overview 

Records Manager provides the records management engine that you can embed into your business application. Content Manager Records Enabler (CMRE) works between Content Manager and Records Manager to bring records management capability into Content Manager. 

In this section, we discuss Content Manager Records Enabler security. 

The Records Enabler does not have its own security model. It uses the Content Manager and Records Manager’s security. One of the main functions of the Records Enabler is to transform Records Manager security into Content Manager ACLs. Content Manager Records Enabler has to have a Content Manager user ID with the appropriate rights to create new ACLs and item types. Figure 4-13 on page 92 shows the user IDs (CMREID and administrator) used by Records Manager to communicate with the connected systems. 

