User Management

Managing your organization members application access within CareSuite

Once an organization member has successfully onboarded, by completing the steps as outlined in "Onboarding into CareSuite" the members application access can then be configured in CS Admin.

Setting Individual member access:

1. Login to CS Admin (USA) CS Admin (CANADA)

2. From the upper right hand corner menu, select Team Access

3. Search the individual by name or email

   • If the user does not appear, return to your organization in Nexus ID by clicking on the button to confirm their status is "Joined at"

4. Once you have sight of the member, click the button next to their name.

5. Select the members role for the application(s) they require access to and click Save

   • Keep in mind:

     • If the member does not require access to an application do not provide them a role

     • General users in caresuite do not require admin access within an applications. Admin roles should be preserved for the sys admin of your organization

   • Breakdown of Roles:

     • Admin

       • No Access

     • Contact

       • Contact Agent- A user that can access and use the application.

       • Contact Admin- A user that can use, configure, and send blast notifications to users within the application.

       • Test Role - Mirrors agenct role (Useful for admin user testing)

     • Resource

       • Superadmin- A user who can read and write all resource information, and configure the application (attributes, groups, service areas, service conditons, funding sources, taxonomy)

       • Writer- A user who can see (read) and edit (write) all resource information.

       • Reader- A user who can see (read) all resource information, but not edit it.

       • Administrator- Same permissions as super admin (Deprecated, do not use)

       • Agency Admin- Same permissions as super admin (Deprecated, do not use)

       • Agency Writer- Can see the amount of resources available at all levels (no access), cannot alter/access any information in the system. (Deprecated, do not use)

     • Care

       • User- A user that can access the application, when onboarded and granted a role, within network project(s)

       • Admin-A user who can read and write all network and project configurations, global roles, and blast notifictions.

     • Provider Portal

       • User- A service provider that can submit an annual and/or interim update to the resource database curation team.

       • Admin- An admin in CS Resource who can initiate a service request to providers.

     • Client Portal (This app is currently in development)

       • User- General user

       • Admin- Admin role

Setting member access in bulk:

1. Follow steps 1-2 as listed above.

2. Select the checkbox next to the user name to individual select the members you will be setting/ updating app permissions for.

   • If there is a shared commonality between the users you are bulk updating you can also search by this. I.E. A shared email domain, for ex. @agencyxyz.com

3. Click the button

4. Check the select butto next to the applciation yo uawill be granting member access to

5. Select the members role for the application(s) they require access to and click Save

   • Keep in Mind:

     • When bulk updating, you can only select one role per application for all.