Staff/Users - User Account - Receiving Agency new user set up and editing
1.
<span>[Knowledge Base](index.html)</span>
</div>
# <span id="title-text"> Knowledge Base : Staff/Users - User Account - Receiving Agency new user set up and editing </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"> Erik Graham</span> on Mar 03, 2022
</div>
<div id="main-content" class="wiki-content group">
**Receiving Agency Related Guide (RARG)****
Summary:**-
- This guide explains how to create new user accounts at your agency from an existing staff record.
-
- If the staff record is not been created yet, follow the directions on this knowledge base page first:
[ Staff/Users - Staff Record - Create (or edit) a new staff record (non-user - no User ID)](https://kb.hspcanada.net/x/14Bz)-
- You may copy an existing user access rights. Even when the access is copied from a local HSPnet administrator, all new user accounts will initially be at the regular level only, which is normal for destination coordinators (yellow user key).
-
**- Users in the RC role need to attend additional training (webinar and/or classroom training) to obtain the level of Local Administrator, which is added by HSPnet support on completion of the additional training. The Local Administrator level provides additional editing icons to the user.
<span
class="confluence-anchor-link"
id="Staff/UsersUserAccountReceivingAgencynewusersetupandediting-TopAnchor"></span>****[
Step by Step instructions: Create A User Account: Receiving Agency Instructions for Receiving Coordinators.
Receiving Agency user roles are all compatible, so multiple roles of Receiving Coordinator, Destination Coordinator, and Supervisor are possible in one user account. There is a warning that Receiving and Destination coordinators are not normally combined, but you can still click: Okay and proceed. Click: Maintenance/Staff/Users. Search the database (including inactive staff) to locate the staff record. When you locate the staff record, use the Department drop down list or the go to icon to filter to a single department and access the edit icon and user key icon for the staff record. If needed, edit the role (Receiving Coordinator, Destination Coordinator, Supervisor, Department Contact. Administrator). If the Staff member is not in the database, please add the staff record then return to the steps below. |
|
If there is a user account already, the key can still be opened to edit the user account; the keys will be:
|
|
2. Create a user ID, normally first initial and last name. If that user ID is already in use you will be alerted and you can resolve this by adding a number to the standard format such as dcorgi2. User ID's are not case sensitive. An e-mail address could also work as a user ID, but "forgotten password help" gives the hint the user ID will be first initial and last name. Potentially, you may see your own user ID appear when you click on the blank field - this is your auto-fill from your browser - backspace/overwrite it - type in the user ID you plan to assign to this Click: Next |
|
4. Click: Next. |
|
Copying access from a local administrator to a new user will provide the same agency access (Sites, Services, Destinations and Disciplines) but as a regular user only; additional training is required for local administrator level access, which HSPnet support will add when RC training is complete. If you have copied a user access, this is your final step; please continue if you are not copying a user to set up a new user correctly. |
|
5. The department where the user record is located becomes the user's home department. If the user requires access to other departments click to highlight and select those departments in the not allowed box: then click arrow key to move the department over to the allowed box. Departments on HSPnet are collections of staff records/names. Access to these departments is required for anyone assigning staff names on HSPnet from that department. A Receiving Coordinator may have access to all or most departments. Most Destination coordinators would only need (and should only get) access to their home department. Departments that show in light grey lettering only, are departments you do not have access to. Another RC with access could provide access to you or edit this account afterward to add it to this user's access. An example of someone who would need more than one department would be a nurse that may coordinate maternity placements at two different hospitals. In the screen capture sample, Doberman's home department is at Mitchel Hospital Nursing; |
|
6. User access is on a need to know basis. Receiving Coordinators may need "all disciplines," but a Destination Coordinator's access is normally restricted. Only the disciplines coordinated by the user should be included, and these should correspond to the sub-disciplines identified on the capacity tab of the Destination Coordinator's destination profile in the services the DC is assigned to. You need to check individual and group capacity to identify all of the disciplines/sub-disciplines required, and on all of the destination profiles the destination coordinator is assigned to on destination maintenance (these can be assigned by service, so it is possible for example to have one destination coordinator assigned to the services of administration and nursing on one destination profile, while another destination coordinator may be assigned to the same destination profile, but to the service of Physiotherapy). To assign access to disciplines, click to highlight and select them in
The second screen capture shows the Destination Profile Capacity tab for the above coordinator. Doberman does not have access to Nursing/Practical Nursing, as the unit does not consider this type of student, as they have no LPN's on the unit that could supervise LPN students. Click: next |
The destination profile capacity matches the access given above.
|
7. Determine the sites the destination coordinator needs access to. Select them from the "not allowed" box by clicking to highlight them, and then lick the right facing arrow to move them to the "allowed" box. When ready, click: Next |
|
8. The services needed by the destination coordinator should only be those the destination coordinator will be coordinating. In this model Doberman coordinates Unit Clerk students, so needs the service of Administration; Doberman also coordinates all of the nursing students, and the main nursing service at this destination is Pediatrics, so Peds/IP needs to be included. Doberman also coordinates the Health Care Assistants, which at this destination are under the service of "Other Health." Important: This guide still shows how to set up a new user, but when you assign a destination coordinator on the destination maintenance screen (second screen capture): the assigned services and destinations will
Click "Next." | |
9. When you set up Destination access, you also need to do this in conjunction with the drop down list on the left: Site: Service.
10. Finally, select HME: OthHealth on the Site: Service drop down in order to select and move HME: OthHealth: MHComHME from the "Not Allowed" box to the "Allowed" box. Click "Next" when done. |
|
11. Review the information; if everything is correct: use one of the save buttons (or click the |
|
|
Receiving Coordinator Training:
Destination Coordinator Training: HSPnet does not have a formal training program for Destination Coordinator users. User guides are linked into their account under online help, including training videos. Receiving Coordinators may choose to create their own training programs for destination coordinators that could cover their agency policies, responsibilities, etc, of which HSPnet is a portion of the training agenda. Destination Coordinator Training Video Index: https://kb.hspcanada.net/x/6Bz9AQ Supervisor Training: Not required. On the welcome screen, the guide: HSPnet Overview for Preceptors shows Supervisors how to use HSPnet |
|
Link to: |
|
Return to top of | document |
<div class="pageSection group">
<div class="pageSectionHeader">
## Attachments:
</div>
<div class="greybox" align="left">

[worddav68ae31fd646ea2c673f0f78beca2b03a.png](attachments/7569897/7569896.png) (image/png)

[worddav0d75610f569cdb2bfba4c984f54c3932.png](attachments/7569897/7569898.png) (image/png)

[worddav8a5b8c990c8efc5489c4c9da98ac884b.png](attachments/7569897/7569899.png) (image/png)

[worddav69e4b4098fc3f8cbb270e9b55a6c05bb.png](attachments/7569897/7569900.png) (image/png)

[worddav5a680f96c6637a584af175cb7716811f.png](attachments/7569897/7569901.png) (image/png)

[worddav66d3b144d747fd6d11b9dc016076f30e.png](attachments/7569897/7569902.png) (image/png)

[worddav396ac28ae03c77f809f307676c696c58.png](attachments/7569897/7569903.png) (image/png)

[worddava9ad3ab61993366ec2a962fad4d0718b.png](attachments/7569897/7569904.png) (image/png)

[worddav0e1851ce23a4040d631d942159eb6841.png](attachments/7569897/7569905.png) (image/png)

[worddavf5631337314a3664ac38b5ac942e33f2.png](attachments/7569897/7569906.png) (image/png)

[worddavaeeb2cab0a1a5fe42ccc57dbf30bc0a1.png](attachments/7569897/7569907.png) (image/png)

[worddav02e3f54ca23fcbfaf8e903bd032c4792.png](attachments/7569897/7569908.png) (image/png)

[worddav4344e95901c78101def909a61fc55c17.png](attachments/7569897/7569909.png) (image/png)

[worddavf441e336701543c72e107ecd51d1a5dc.png](attachments/7569897/7569910.png) (image/png)

[worddavabb4193159d547f6551cf4678a04cff0.png](attachments/7569897/7569911.png) (image/png)

[worddav18ede675fd6282d25782242c66bf9cb6.png](attachments/7569897/7569912.png) (image/png)

[worddava3ccbb5e51be3ae8cd469e06c4f5d2f3.png](attachments/7569897/7569913.png) (image/png)

[worddave67f1a746a9283b82dfe5c4cbfbd1010.png](attachments/7569897/7569914.png) (image/png)

[worddav1a70753f63df4602219f295222063a33.png](attachments/7569897/7569915.png) (image/png)

[worddavf175a0330f554f87d7c5e51250af53fc.png](attachments/7569897/7569916.png) (image/png)

[worddav71ce830afb30ea8be41e267ea91c938c.png](attachments/7569897/7569917.png) (image/png)

[worddav1949c738255558ba4ca274850202f4c1.png](attachments/7569897/7569918.png) (image/png)

[worddav72d34b5a909306a2acab972fbb66d8c7.png](attachments/7569897/7569919.png) (image/png)

[worddav00d3d20814585c93b374b3a714a14cf1.png](attachments/7569897/7569920.png) (image/png)

[worddav91bd930c7e0a490c4cf875f0c5265d89.png](attachments/7569897/7569921.png) (image/png)

[worddav2e02b194ed19efa966b27a2ebaf5fbed.png](attachments/7569897/7569922.png) (image/png)

[worddav50a0267acb1c29cece76d7e53adf2b48.png](attachments/7569897/7569923.png) (image/png)

[worddav9c483717155d56e8f6f93574098bd41e.png](attachments/7569897/7569924.png) (image/png)

[worddav73174b10fb2a7a6e3528b9a516d960f9.png](attachments/7569897/7569925.png) (image/png)

[image2020-3-11_14-44-25.png](attachments/7569897/28805364.png) (image/png)

[image2020-3-11_12-3-14.png](attachments/7569897/28805462.png) (image/png)

[image2020-3-11_11-54-2.png](attachments/7569897/28805464.png) (image/png)

[image2020-3-11_14-26-23.png](attachments/7569897/28805465.png) (image/png)

[image2020-3-11_14-25-23.png](attachments/7569897/28805466.png) (image/png)

[image2020-3-11_14-21-31.png](attachments/7569897/28805467.png) (image/png)

[image2020-3-11_12-43-1.png](attachments/7569897/28805468.png) (image/png)

[image2020-3-11_13-11-16.png](attachments/7569897/28805469.png) (image/png)

[image2020-3-11_13-11-56.png](attachments/7569897/28805470.png) (image/png)

[image2020-3-11_13-29-31.png](attachments/7569897/28805471.png) (image/png)

[image2020-3-11_13-38-2.png](attachments/7569897/28805472.png) (image/png)

[image2020-3-11_14-19-17.png](attachments/7569897/28805473.png) (image/png)

[image2020-3-11_14-38-23.png](attachments/7569897/28805474.png) (image/png)

[image2020-3-11_14-41-50.png](attachments/7569897/28805475.png) (image/png)

[image2020-3-18_13-41-12.png](attachments/7569897/28805476.png) (image/png)

[image2020-3-11_14-45-29.png](attachments/7569897/28805477.png) (image/png)

[image2020-3-31_9-31-1.png](attachments/7569897/28805900.png) (image/png)
</div>
</div>
</div> </div>
<div id="footer" role="contentinfo">
<section class="footer-body">
Document generated by Confluence on Nov 03, 2023 15:05
<div id="footer-logo">[Atlassian](https://www.atlassian.com/)</div>
</section>
</div>
</div>