This shows you the differences between two versions of the page.
help:admin:recruit_detail [2009/05/18 18:27] anthony |
help:admin:recruit_detail [2009/09/01 13:50] (current) anthony |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Recruit Detail ====== | ====== Recruit Detail ====== | ||
- | ===Company Details=== | + | For information on setting up internal admins to service Recruiter, please click [[recruit_manage_email_notifications|here]]. |
- | The company details are captured via the recruit form that an interested partner fills out. | + | |
- | FIXME After a recruit has been approved, the Admin will need to edit the Theater and Region of this section. | ||
- | ===Endorsements=== | + | ====Company Details==== |
- | Anyone with the permission to act on a recruit (FIXME what permission?) has the ability to log an endorsement. This endorsement is a simple thumbs up/thumbs down, and is meant as supporting data for the final approver to make their decision. | + | These details are either manually entered by an Admin or captured via the recruit form that an interested partner fills out online. |
- | Users may log multiple endorsements should they so wish. | + | ===What happens when approved=== |
+ | Something to keep in mind is that when a recruit is ready to be approved, an Admin will need to edit/assign a Theater and Region within this section. | ||
- | ===History=== | + | Upon approval the appropriate Detail fields will be saved as new Partner, Location, and Contact records. |
+ | ====Endorsements, Notes & Attachments, Check List==== | ||
- | * Why can't I see all the administrators? | + | This includes the ability to log an endorsement; add a note and attachment; or check off an item from the checklist. These actions are intended to be supporting data for the final approver. |
- | * must have theater and region to approve application | + | |
- | How to move it to completion. | + | |
- | Any notifications sent out? | + | |
- | Checklist values come from where? | + | |
- | What happens to the data after an approval. | + | |
+ | In the case of **Endorsements** and **Notes/Attachments**, users may log multiple entries should they so wish. | ||
+ | |||
+ | ====Process==== | ||
+ | A complete overview of the Recruit process may be found in the "How To" Guides -Partner Recruiting with ChannelSUITE [[/recruiting|here]]. | ||
+ | |||
+ | Some quick takeaways are: | ||
+ | * Recruiter application was designed with flexibility in mind. | ||
+ | * A new recruit entry sends a notification to admins who have been setup with the **Recruit Coordinator** role | ||
+ | * These admins can either take action or assign the recruit to another admin for their follow up. | ||
+ | * Should it become apparent that the recruit's status should be changed the admin may take the action of either **Rejecting the recruit** or stating that it is **Ready for Approval**. | ||
+ | * The RFA status will send a notification to users who have been setup with the **Recruit Final Approval** role. If they have Approve Recruits permission, they can then log into the system and approve the recruit application. | ||
+ | |||
+ | Something to keep in mind is that if a recruit is set as rejected, but needs to have its status looked at again, an admin may choose **Open Recruit** to activate the process. | ||
+ | |||
+ | ====Mini-FAQ==== | ||
+ | * **What gets logged to History in Recruiter?** The history logs the following: | ||
+ | * the entry of a New Application record | ||
+ | * status change | ||
+ | * admin assignment | ||
+ | * admin referral | ||
+ | * note added | ||
+ | * application update/edit | ||
+ | * new endorsement | ||
+ | * check list item update | ||