recruiting
Differences
This shows you the differences between two versions of the page.
|
recruiting [2009/05/18 18:53] anthony |
recruiting [2009/09/01 14:27] (current) anthony |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| Permissions control who is //allowed// to do something, whereas roles define who is //responsible// for doing something. | Permissions control who is //allowed// to do something, whereas roles define who is //responsible// for doing something. | ||
| - | Permissions are set under an admin user's "system account" tab in channelADMIN. There are 4 permissions relevant to the Recruiter function: | + | Permissions are set under an admin user's System Account tab (**Administrators > Summary > users name > Systems Account**). There are 4 permissions relevant to the Recruiter function: |
| - | * the "manage recruits" permission is needed to make updates to the Recruit record, such as marking off checklist items, adding endorsements, or adding notes or attachments. | + | * the **Manage Recruits** permission is needed to make updates to the Recruit record, such as marking off checklist items, adding endorsements, or adding notes or attachments. |
| - | * the "approve recruits" permission is needed to grant final approval and create a new Partner record. Only users with authority to sign off on partner applications should be granted this permission. | + | * the **Approve Recruits** permission is needed to grant final approval and create a new Partner record. Only users with authority to sign off on partner applications should be granted this permission. |
| - | * the "system manager" permission is needed to add new checklist items and manage the email notifications. | + | * the **System Manager** permission is needed to add new checklist items and manage the email notifications. |
| - | * the "manage administrators" permissions is needed to grant permissions and assign roles. | + | * the **Manage Admin Accounts** permissions is needed to grant permissions and assign roles. |
| - | There are 3 roles related to the Recruiter function: | + | There are 2 roles related to the Recruiter function: |
| - | * the "recruit coordinator(s)" receive an email when new recruit applications are entered in the system, and are expected to either assign the application to another admin or move the application forward. The recruit coordinator role is set through the tool options section of the Recruit menu. Anyone with this role should also have the "manage recruits" permission. | + | * the **Recruit Coordinator** receive an email when new recruit applications are entered in the system, and are expected to either assign the application to another admin or move the application forward. The recruit coordinator role is set at **Recruits > Manage Other Settings**. Anyone with this role would need to have the **Manage Recruits** permission. |
| - | * the "final approver(s)" are notified by email when a recruit application is changed to the "ready for final approval" status by any of the admins. Only people with the "approve recruits" permission are eligible for the "final approver" role. This role is specified through the recruit options screen. | + | * the **Recruit Final Approval** role is notified when a recruit application is changed to the "ready for final approval" status by any of the admins. Only people with the **Approve Recruits** permission are eligible for this role. |
| - | * the "assigned admin" is (optionally) specified //on a per-application basis// through the recruit edit screen. The assigned admin is the person responsible for moving the application through the process until it's eventually ready for final approval or rejected. The assigned admin is notified by email as updates are made to the application by other admins. Only people with the "manage recruits" permission are eligible to have recruits assigned to them. Recruit applications can be reassigned if needed. | + | |
| ===== 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) ===== | ||
| Line 38: | Line 37: | ||
| * **Can I get an email notification when a new recruit application is received?** -- Yes, if you have the "recruit coordinator" role. Multiple recruit coordinators may be assigned. | * **Can I get an email notification when a new recruit application is received?** -- Yes, if you have the "recruit coordinator" role. Multiple recruit coordinators may be assigned. | ||
| * **What's the difference between "new" and "open" status?** -- The "new" status indicates that nobody has started to process the application yet. | * **What's the difference between "new" and "open" status?** -- The "new" status indicates that nobody has started to process the application yet. | ||
| - | * **Can I get email notifications when updates are made to a Recruit?** -- You'll receive notifications of updates if you're the assigned admin for a specific recruit. There can be only one assigned admin for a recruit. | ||
| - | * **What's the difference between assigning and referring an application?** -- The assigned admin is responsible for getting the recruit application processed, and is notified by email of updates. In the case of a referral, you're asking for input on the application, but the primary responsibility is not shifted to the referred admin. | ||
| * **Why can't I approve this recruit?** -- Only admins with the "approve recruits" permission can approve an application. However, you can change the status to "ready for final approval", and admins with the "final approvers" role will be notified that approval action is required. | * **Why can't I approve this recruit?** -- Only admins with the "approve recruits" permission can approve an application. However, you can change the status to "ready for final approval", and admins with the "final approvers" role will be notified that approval action is required. | ||
| * **How do recruit applications get into the system?** -- They can be entered by admins, or they can be received from a public website (see the integration section below) | * **How do recruit applications get into the system?** -- They can be entered by admins, or they can be received from a public website (see the integration section below) | ||
recruiting.1242672818.txt.gz · Last modified: 2009/05/18 18:53 by anthony