Receiving Coordinator - Destination Coordinator Assigning/unassigning
1.
<span>[Knowledge Base](index.html)</span>
</div>
# <span id="title-text"> Knowledge Base : Receiving Coordinator - Destination Coordinator Assigning/unassigning </span>
</div>
<div id="content" class="view">
<div class="page-metadata">
Created by <span class="author"> user-b1fcb</span>, last modified by <span class="editor"> user-10cb2</span> on Oct 29, 2021
</div>
<div id="main-content" class="wiki-content group">
**<span style="color: rgb(0, 0, 0);">Receiving Agency Related Guide (RARG)</span>****<span style="color: rgb(0, 0, 0);">Summary: </span>**<span style="color: rgb(0, 0, 0);">This guide shows how to add a *destination contact* on the **destination maintenance** screen. If you provide destination coordinators with HSPnet user accounts/access, you can have as many back up destination coordinators as you like, but those are assigned on the destination profile, under *other contacts*. The individual assigned on the **Destination Maintenance** page is the name that will appear as the **destination coordinator/destination contact** on student placement requests and if the individual has a user account, the box "E-mail alerts accepted" must be checked or the system will not recognize that you have assigned a user. The only time any names on *Other Contacts* overrides the **destination contact** is when you set up a [Discipline Contact](https://kb.hspcanada.net/x/u4_v).</span><div class="table-wrap"><table class="wrapped relative-table confluenceTable" style="width: 100%;"><colgroup><col style="width: 55.3112%;"><col style="width: 44.6399%;"></colgroup><tbody><tr><td colspan="1" class="confluenceTd">
Destination Coordinator role must be in the staff record.
A Destination Coordinator (contact) needs to have the role "Destination Coordinator" identified in their Staff Record in order to appear on the Destination Coordinator drop down lists.
If you are uncertain, or if the staff record doesn't exist, please see one of these linked guides and then return here.
If you also wish to issue a user account:
Navigate to the Destination Maintenance page to add the Destination Contact:
- Click: Maintenance.
- Click Setup/Lookup.
- Click: Destinations.
On the Destination Maintenance Page:
-
Click the garbage can icon to remove the service. Best practice is also to save a blank space instead of a name to the Destination Contact prior to removing the service.
-
Click the pencil (edit)icon to add or remove a destination contact.
On the Edit Entry screen:
- Select the name of the individual you wish to add from the drop down list (or select add new, the second "name" on the drop down list - the "top name" is a blank.
- Save the changes with the green check mark.
User maintenance screen:
-
The Destination Coordinator's personal access will be automatically updated to include the service and destination you assigned them to, but NOT their discipline or department access which needs to be updated manually. Also, if you remove a destination contact user, and this individual is still going to have a role on HSPnet but at a different destination: you MUST REMOVE the service and the Destination from their personal access manually by moving the service and destination out of the user's allowed box (and save the changes).
-
The screen capture in user maintenance (Click the Destination Coordinator's user key
to open this screen) shows where this change is made.For more information, please see sections 8 through 11 of Receiving Agency User Accounts.
-
The screen capture in user maintenance (Click the Destination Coordinator's user key
If the Destination Coordinator you removed/unassigned, no longer has a role on HSPnet, their account needs to be inactivated in Staff & User Maintenance with the inactivate icon:
For more information please see deactivate/reactivate a staff record.
<div class="pageSection group">
<div class="pageSectionHeader">
## Attachments:
</div>
<div class="greybox" align="left">
[worddav103e9150bc210e4ea96fb3167bf76585.png](attachments/14155906/14155905.png) (image/png)
[worddav8a5b8c990c8efc5489c4c9da98ac884b.png](attachments/14155906/14155907.png) (image/png)
[worddav5a680f96c6637a584af175cb7716811f.png](attachments/14155906/14155908.png) (image/png)
[worddav26afddb83f4a415e5bf83381cef99261.png](attachments/14155906/14155909.png) (image/png)
[worddav18e478bdeefd003b361582021bc8a43d.png](attachments/14155906/14155910.png) (image/png)
[worddav9fd846f8e89964a20a56e1504306c45d.png](attachments/14155906/14155911.png) (image/png)
[worddav0589f0c557836e995ad0df7a1df8baab.png](attachments/14155906/14155912.png) (image/png)
[worddav010ccd3f57e965c73f912290d3376f35.png](attachments/14155906/14155913.png) (image/png)
[worddavd94cf4338d1adaf901ba1b635903e61a.png](attachments/14155906/14155914.png) (image/png)
[worddav0e1851ce23a4040d631d942159eb6841.png](attachments/14155906/14155915.png) (image/png)
[worddav1ad7bb0c18fb971956c42be5595af37e.png](attachments/14155906/14155916.png) (image/png)
[worddav9c483717155d56e8f6f93574098bd41e.png](attachments/14155906/14155917.png) (image/png)
[worddav4e065bc4ec9749e687f04c83e91b1fa6.png](attachments/14155906/14155918.png) (image/png)
[image2020-6-24_8-27-43.png](attachments/14155906/33359901.png) (image/png)
[image2020-6-24_9-16-57.png](attachments/14155906/33359914.png) (image/png)
[image2020-6-24_9-22-51.png](attachments/14155906/33359919.png) (image/png)
[image2020-6-24_9-25-12.png](attachments/14155906/33359926.png) (image/png)
[image2020-6-24_9-33-17.png](attachments/14155906/33359941.png) (image/png)
[image2020-6-24_9-54-14.png](attachments/14155906/33359953.png) (image/png)
[image2020-6-24_10-3-55.png](attachments/14155906/33359964.png) (image/png)
[image2020-6-24_10-4-50.png](attachments/14155906/33359966.png) (image/png)
</div>
</div>
</div> </div>
<div id="footer" role="contentinfo">
<section class="footer-body">
Document generated by Confluence on Nov 03, 2023 14:44
<div id="footer-logo">[Atlassian](https://www.atlassian.com/)</div>
</section>
</div>
</div>