Hats Protocol Docs
hatsprotocol.xyzGithub
  • ๐Ÿ‘‹Welcome to Hats Protocol
  • ๐ŸงขGetting Started with Hats
  • โญQuick Start
  • Using The Hats App
    • ๐Ÿค Essentials For Hat Wearers
    • ๐ŸŽฉCreating My First Hat
    • ๐Ÿง™Admins: Creating, Issuing, and Revising Hats
    • ๐Ÿ‘ฅWhat Hats Do I Need?
    • ๐ŸŒณDrafting, Exporting, and Deploying Tree Changes
    • ๐Ÿ—๏ธSetting a Hat's Basic Properties
    • ๐ŸฅณAdding Wearers
    • ๐Ÿ”Connecting Hats w/ Permissions & Authorities
      • Types of Hat-Powered Authorities
      • Connecting Hats to Token Gates
        • Hats Protocol Contract Addresses
        • Finding a Hat's Token ID
      • Documenting Hat Powers & Responsibilities
    • ๐ŸŒŸRevocation & Eligibility: Requirements for Wearers
    • โšกDeactivating & Reactivating Hats
    • โœ…Making Hats Claimable
    • ๐Ÿ”—Linking Trees Together
    • โ›“๏ธHats Protocol Supported Chains
    • โ“Glossary & FAQ
  • Hats Integrations
    • ๐Ÿ”Permissions & Authorities
      • Coordinape
      • Council Voting Vault
      • Charmverse
      • Discord
        • Collab.Land --> Discord
        • Guild.xyz --> Discord
      • Farcaster Casting Rights
      • Fileverse
      • Google Workspace
      • Hats Account
      • Role-Based Compensation
      • Safe Multisig Signing Authority
      • Telegram
        • Collab.Land --> Telegram
        • Guild.xyz --> Telegram
      • Snapshot: Voting, Weight & Proposal Creation
      • Wonderverse
    • ๐ŸŒŸEligibility & Accountability Criteria
      • Agreement Eligibility
      • Allow-List Eligibility
      • CoLinks Eligibility
      • ERC20 Eligibility
      • ERC721 Eligibility
      • ERC1155 Eligibility
      • Hat-Wearing Eligibility
      • Hats Election Eligibility
      • JokeRace Eligibility
      • Pass-Through (Hat-Based) Eligibility
      • Staking Eligibility
      • Subscription or Membership Fee (Unlock Protocol)
      • Gitcoin Passport Eligibility
    • โšกActivation & Deactivation Criteria
      • Seasonal/ Time-Expiry Toggle
      • Pass-Through (Hat-Based) Toggle
    • ๐Ÿ‘ทHatter Modules
      • Multi Claims Hatter
      • DAOhaus Moloch v3 Membership & Share Allocation
  • For Developers
    • ๐Ÿ‘ทHats Protocol, for Developers
      • Hat Properties
      • Wearing a Hat
      • Hat Admins & Hatter Contracts
      • Hats Trees
      • Hat IDs
      • Linking Hats Trees
      • Eligibility Modules
      • Toggle Modules
      • Hat Mutability and Editing
      • Creating Hats
      • Minting Hats
      • Transfering Hats
      • Renouncing Hats
      • Batch Actions
      • Hat Image URIs
      • ERC1155 Compatibility
      • โ›“๏ธSupported Chains
    • ๐Ÿค–v1 Protocol Spec
      • Hats.sol
      • HatsEvents.sol
      • HatsErrors.sol
      • HatsIdUtilities.sol
      • Interfaces
        • IHats.sol
        • IHatsIdUtilities.sol
        • IHatsEligibility.sol
        • IHatsToggle.sol
    • ๐Ÿ–ฅ๏ธv1 SDK
      • Core
        • Getting Started
        • Onchain Reads
        • Onchain Writes
        • Multicall
        • Claiming Hats
        • Utilities
      • Subgraph
        • Getting Started
        • Fetching Hats
        • Fetching Wearers
        • Fetching Trees
        • Misc
        • Types
      • Hat Details
        • Getting Started
        • Usage
    • ๐Ÿ”ญv1 Subgraphs
    • ๐ŸงฉHats Modules
      • ๐Ÿ”ŒModules SDK
        • Getting Started
        • Get Available Modules
        • Create New Instance/s
        • Composing Modules
        • Interact With Instances
        • Utilities
        • Types
      • โš’๏ธBuilding Hats Modules
        • Inside a Hats Module
          • Immutable Arguments
          • Module Setup
          • Versioning
        • Creating New Modules
        • How Module Instances Are Deployed
        • Modules Registry
        • About Module Chains
    • ๐Ÿ”Hats Signer Gate v2
    • ๐Ÿ‘’Hats Signer Gate SDK
      • Getting Started
      • Creating New Instances
      • Hats Signer Gate
      • Multi Hats Signer Gate
      • HSG & MHSG Handlers
    • ๐Ÿ’ผHats Account SDK
      • 1 of N Hats Account
        • Getting Started
        • Creating New Instances
        • Executing From An Instance
        • Constants
        • Types
    • ๐ŸŒHats Security Audits
  • Legal
    • Terms
      • Terms of Service
      • Acceptable Use
      • Privacy Policy
      • Cookie Policy
      • Attribution
