Frequently Asked Questions

User Access & Permissions

Q: What is the process to deactivate a user? Can it be done by the user themselves, or another party at the CBO, or can it only be done by a Child Welfare staff member with a CWS-CARES administrator login? What permissions does a CWS-CARES worker need to be able to add individuals to the provider portal? Will reports on logins/utilization by individuals be available, so counties can monitor users?

A: Regarding deactivation of a user in CWS-CARES, the CBO Portal Administrator will control activation and deactivation for their organization. To add and remove users, A CBO Portal Administrator permission their specific organization is required. The Project did not build native reports on data aspects such as logins and utilization by individual in CWS-CARES V1, but the data will exist within each organization’s portal and for the county Prevention Services Supervisor. County Prevention Services Supervisors will be able to monitor this data in CWS-CARES and could possibly have their own county Super Users build their own reports.
 

Q: After CWS-CARES Version 1 Go-Live, will Organizations still need to provide Object IDs to the Project, or can the county admins just update them in Okta?

A: After the CWS-CARES Version 1 Go-Live, county administrators will be onboarding users in CWS-CARES and they will add Object ID in user profile in CWS-CARES Okta.
 

Q: Once a user is deactivated in CWS-CARES, do they need a new Object ID when they are reactivated?

A: When the user is deactivated, the user profile (username, email address, first name, last name, Object ID) does not change, the profile attributes remain intact. When the user is reactivated the same user profile attributes are used.
 

Q: Can we use an Azure group or business-to-business setup to manage access more efficiently?

A: There is already an Azure group on the county-side that manages CWS-CARES access.
 

Q: Is there a better way to manage user access instead of providing individual Azure Object IDs every time someone is added or removed?

A: For integrated counties, the object ID (SSO ID) is mandatory key attribute, so during the user provisioning this attribute is required. The system also supports another flow, called Just in Time (JIT), for obtaining the object ID automatically during SSO, if the following conditions are true:

  • This is a new user and does not exist in the CWS-CARES system 
  • The user is already added to Azure security group on the county (integrated county) side
  • County administrator requests the user to login to CWS-CARES
The outcome of above actions is that the user is created/provisioned in CWS-CARES Okta with required user profile attributes including Object ID. Later the county administrator can login to CARES Okta and grant access to CARES application. Please note that the object ID is not required to remove / terminate the users.

Q: Will the Production Simulation (CARES 100) data refresh wipe any permissions CARES100 users might have changed or is it just the case data that's being wiped out and refreshed?

A: All data and permissions will be overwritten during the data refresh.
 

Q: What updates can you share regarding improvements to access and permissions in CARES?

A: The Project reports that Roles Based Access will be ready for testing during Production Simulation, the CWS-CARES Administration team is supporting user setup, and staff lists have been updated to include only active users.
 

Q: What training and preparation will county Help Desk teams receive to ensure they are ready to support users at Go‑Live?

A: County Help Desk teams will receive targeted guidance and training to ensure they are ready for Go‑Live. The project is defining clear roles for Tier 1, Tier 2, and Tier 3 support, and policies and procedures for local Tier 1 help desks are currently being developed. A new service desk vendor begins at the end of September, and counties will receive information to help them understand the transition and what support will look like during cutover and Go‑Live. The Production Simulation (Prod Sim) team will remain in place to assist throughout this period.

Counties can leverage built‑in CWS-CARES tools and ServiceNow, which will guide users through basic troubleshooting and route issues to live support when needed. Some counties will use local Tier 1 help desks, while others without local support will contact the project help desk directly.

A small SME huddle will be convened to finalize help desk procedures, and counties are invited to provide input through county leadership and CWDA to the Project.
 

Q: After Go-Live, when CWS/CMS goes into read-only mode, how do counties terminate account access for staff who are no longer with the division? County Admins will not have the ability to terminate access like before. Additionally, will the State be automatically terminating CWS/CMS access when a CWS-CARES Account is terminated? Will County Admins need to submit a ticket to the State for termination?

A: Counties will need to submit CWS/CMS Help Desk tickets to IBM to request termination of account access. County Admins will not have the ability to terminate that access like before but will be given access to weekly deactivation reports in CWS-CARES to help support this process. Please note that CWS/CMS account access will not automatically be terminated when an CWS-CARES account is terminated, so please ensure to submit a CWS/CMS ticket to IBM for CWS/CMS account access termination.

Q: Will the CWS-CARES registration process be changing post-Go-Live? How will this look for new employees coming post-Go-Live?

A: After Go-Live, County Admins are responsible for creating new user accounts and assigning permissions in the Admin Console for any staff who join the department post–Go-Live.