recruiting
Differences
This shows you the differences between two versions of the page.
|
recruiting [2009/09/01 14:20] anthony |
recruiting [2009/09/01 14:27] (current) anthony |
||
|---|---|---|---|
| Line 27: | Line 27: | ||
| ===== Sample Recruiting Workflow (Small Organization)===== | ===== Sample Recruiting Workflow (Small Organization)===== | ||
| - | In a small organization, there may be one person who has primary responsibility for recruiting, and one other person with authority to approve new partners. In this case, the first person should be given the "manage recruits" permission and assigned the "recruit coordinator" role. It's not necessary to assign recruit applications. The second person should be given the "manage recruits" and "approve recruits" permissions, and be assigned the "final approver" role. The first person would process the application until it's "ready for final approval" or "rejected". When the application is changed to "ready for final approval" status, the "final approver" will be notified via email and will then approve (or reject). | + | In a small organization, there may be one person who has primary responsibility for recruiting, and one other person with authority to approve new partners. In this case, the first person should be given the "manage recruits" permission and assigned the "recruit coordinator" role. The second person should be given the "manage recruits" and "approve recruits" permissions, and be assigned the "final approver" role. The first person would process the application until it's "ready for final approval" or "rejected". When the application is changed to "ready for final approval" status, the "final approver" will be notified via email and will then approve (or reject). |
| ===== Sample Recruiting Workflow (Larger Organization) ===== | ===== Sample Recruiting Workflow (Larger Organization) ===== | ||
recruiting.1251814800.txt.gz ยท Last modified: 2009/09/01 14:20 by anthony