Corppass
  • INTRODUCTION
    • About Corppass
    • Corppass Design Guidelines
      • Brand Guidelines
      • Button Guidelines
  • Technical Specifications
    • Corppass Authorization API
      • Key concepts
        • Client JWKS
        • JWS and JWE
        • Client Assertion JWT
        • Proof Key of Code Exchange (PKCE)
      • Staging and Production URLs
      • Well-known Endpoints
        • OpenID Discovery Endpoint
        • JWKS Endpoint
      • Scopes
      • Authorization Endpoint
        • Authorization Code with Proof Key of Code Exchange (PKCE) Flow
        • Pushed Authorization Request (PAR) Flow
      • Token Endpoint
        • ID Token Structure
          • UserInfo Claim Structure
          • EntityInfo Claim Structure
        • Access Token Structure
      • Authorization Info Endpoint
        • AuthInfo Structure
        • TPAuthInfo Structure
      • Pushed Authorization Request (PAR) Endpoint
  • Corppass Developer Portal (CDP)
    • User Guide
      • Getting Started
      • Login to CDP
      • Available Digital Service Settings
        • FAQs
      • Toggle Between Staging and Production Environments
      • Portal Features
        • Updating the Digital Service and Managing Metadata
      • User Roles and Permissions
      • Frequently Asked Questions (FAQ)
        • Login Issues
        • Access and Permissions
        • How is CDP Different from Corppass Agency Admin (AA) Portal?
        • Other Common Issues
  • MORE INFORMATION
    • Is Corppass working?
    • Contact Us
Powered by GitBook
On this page
  1. Corppass Developer Portal (CDP)
  2. User Guide

User Roles and Permissions

This page provides an overview of the roles available in the Corppass Developer Portal (CDP) and the associated permissions for each role.

Role Definition in CDP

All authorised users to CDP will have 'View' access to all the digital services under their entity.

  1. Admin User*:

    • Full permissions to read and modify all staging and production digital services within the entity.

    • This role is suitable for users responsible for end-to-end management of digital services.

  2. Staging Admin User:

    • Allowed to view both staging and production digital services.

    • Can only modify staging digital services under the entity.

    • Ideal for users handling testing or pre-production environments.

  3. Read Only User:

    • Restricted to view-only access for digital services registered under the entity.

    • Cannot modify any digital services settings.

    • Suitable for users who need visibility but do not require editing permissions.

*This is the CDP Admin role, not to be confused with "Corppass Admin".

The table below gives an overview of the differences in access rights for roles on CDP.

Roles
Description
Modify STG
Modify PRD

Admin User

This user role will be able to view and modify the digital services within their agency.

Y

Y

Staging Admin User

This user role will be able to view the digital services in their agency across STG and PRD but can modify them only in STG.

Y

N

Read Only User

This user role can only view the digital services in both STG and PRD for their agency.

N

N

PreviousUpdating the Digital Service and Managing MetadataNextFrequently Asked Questions (FAQ)

Last updated 3 months ago