Crowdmuse Whitepaper
  • Overview
    • What is Crowdmuse?
  • Background
    • Complex Challenges
    • Networked Solutions
  • Crowdmuse Protocol v1
    • Summary
    • Features
      • Multiplayer Products
      • Coordination Marketplace
      • Creator Profiles
      • Co-ownership Models
    • Use Cases
      • Fashion
      • Media & Film
      • Crafts
      • Experiences
      • Other Experiments
    • Architecture
      • Product Contract
      • Profiles and Licensing
      • Programmable Treasury
      • IP Management
      • Joint Venture Contract
      • Impact Certification
    • Organization
      • Team
      • Structure & Roles
      • Tokenomics
        • Page 1
        • Valuation & Token Price
      • Legal
        • Contribution Agreement
        • Legal Co-ownership
        • Collective IP
  • User Guides
    • Creators
      • Create Profile
      • Create Artifact
      • License Artifact
      • Contribute to Product
      • Receive Royalties
    • Brands / Product Owners
      • Create Profile
      • Create Product
      • Propose Product
      • Approve Creators
      • Distribute Funds
  • Links
    • Twitter
    • Website
    • Mirror
Powered by GitBook
On this page
  1. Crowdmuse Protocol v1

Organization

GitBook tip: your product docs aren't just a reference of all your features, use them to encourage folks to perform certain actions and discover the value in your product.

Permission levels

There are 4 types of permission levels in the product.

Role
Capabilities

Administrator

Has all admin privileges

Editor

Can edit posts

Viewer

Can only view posts

Guest

Can only view posts they are inivted to

PreviousImpact CertificationNextTeam

Last updated 1 year ago