# Quick Start

### Understanding the Components

#### 1. OCID Connect

OCID Connect is an authentication protocol that allows users to sign in to third-party applications using their OpenCampus identity. It works similarly to other popular single sign-on (SSO) methods like "Login with Google" or "Login with Twitter”

<figure><img src="/files/0zK8KyxjP6lHbPLtLwSI" alt=""><figcaption><p>OCID Connect UI</p></figcaption></figure>

You can find out more about OCID connect in a separate section [here](/start-building/open-campus-id-connect-sdk.md)

#### 2. Open Campus Achievements (OCAs)

**Open Campus Achievements (OCAs)** are **verifiable digital credentials** that represent a learner’s formal accomplishments. They are built on the **W3C Verifiable Credentials** and **Open Badges 3.0** standards, ensuring that they are portable, tamper-proof, and interoperable across platforms.

OCAs are typically used for **structured, formal recognitions**, such as:

* Course completions
* Professional certifications
* Licenses or qualifications
* Assessments or skill validations

Each OCA includes:

* **Metadata**: Name, identifier, description, and achievement type
* **Issuer details**: The institution or developer who granted it
* **Holder identity**: The recipient’s Open Campus ID (OCID)
* **Credential visuals**: Logo of the issuing institution and an achievement image (certificate or badge visual)

When issued, an OCA becomes part of the learner’s **Open Campus profile** and can be shared or verified by third parties without relying on a central authority.

<figure><img src="/files/0SioAfhzmHvT9MMS31wK" alt=""><figcaption><p>Sample OCA</p></figcaption></figure>

#### 3. Open Campus Badges

**Open Campus Badges (OCBs)** are **lightweight digital recognitions** designed for flexibility, engagement, and gamification. Like OCAs, they follow the **Open Badges 3.0** and **W3C Verifiable Credentials** standards, making them secure and verifiable — but they’re often used for **informal or community-driven recognition**.

OCBs are well-suited for:

* Community participation (e.g., attending an event, joining a program)
* Milestones (e.g., completing a challenge, reaching a streak)
* Skill highlights (e.g., contributing to a project, demonstrating teamwork)
* Engagement rewards (e.g., gamified achievements within a platform)

Each OCB includes:

* **Metadata**: Badge name, description, and achievement type
* **Issuer details**: The organization or community that granted it
* **Holder identity**: Typically tied to an **Open Campus ID (OCID)**, but can also be issued **directly to a wallet address** when `collectionSymbol = ocbadge`
* **Badge visual**: A custom image that represents the recognition

Badges are ideal for **driving participation and motivation** within learning or community ecosystems, while still maintaining interoperability and verification standards.

#### 4. Open Campus ID Dashboard

The **OCID Dashboard** is the learner’s control center for their **Open Campus ID (OCID)**. It provides a personal profile where holders can view, manage, and share all the credentials they’ve earned — whether Achievements (OCAs) or Badges (OCBs).

Key functions include:

* Viewing issued credentials in one place
* Sharing credentials externally for verification
* Managing linked wallets and identities

The OCID Dashboard ensures that learners always have **full visibility and ownership** over their verifiable credentials.

<figure><img src="/files/q6NfUsPuJzQwSw3NhQen" alt=""><figcaption><p>OCA Dashboard</p></figcaption></figure>

#### 5. Open Campus Developer Portal

The **Open Campus Developer Portal** is the central hub for issuers and developers to integrate with the Open Campus ecosystem. It provides all the tools needed to issue, manage, and track digital credentials at scale.

Key features include:

* **API Key Generation** – Obtain staging and production keys for secure credential issuance.
*

```
<figure><img src="/files/z4ao8ZHUzXBFA9MpBNtA" alt=""><figcaption></figcaption></figure>
```

* **Credential Issuance** – Issue Achievements (OCAs) or Badges (OCBs) directly from the portal.

  * **Single issuance**: Quickly issue one credential to a learner.
  * **Bulk issuance**: Upload a CSV file to issue credentials to multiple learners at once.

  <figure><img src="/files/g6bIaH0ZzndXy9hr239y" alt=""><figcaption></figcaption></figure>
* **Credential Management** – Take direct actions on issued credentials, including:

  * **Revoking credentials** when they are no longer valid
  * **Viewing issuance history** for audit and verification
  * **Tracking credential status** across holders

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

With these tools, issuers can handle both **individual recognitions** and **large-scale credential distribution**, while maintaining full control over the lifecycle of every credential.


---

# Agent Instructions: 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:

```
GET https://devdocs.educhain.xyz/start-building/open-campus-achievements-badges/quick-start.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.