> For the complete documentation index, see [llms.txt](https://docs.cdpi.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cdpi.dev/technical-notes/digital-ids-and-electronic-registries/digital-id/capabilities-on-id-system.md).

# Capabilities on ID system

How to convert any ID system into a DPI

Building a use cases layer on top of any foundational / functional ID system is crucial for unlocking service delivery. An ID system should be considered infrastructure that provides citizens with seamless access to services.

An ID system is only as powerful as the use cases it can unlock. This is also how countries can encourage enrolment and ensure that their ID system is “sticky”.

The layers built on an identity system, as outlined below, can make an existing ID system operate as digital public infrastructure in an economy, thereby enhancing both enrolment rates and overall system utilisation.

<figure><img src="https://697430317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPSpwXyMDD6nT6RU93idI%2Fuploads%2FiFAnm6g0fekwcFEeuXZF%2FScreenshot%202023-10-11%20at%2016.44.48.png?alt=media&amp;token=111c8d73-37ec-46b7-86ca-14fddbc8d31e" alt="Capabilities built on the identity layer: Auth (verify identity online), e-sign (sign any contract or agreement online), KYC (authenticate and fetch identity profile fields), and SSO (sign into any government or private portal)."><figcaption></figcaption></figure>
