At least one Super Compliance Officer (SCO) must be active in a Symphony instance at any point in time, but it is best practice to assign a minimum of two SCO as soon as an organization begins using Symphony.
Should the last SCO account be selected for deactivation, Symphony will return an error preventing this. Therefore, it will be necessary to assign a second SCO account before deactivating the original account.
To recover an SCO account without access to the original SCO account itself, several options are available:
Administrator update
Depending on the compliance restrictions in place, a Symphony Admin could update the existing SCO account with the details of another user.
- In Symphony, select the Settings icon.
- Select Admin Portal. This option is only available if you're a designated Administrator with Admin Portal access.
- Select Begin Session.
Note: Session Objective and Comments are optional fields and are not required to access the Admin Portal.
- Search for the SCO account.
- Update the email address with the credentials of a different, already existing user.
- Select Save.
- Complete the password reset process for the SCO account.
- Log in as the SCO using the credentials from step 5.
- Identify another user to receive the SCO role and update their profile to ensure there are two SCO roles active in the pod.
API update
If your firm uses Symphony APIs and has a bot account with the USER_PROVISIONING role, this account can be utilized to provision a new SCO. You can add roles to user accounts using the Add Role endpoint.
If neither of these options work and you are still unable to recover the SCO account, please contact the Symphony Support team at support@symphony.com and inform them that you are experiencing issues with recovering an SCO account.