A: Yes, multiple permissions can be assigned to one user.

A: CWS-CARES will allow you to create a user who is clerical by your definition, and you can give permission sets for them to do their job. For example, clerical in one county might allow for access to case management, eligibility and adoptions but in another county it's only for case management.

A: Yes, the Project has developed a user manual of definitions on permissions and privileges and it will be included with the training materials.

A: No, not necessarily. Only in some parts of the system will a user who was previously a Regional Administrator or Director then be a worker in CWS-CARES.

A: No, CWS-CARES does not have that option. During the first phase of testing, administrators will be configuring their offices, units, etc. and will see how the structure is set up. Then, when your actual users are in the system, you'll have a chance to pair up with them and see how the changes you make as an administrator affects their permissions in the system.

A: Counties will maintain records for service providers, law enforcement agencies, county superior courts, district attorney offices, county offices, and adoption agencies, with much of this information being converted from CWS/CMS. The California Department of Education (CDE) will maintain education provider records, the Department of Developmental Services (DDS) will maintain information for regional centers, and Community Care Licensing (CCL) will maintain records for licensed facilities such as FFAs, STRTPs, and TTHPs.

A: After Go-Live County Admins will have permissions to add/update/inactivate users. The CWS-CARES Okta Team is currently working through an integration process to connect CWS-CARES Okta to the organization's security process. [Riverside has completed the integration process] For organizations that participate in integration their users will experience a single sign on experience that is managed on the organization side through their administrative processes.

A: An inactive account is not end-dated; accounts are only end-dated when access is truly being terminated (for example, when an employee is separated, resigns, or retires). An inactive account will be disabled in Okta, and the user will need to contact their County Administrator to re-enable it. Data in CWS-CARES associated with the user will remain unchanged, and the user's supervisor is responsible for any units of work associated with the user while the account is disabled.

A: CWS/CMS permission sets will be the source of truth for Production Simulation and production Go-Live. All permissions from CWS/CMS will be mapped to CWS-CARES permissions. There are also new CWS-CARES permissions that will require County Administrator input on who should have them; these can be added by an administrator during Production Simulation for testing and research purposes. For Go-Live, CWS/CMS permissions will again be pulled and mapped to production. The Project also plans to provide counties a report of all new CWS-CARES permissions assigned in Production Simulation for review.

A: Yes. Service desk/help desk personnel have role-specific On-Demand courses. The recommended audience in the Instructional Design Maps indicates the ILT courses the CWS-CARES Team feels would support this group of people the best. However, you may choose to assign ILT courses that do not indicate service/help desk personnel as the target audience if you feel the content covered aligns with the tasks performed by the individual.