Frequently Asked Questions

Admin Services

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: Once CWS-CARES is live, will county CWS-CARES Admins be able to reactivate users that are deactivated if they do not login within 90 days or will they need to continue to request support from the CWS-CARES Service Desk?

A: Once CWS-CARES is live, County/Office Admins will have the ability to reactivate users from the Okta Admin Console if they are deactivated. Admins will be able to run a CWS-CARES report called "Worker Permissions | Last Login" to identify users who are close to 90-days without activity in CWS-CARES. The report is currently in both CARES100 and CARES104 for testing.

Q: Can dedicated counties receive some sort of guides or direction on how we will handle user management? With three different systems at play here having some official guidance on the process will help to prepare better. Everything from requesting a new user, closing out a new user, and disabling access. The CWS-CARES team is not responsible for all three (Windows Active Directory, Okta/Zscaler, Okta/CARES) but they all play into the same pot to get users up and running.

A: There will be a dedicated county administrator for dedicated counties from their county who will have privileges to create, update, grant access and suspend their county-specific users in the CWS-CARES application. The county administrator also has the option to suspend users if the user does not need access to the CWS-CARES application. The suspended user will be automatically deactivated after 90 days of last successful login. Regarding deleting users, as a best practice and aligning with the retention policy, users are never deleted from the system. They are transitioned into a deactivated status and maintained in the system. Processes regarding user management such as enhancements to streamline onboarding including the Zscaler + SPOC alignment continue to be a work in progress and updates provided by the Project will be communicated out as information becomes available. If County Administrators have questions or issues about user management in Okta/CWS-CARES, then they can come to the Production Simulation Support office hours. For more information and resources on the County Admin and deactivation processes, please refer to the user onboarding video on the IP Quick Access CWS-CARES V1 webpage. Additionally, there are guides on user management for County admins that are available on the System Updates & Release Notes | Child Welfare Digital Services webpage.
 

Q: Will counties receive JIRA access for bug tracking?

A: Counties receiving JIRA access is not currently on the roadmap due to the licensing structure. However, counties can request an update on JIRA tickets through the CWS-CARES Go-Live help desk.
 

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.