> For the complete documentation index, see [llms.txt](https://docs.sunbirdrc.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sunbirdrc.dev/~/changes/ZV4lFZMKighmbjr9sJml/learn/core-capabilities.md).

# Core Capabilities

<figure><img src="/files/yW7d5rxWqIjEl0sRA9zC" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/XgiRk7vvEa0iu0zEVi64" alt=""><figcaption></figcaption></figure>

## Registry

A governing body/authority would be able to build registry that acts as a single source of truth

1. Define Schema as per policy:
   * Define field and field types
   * Field level privacy: Able to define visibility of who can view the content at field level
   * Consent framework at schema level
2. Create entities:
   * Able to Bulk invite users via CSV
   * Able to link to external systems
   * Able to self-register
   * Able to decide visibility of who can view the content at field level
3. Define Ownership
   * Able to define which entities can login & how is authorisation handled
4. Discovery: Able to define discovery attributes that are public, private or consent based
5. Analytics: Basic Analytics for Registries

## Verifiable Credentials (VC)

1. Define Attestation and Claim Workflow: Tenants can define the 'add on' workflow
   * Able to configure how claims will be approved (Auto or Manual)
   * Using Internal (Sunbird RC system) or Connecting to external systems
   * Able to create multi-level attestation for claim
   * Define Validity
2. Consent:
   * Grant or Revoke Consent: Able to receive consent requests to grant or revoke the consent access.
   * Consent Auditing
3. Issuance services:
   1. W3C compliant&#x20;
   2. Create and Issue Verifiable Credentials
   3. Updation and Revocation
4. Unique ID generation

## VC Verification

1. Offline verification of Verifiable Credentials: [Reference SDK](https://docs.sunbirdrc.dev/vc-verification-module)
2. Consent based access: Able to provide consent to another system/person to access Verifiable Credentials for the purpose of transaction/interaction

## Digital Wallet

Citizen (credential owners/holders) can access Verifiable Credentials anytime anywhere.

1. Fetch and store personal verifiable credentials
2. Consent based sharing of verifiable credentials


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sunbirdrc.dev/~/changes/ZV4lFZMKighmbjr9sJml/learn/core-capabilities.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.