Pro templates and blocks install the same way as free components: the shadcn CLI copies their source into your project. The only difference is that the Pro registry asks for your licence key.
Your licence key is in the email you get after checkout (check spam if it is missing). The key is also your login: paste it on /pro/login and your Pro library opens with the exact configuration for your project. Logging in also unlocks the Code panel on every Pro template and block page in that browser. The key is kept in a secure cookie, and you can log out from the library at any time.
Put the key in .env.local (or your shell environment). Keep it out of
version control.
TEALMAC_UI_LICENSE_KEY=your-licence-keyAdd the Pro namespace to components.json. The CLI replaces
${TEALMAC_UI_LICENSE_KEY} with the value from your environment, so the key never
appears in the file.
The snippet shown in your Pro library is generated from the live configuration; if it differs from the one above, use that one.
Use the name shown on the template or block page.
pnpm dlx shadcn@latest add @tealmac-pro/dashboard
Templates install their components into their own folder under components/
and add a ready-to-run page at app/templates/<name>/page.tsx. Any free
components they use are installed with them.
Use Pro in as many personal and client projects as you like, and get every update for life. You can't resell or redistribute the Pro source as a kit, template or library. The Pro licence has the full terms in plain English.
Add the key as a secret only if your pipeline runs shadcn add. Built apps
never need the key at runtime, and it must never be shipped in client-side
code.
.env.local you run the CLI from, and that the
headers entry is in components.json.