Collections

Access prerequisites

• Permission (module): manageToken
• License/Feature: MANAGE_NFTS
• Menu container: TOKENIZATION → group Tokenization → Collections

What it is / when to use

Collections group NFTs by theme/offering and carry the shared on-chain configuration: network, contract and — when applicable — the regulated contract standard (ERC-3643 / ERC-721-compliant). Every NFT belongs to a collection, so the collection must exist before creating the NFT.

The choice of contract standard (regulated or not) is resolved per collection, normally at the close of a crowdfunding, and is stored in contract_standard.

Prerequisites

• Permission: manageToken (dual — CPM enum + module in DB).
• License/Feature: MANAGE_NFTS.
• Dependencies: networks (network_id) registered.

Step by step (listing)

1. Go to Tokenization → Collections.
2. Search by name and filter by network.
3. Edit, view, or delete (collections with items cannot be deleted).
4. Create collection to open the form.

Filters and columns

Filter / Column	What it shows	Data source
Search by name	Filters by name (server-side, paginated, debounce)	getCollections({ name, networkId, limit, offset })
Network	Filters by networkId	getNetworks()
Name / Items / Network	Identification, number of NFTs and blockchain	TokenController (collections)

Form fields

Field	What it is	Required?	System/backend effect
Name	Collection name	Yes	name. Not modifiable after creation (tooltip "cannot modify"). Format validation (collectionNameValidator).
Network	Blockchain of the collection	Yes	network_id. Not modifiable after creation. Defines where the contract is deployed.
Description	Description (up to 1500 characters)	Yes	description.
Image	Collection logo	Yes	photo.
Cover image	Banner	No	cover_photo.
Price	Reference price	No	price (BigNumber) + priceCurrency.
Whitepaper (URL)	Whitepaper link	No	whitepaper_url.
Creating institution	Name/URL of creator	No	creator_institution / creator_institution_url.
Legal document (PDF)	Legal documentation	No	document_url (upload, max 10 MB).
Contract document (PDF)	Attached contract	No	contract_url (upload).
Show disclaimer	Shows warning on the collection	No	show_disclaimer.
Contract address	On-chain contract	Automatic	contract_address — filled by the platform after on-chain processing (displayed as "processing" until confirmed).

Contract standard and Regulation panel

The contract_standard field defines the collection's contract type:

• ERC721 (default) — unregulated NFT;
• ERC721_COMPLIANT — regulated NFT (on-chain identity via shared IdentityRegistry);
• ERC3643 — regulated fungible security token.

For regulated collections, the form (edit/view modes) displays the Regulation panel (app-regulated-admin), auto-hidden when the collection is not regulated. This panel allows the following actions on the token/holder:

Action	What it does
Pause / Unpause	Pauses transfers of the regulated token.
Freeze / Unfreeze (per wallet)	Freezes a specific wallet.
Forced transfer	Forced transfer from → to → value (value = tokenId for NFT-compliant, or amount for fungible).
Recover	Recovery oldWallet → newWallet via ONCHAINID (tokenId only for NFT).
Holders list	Table with real holders of the collection (freeze/recover/forced per row).

Investor identity actions (status/retry/revoke) are located on the User Details screen, not here.

Actions and modals

• Create / Save: confirmation modal (bottom sheet). Creates (createCollection) or updates (updateCollections).
• Delete: only allowed if the collection has no items; requires confirmation. Otherwise, blocked with a warning.
• Regulation actions: trigger step-up (password+MFA re-authentication, header X-Step-Up-Token) for destructive operations (forced-transfer, recover, freeze).

Business rules / cautions

Attention

• Name and network are immutable after the collection is created.
• A collection with NFTs cannot be deleted — empty/close it first.
• The contract address is generated by the platform; wait for on-chain processing.

Irreversible

• Regulated operations of forced transfer, recover, and identity revoke change on-chain ownership and have no rollback. They require step-up (password+MFA).

• Financial values: price is BigNumber, without rounding.

Examples

Scenario 1 — Standard (unregulated) collection for collectible NFTs

1. Name "Arte Axia", network POLYGON, description, image and cover.
2. Save — contract_standard remains ERC721.
3. The collection is ready to receive NFTs in Manage NFTs.

Scenario 2 — Regulated collection (security token) for crowdfunding

1. The collection is born regulated when the corresponding crowdfunding is marked as regulated — at closing, contract_standard is resolved to ERC721_COMPLIANT (NFT) or ERC3643 (fungible).
2. When editing/viewing the collection, the Regulation panel appears with IdentityRegistry/compliance and pause/freeze/forced/recover actions.
3. Transfers now require investors with verified identity (on-chain KYC provisioned lazily).

Related screens

• NFT Management
• NFT Category
• NFT Burn