Create a user template that includes Service Providers and Rights, to speed up user creation.

The Problem

• User have a set of rights at each Service Provider (this is not the problem)

• Each user account needs to be configured individually, even when it should be identical to that of a co-worker. A user could have 10 different sets of rights at 10 Service Providers

• It’s time-consuming and confusing to set up user accounts and mistakes often happen

• For the following two example users, an administrator would need to manually go through and define rights at Shelter A, then define rights at Shelter B, then define rights at Shelter C, etc.

Example User: Secondary Rights Steve

Let’s imagine Steve works at Shelter A. He logs in at Shelter A but also needs some access to data belonging to Shelters B and C. In order to achieve that, he needs to be granted access to 3 Service Providers and be configured with different rights at each.

• Shelter A: General shelter staff rights

• Shelter B: No ability to log on, but can read case files and VI-SPDATs belonging to this agency

• Shelter C: No ability to log on, but can read VI-SPDATs completed here

Example User: Manager Madeline

Let’s imagine Madeline is a manager at Shelter A. Because the shelters in her community work together very closely, all shelters have agreed that managers can ban staff from the other shelters in exceptional circumstances, and communicate important notices with each other.

• Shelter A: General shelter manager rights

• Shelter B, C, and D: Can create Service Restrictions and Bulletins

The Proposed Solution

• Allow administrators to define a user template, which is a combination of Service Providers and the Rights for each Service Provider, and/or

• Give administrators the ability to clone an existing user (copy Roles, Service Providers, and Rights)

The Advantages of this Solution

• User accounts are set up without error (less troubleshooting)

• Increased user acceptance by new users (no more “I can’t do X that my co-worker can”)

• Reduced administrative burden to administrators (faster to set up accounts)

• Because it would be easier, communities may be more willing to customize data sharing to suit their needs instead of coming up with workarounds (i.e. through reporting)