Custom templates
Last updated: 28 Jun 2026
Premium L1—fork official templates or compose new categories.
Who this is for
Premium subscribers who need bespoke asset categories—loyalty cards, hardware tokens, internal IDs—without waiting for official packs.
What you need
| Tier | Premium L1 (authoring and using custom templates) |
| Vault state | Unlocked |
| Network | Offline after the first successful app load |
| Feature toggle | None (Premium gate applies) |
Steps
Open the template author
- Unlock your vault and confirm Premium is active—see Help: Billing if controls are locked.
- Open Settings → General → Category templates (
https://se.nt2.me/settings/general/templates). - Scroll to Custom templates and select Create template (or Fork an official pack to start from its fields).
Define fields and save
- Enter a display name and slug (internal category id)—follow on-screen validation.
- Add fields from the semantic registry (text, password, URL, date, etc.) and mark required fields as needed.
- Save the template. It appears under Custom templates and in the Add asset picker.
Create items with your template
- Go to
https://se.nt2.me/assetsand select Add asset. - Pick your custom template from the list (alongside Credential, Secure Note, and enabled official packs).
- Fill fields and save—encryption and list behavior match built-in templates.
Export or delete a custom template
- Return to Settings → Category templates → Custom templates.
- Use Export to download an
.nt2tplpack for backup or another vault. - Use Delete only when no items need that category—existing items may block deletion until migrated or removed.
Tips and common mistakes
- Premium L1 required—free vaults can use official packs but not author custom templates.
- Fork vs scratch—forking copies field layout from an official template; faster than building every field manually.
- Slug stability—changing slugs after items exist can complicate sync and filters; plan names early.
- Not a blank canvas—fields come from NT²’s registry for consistent copy buttons and validation, not arbitrary HTML.
- Separate from CSV import—bulk migration uses CSV import, not custom template authoring.