How is CDP Different from Corppass Agency Admin (AA) Portal?

Last updated 3 months ago

Partners can now manage their own access to CDP independently, eliminating the need to wait for Corppass team to create or manage Agency Admin accounts.
- Once authorised, access rights are granted to all digital services tagged to a user's organisation/agency, unlike Agency Admin Portal which granted access at a per digital service level.
Different role types on CDP allow varying level of permissions to users. Visit for more details on what access rights each role has.
- Notably, users assigned with the Admin role in CDP can view and edit all digital service(s) tagged to their organisations/agencies.

Activating/publishing a service in the Staging environment will not require any approval.
However when you activate/publish a digital service in the Production environment for the first time, this will trigger a review of your service by GovTech-authorised personnel.
- You are no longer required to upload an approval email, as having a Corppass account with the 'Admin' role for the 'Corppass Developer Portal' (CDP) service confirms your prior authorisation to onboard and publish a service.
(no change) You may deactivate your active digital services on CDP (no approval process).

Since deletion of a service is an irreversible action, we are no longer availing this as a self-serve feature to avoid unintended consequences. Partners are to raise a service request through the .

In CDP's current state, roles and parameters cannot be changed / added after a service is published for the first time. In particular,
1. Entity types and/or statuses - can be added, but cannot be removed
2. Sub-UEN settings - cannot be changed
3. Roles and parameters - cannot be added or removed
The following operations can be done on the Agency Admin portal, if needed:
1. Add role
2. Delete role (NOTE: this is a destructive action and will irreversibly remove all existing user assignments with that deleted role which Corppass Admins of various entities have authorised to your service previously. Corppass does not send out notifications to the affected users or Corppass Admins for such changes.)
3. Add Parameter
  1. Any parameters added after service has been published should be marked as optional.
  2. Whilst allowed, adding new mandatory parameters after your service has been published may cause existing authorisations to fail on your end (especially if you're enforcing checks on the payload that Corppass returns to you), and is not recommended.

Last updated 3 months ago

Partners can now manage their own access to CDP independently, eliminating the need to wait for Corppass team to create or manage Agency Admin accounts.
- Once authorised, access rights are granted to all digital services tagged to a user's organisation/agency, unlike Agency Admin Portal which granted access at a per digital service level.
Different role types on CDP allow varying level of permissions to users. Visit for more details on what access rights each role has.
- Notably, users assigned with the Admin role in CDP can view and edit all digital service(s) tagged to their organisations/agencies.

Activating/publishing a service in the Staging environment will not require any approval.
However when you activate/publish a digital service in the Production environment for the first time, this will trigger a review of your service by GovTech-authorised personnel.
- You are no longer required to upload an approval email, as having a Corppass account with the 'Admin' role for the 'Corppass Developer Portal' (CDP) service confirms your prior authorisation to onboard and publish a service.
(no change) You may deactivate your active digital services on CDP (no approval process).

Since deletion of a service is an irreversible action, we are no longer availing this as a self-serve feature to avoid unintended consequences. Partners are to raise a service request through the .

In CDP's current state, roles and parameters cannot be changed / added after a service is published for the first time. In particular,
1. Entity types and/or statuses - can be added, but cannot be removed
2. Sub-UEN settings - cannot be changed
3. Roles and parameters - cannot be added or removed
The following operations can be done on the Agency Admin portal, if needed:
1. Add role
2. Delete role (NOTE: this is a destructive action and will irreversibly remove all existing user assignments with that deleted role which Corppass Admins of various entities have authorised to your service previously. Corppass does not send out notifications to the affected users or Corppass Admins for such changes.)
3. Add Parameter
  1. Any parameters added after service has been published should be marked as optional.
  2. Whilst allowed, adding new mandatory parameters after your service has been published may cause existing authorisations to fail on your end (especially if you're enforcing checks on the payload that Corppass returns to you), and is not recommended.