Powered by GitBook
On this page
  • Step 1. Create a Charmverse role associated with your desired hat(s)
  • Step 2. Set page-level permissions for that Charmverse role
  • 3. Hat-gate access to that Charmverse role
  1. Hats Integrations
  2. Permissions & Authorities

Charmverse

How to hat-gate access to specific Charmverse roles, pages, and read/comment/write/admin permissions

PreviousCouncil Voting VaultNextDiscord

Last updated 1 year ago

is a Web3 platform that provides Notion-like workspaces, databases, a forum, bounty system, and proposal system, all of which can be accessible only to wearers of specific hats using Charmverse's highly-customizable roles and permissions system.

There are three steps to connecting Charmverse permissions with specific hats.

  1. Create a Charmverse role associated with your desired hat(s)

  2. Set page-level permissions for that Charmverse role

  3. Hat-gate access to that Charmverse role

Each step is explained in detail below.

Step 1. Create a Charmverse role associated with your desired hat(s)

To set up your hat-gated authorities within Charmverse, first navigate to your Charmverse space, open "Settings", and select "Roles & Permissions".

Next, select "Add a role" as seen in the lower-right of the screenshot above.

Create a Charmverse role you want to associate with a given hat or set of hats (you can associate multiple hats with a single Charmverse role). Enter a name for the role, do not add any members to the role, and select "Create role".

Once the Charmverse role has been created, open the role with the dropdown arrow, select "Permissions", and set your desired permissions associated with this role.

Step 2. Set page-level permissions for that Charmverse role

Next, navigate to any Charmverse pages within your space that you specifically want to set permissions for. Each page within Charmverse can set its own permissions along the dimensions of view, view & comment, editor, and full access. Note: subpages will inherit permissions from their parents.

Once on a page, navigate to the "Share" button in the upper-right, and click in the box that says "Add people, roles or email"

In the box that appears (shown below), set the permissions for this page, and add the role(s) you created into the "Roles" box. Then click "Invite".

Repeat this process for all the Charmverse pages you want to make accessible to holder of the role(s) you created (remember, subpages will inherit permissions from their parents).

3. Hat-gate access to that Charmverse role

To require an address to be wearing a given hat in order to claim a Charmverse role, and the permissions held by that role, return to your Charmverse space's "Settings", select "Invites", select "Add", and click "Add a Token Gate"

Selecet "Communities":

Select the blockchain network your hats are on and enter the Hats token ID associated with a hat you want to associate with this role (see Finding a Hat's Token ID for details on how to find specific hat token IDs).

Then click "Next", review your condition and select "Confirm".

Finally, locate this new "Token Gated Link" within the Invites page, and assign the role you created to this token ID.

Repeat this process for any other hats you want to associate with this same Charmverse role, or other roles you have created.

You can now select "Copy Link" associated with this Token Gated Link, which can be shared with wearers of the appropriate hat(s) to claim their Charmverse role and access the associated Charmverse permissions.

๐Ÿ”
Charmverse