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.

A: If someone gets assigned to a unit of work as a primary or secondary, they will then get notifications pertaining to that assignment. Supervisors also get an email once the screening has been submitted for approval. Any other noticing will have to be handled per county business processes as determined by each county whether that is by assignments within CWS-CARES or an external county business process.

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.

A: Yes, P-CIS access will be permission/role-based and controlled by counties.

A: County Administrators will not have the ability to assign enablement programs, but each user can self-enroll in any of the enablement programs.

A: No — county admins should not be making adjustments in the training environment. Training coordinators/train leads are responsible for ensuring access works as expected; if not, contact them or attend office hours. The training environment also does not use role-based access, unlike Production Simulation, so everyone has full access there to allow continuity of training.

A: Permissions would only reset with a full data load (such as a future Mock 3 load) — not with routine functionality updates. The team is researching how to preserve current Prod Sim permission sets so they can be combined with CWS/CMS permission sets at go-live, with counties verifying before the combined list is uploaded to production.

A: This is being considered as a new feature — a County Admin would be able to change another County Admin within the county, but not their own permissions.

A: It is California State policy using National Institute of Standards and Technology (NIST) 800-53 rev5 guidelines, that account usage be monitored and disable accounts where the user has not logged into the CWS-CARES system for more than 90 days. This policy helps us maintain the data integrity and security of the system. For instance, this policy helps to prevent users who may have left a department, but whose accounts might not have been disabled by that department, from logging in to the system.

The County and Office Administrator will be able to reactivate that user when their account has become disabled.

A: The CWS-CARES Project is currently finalizing its supervisor approval functionality; Currently, CANS is not accessible in a referral. The user would need to promote the referral to a case to include CANS accessibility, which an ER worker will be able to access in CWS-CARES. Including CANS accessibility in referrals will be a future development consideration.

Furthermore, cases plans can begin prior to a CANS being fully completed, but you cannot enter a case plan’s objectives with CANS being completed. This means you can document everything else such as the people involved, permanency goals, visitation plans, agency responsibilities, and Objectives for the Parent/Legal Guardian/Indian Custodian which are based on the Safety Threats identified from the Structured Decision Making (SDM) Safety Assessment. Objectives must be added for the Focus Child(ren) prior to submitting for supervisor approval, so this is the point where a user will be blocked without a CANS Assessment completed. The CANS will also need supervisor approval.