Altamira Recruiting allows organizations to partition the database to give different users access to different CV sets. To do this HR Managers setup projects and grant access to the projects to specific users or groups. CVs can then be copied from any of the other containers into the newly created projects. Recruiters can also configure projects to add CVs automatically based on specified criteria so that these projects become complete and dynamically updated CV repositories.

Users therefore no longer need to access the complete database but only need to access the projects that contain the CVs they are interested in. They can then create other projects or vacancies and use the project setup by their HR manager as their complete CV database.

This usage scenario is typically employed when dealing with branch offices or business units. For example:

• An HR manager from headquarters creates a project for the branch office (say it is located in Lima) and calls it Lima
• The HR manager configures the project to add CVs automatically if the candidate has indicated they live in Lima
• The HR manager grants access to the Lima users to the Lima project either by creating a custom group or by assigning permissions to users individually

The users in Lima would therefore have all the CVs they require in the Lima project and could use this project as their master database from which to copy CVs into other projects. Adding CVs automatically will ensure that new CVs will be moved to the Lima project keeping it current with no further HR manager intervention.

See also: How to use projects, Adding CVs automatically to a project