Permission System
The permission system is foundational for Webify community assets and content monetization.
Webify communities include open content, internal content, paid content, VIP content, NFT-gated content, and token-gated content. A clear permission model enables flexible operations across user tiers.
Content Permissions
| Permission Type | Description |
|---|---|
| Public | Accessible to everyone |
| Community-only | Accessible to joined members |
| One-time payment | Accessible after single purchase |
| Monthly subscription | Accessible after active subscription |
| VIP-only | Accessible to VIP members |
| NFT-holder only | Accessible to designated NFT holders |
| Token-holder only | Accessible to designated token holders or thresholds |
| Admin-only | Accessible to owner/admin/moderator only |
These permission types can apply to articles, columns, posts, knowledge-base entries, chat, and channels.
Community Join Permissions
Communities can define join conditions:
- Free join
- Paid join
- Invite-only join
- Membership NFT required
- VIP NFT required
- Designated token holdings required
- Reputation threshold required
Different communities can choose different strategies.
Channel Permissions
Each channel can have independent access policy. Examples:
- Announcement channel: public view, admin-only posting
- Discussion channel: community member posting
- VIP channel: VIP or designated NFT holders only
- Governance channel: token holders/core contributors only
- Admin channel: owner/admin/moderator only
This allows one community to serve public users, members, paid users, and core contributors at the same time.
Asset-Bound Permissions
Permissions can be bound directly to on-chain assets. For example:
Member NFTrequired for internal sectionsVIP NFTrequired for VIP chat access- Reputation NFT required for moderator application
- Project token required for governance voting
This connects identity, assets, and product capabilities in one coherent model.