Using the dashboard
Run your organization from the Developer Platform — team, users, keys, contracts, assets, and billing — without writing code.
The Developer Platform is where your team sets everything up. Anything you can do with the API, you can also do here.
API keys
Create a key for each environment, and delete any key that may have leaked.
Smart contracts
Create the on-chain collection your assets are issued from, then deploy it.
Users
Invite the people who own or approve assets. They finish setup in Confida.
Digital assets
Issue assets, choose owners, and watch approvals come in.
CRDB credits
Add free test credits or buy live credits for production.
Settings
Your organization's profile, team members, and billing mode.
A typical first week
- Create an organization for your product. It starts in managed mode, which suits most teams.
- Invite your team in Settings — owners handle billing; developers build.
- Add test credits so you can try things for free. See CRDB tokens.
- Create and deploy a smart contract on the test network.
- Invite a user — try it with your own email first — and issue an asset. Approve it in Confida to see the full experience.
When you're happy, repeat steps 3–5 on the live network. The quick start walks through each step in detail.
Managed vs. self-service organizations
Every organization is in one of two modes. The mode decides who pays for blockchain activity and which APIs you can use, so it's worth knowing which one you're in before you build. You'll see it as a badge next to the organization name throughout the dashboard.
| Managed | Self-service | |
|---|---|---|
| Badge | Gray, building icon | Blue, wallet icon |
| Who pays | The organization owner pays for every asset and transfer. Users never buy or hold CRDB. | Each user has their own wallet and buys their own CRDB. |
| APIs | Public CL2C API | CL2C API, plus the Cordoba API for owners and developers |
| How to get it | The default for every new organization | Request it when creating the organization or in Settings → Billing model. A Taliware admin approves it. |
| Best for | Most companies, B2B, and any product where you control the experience | Approved partners whose users manage their own credits |
While a request is waiting for approval you'll see an orange, dashed Self-service pending badge. Until it's approved, the organization works exactly like a managed one.
What happens on approval
A Taliware admin reviews each self-service request. When approving, they can also add starting CRDB to the organization in the same step. Those credits go to the organization owner's wallet, and the owner gets an email with the amount. Admins can also switch an organization back to managed later.
Not sure which to pick? Stay managed.
CL2C is the standard API and covers almost every product. Self-service and the Cordoba API are for approved partners with a specific need, such as their own in-app biometric approval.
Certificates of authenticity
Every asset has a printable certificate that shows what it is, who issued it, who owns it (and what share), when each owner approved, and where it's recorded on the blockchain.
- In the dashboard: open an asset's details (or its row menu) and choose Certificate.
- In Confida: owners tap Certificate of Authenticity on a minted asset.
- With the API:
GET /api/v1/cl2c/nft/{id}/certificate. Add?format=htmlto go straight to the printable page.
Each certificate has its own private link (/certificate/<token>) that can't be guessed from the asset ID. Anyone with the link can view it, so only share it with people who should see it.
Until an asset is recorded on the blockchain, its certificate is marked Provisional. Every printed copy includes a document fingerprint that changes if any detail changes, so a paper copy can always be checked against the live page.