Cobo WaaS Role Permission Adjustment Notice

Dear Cobo Users,

To further enhance the security and flexibility of organization-level permission management, we will optimize the role permissions in Portal on July 2, 2026. This update will introduce a new Developer role, adjust the permissions assigned to roles such as Viewer, and consolidate certain Compliance-related viewing permissions under the Compliance Officer role.

Changes
- New Developer Role
Developer-related read-only permissions, including API Key, API Logs, Developer Console, Webhook/Callback, and related features, will be managed under the new Developer role.

- Compliance Permission Adjustment
Viewing permissions for KYT/KYA Screening results and Compliance Screening will be retained only for the Compliance Officer role. Other roles will no longer have access to these permissions.

- Viewer Role Adjustment
The Viewer role will no longer include the above developer-related and compliance-related viewing permissions. All other Viewer permissions will remain unchanged.

Impact
- Existing Organizations
During the migration, the system will automatically assign the Developer role to organization members and API Keys to ensure that developer-related viewing permissions are not affected.
If any non-Compliance Officer members in your organization currently need to view KYT/KYA or Screening results, they will no longer be able to access them after the migration. Please ask an organization administrator to grant them the Compliance Officer role if needed.

⭐️ Friendly Reminder：
Please check whether members who need to view KYT/KYA or Screening results have been assigned the Compliance Officer role.
For newly created organizations, please assign the Developer role to relevant members if they need to access the Developer Console.

For more information, please refer to the official documentation
If you have any questions, please feel free to contact us.

Cobo Support
July 1, 2026