Permissions
Every NFT Marketplace permission key, which admin screen it opens, and what a user can do without it.
1 min readUpdated 3 August 2026permissions, roles, admin
Permission keys follow the platform convention: the admin path with / as .
and - as _. Granting access.nft.admin opens the console; every screen
inside it still checks its own key.
Access
| Key | Opens |
|---|---|
access.nft |
The addon at all. Without it nothing under NFT is reachable. |
access.nft.admin |
The admin console. |
access.nft.marketplace |
Marketplace management. |
access.nft.settings |
The settings screen. |
access.nft.dispute |
The dispute queue. |
Read
| Key | Covers |
|---|---|
view.nft |
The dashboard and general records. |
view.nft.collection |
Collections. |
view.nft.token |
Individual tokens. |
view.nft.listing |
Active listings. |
view.nft.auction |
Auctions and their bids. |
view.nft.offer |
Offers made on tokens. |
view.nft.sale |
Completed sales. |
view.nft.creator |
Creator accounts and their onboarding state. |
view.nft.category |
Categories. |
view.nft.backup |
Backup records. |
Write
| Key | Allows |
|---|---|
edit.nft |
General edits. |
edit.nft.collection |
Changing a collection. |
edit.nft.marketplace |
Marketplace-level changes. |
edit.nft.dispute |
Resolving a dispute — this is the one that moves an asset. |
create.nft.category / edit.nft.category / delete.nft.category |
Category management. |
delete.nft |
Deleting records. |
delete.nft.collection |
Removing a collection. |
manage.nft.backup / delete.nft.backup |
Backup operations. |
edit.nft.dispute lets an admin settle a contested trade. Grant it to the same
people you would trust with a withdrawal approval, not to everyone with
access.nft.admin.
Nothing here affects what a normal customer can do — buying, listing and bidding are gated by ownership and, where enabled, KYC. These keys only control the admin side.
See Roles and permissions for how keys are assigned to roles.