Manage an allowlist

Upload or collect an allowlist of wallets and email addresses, and gate a role, Discord role or Telegram group with it.

To manage an allowlist (whitelist) in Guild, create a role and give it an Allowlist requirement: upload a .txt or .csv file with one EVM wallet address or email address per line, and only people on the list get the role and what it unlocks, such as a Discord role, a Telegram group or a gated page. If you don't have the list yet, let Guild collect it: create a role whose requirements describe who qualifies, then export the members who hold it from Members.

Both approaches start with a guild. If you don't have one, go to /create.

Gate access with a list you already have

Use this when you already know who should get in: beta testers, event sign-ups, hackathon winners, customers, or a snapshot taken somewhere else.

  1. Prepare the file. Put one wallet address or email address on each line; you can mix both kinds in one file. In the requirement form, View example file shows the format.
  2. In the admin panel, open Spaces & roles and choose New role, then Empty role. Name it, for example "Allowlist", and press Save.
  3. Under Who gets it, press Requirement and pick Allowlist.
  4. Keep Should satisfy selected.
  5. Choose Upload allowlist, pick the file and wait for Uploaded allowlist.
  6. Under Custom image and name, give the requirement a name you will recognise later, such as "Beta testers, October".
  7. Press Add requirement.
  8. Under Unlocks, press Add reward and add what the list should open: a Discord role, a Telegram group, a secret, points or access to a page. See Rewards.

People on the list sign in to Guild, connect the wallet or email address you listed, and join the guild. A member matches with any wallet or email address connected to their Guild account, so they don't have to sign in with that exact one.

Add, remove or check entries

Open the requirement from the role's Who gets it list:

  • View uploaded allowlist opens the list with a search field, so you can check whether an address is on it. Download saves it as a text file.
  • To add people, paste them into Add new addresses or IDs, one per line, and press Add new items.
  • To remove people, upload a new file with Upload allowlist and press Save. Members who are no longer on the list lose the role, and its rewards, when they are next checked.

Collect the list with a role

Use this when the list is the result of a campaign: everyone who did something, rather than names you picked.

  1. Create a role, for example "Mint allowlist".
  2. Under Who gets it, add the requirements that earn a spot, for example follow your account on X, join your Discord server, and an Onchain activity requirement for a first transaction before a date you pick, to filter out fresh wallets. Set Members should meet to All. See Requirements for every type.
  3. To cap the number of spots, open How many get it, set Only the first members and press Save limit. The role closes once that many members hold it, and members see how many spots are taken.
  4. Share the guild link. People join, Guild checks them against the role, and everyone who qualifies gets it.

When the campaign ends, open Members, choose the Roles filter and pick the role. Press Export audience, then Export CSV, and download it with Download CSV when it's ready. The CSV includes member IDs and wallet addresses on every plan; connected accounts such as Discord, X and GitHub are included on the Growth plan and above. See Members and analytics.

Review applications by hand

If you want to pick people yourself, use a form. Members fill out a gated form with Automatic approval off, you approve or reject each response, and a second role with the Submitted a form requirement goes only to approved members. Forms and the Submitted a form requirement are part of the Pro plan and above. See Forms.

Keep people out with a blocklist

An allowlist requirement set to Should not satisfy works the other way round: everyone except the people on the list meets it. Add it next to your other requirements, with Members should meet set to All, to keep known bots or banned wallets out of a role.

When a list is the wrong tool

An uploaded list is a snapshot: it only changes when you change it. If the rule is onchain, such as holding your token or NFT, a token or NFT requirement stays current on its own: members who sell lose access when they are next checked. You can combine both in one role, for example "on the allowlist and holds at least one NFT".

FAQ

Is an allowlist the same as a whitelist?

Yes. Guild calls it an allowlist. It is the Allowlist requirement on a role: a list of wallet or email addresses you upload, checked against each member's connected accounts.

Can I use email addresses instead of wallets?

Yes. One file can hold wallet addresses, email addresses or both, one per line. A member matches once that email address is connected to their Guild account.

Which file formats can I upload?

A .txt or .csv file with one EVM wallet address or email address per line. Use View example file in the requirement form to see the format.

Does the allowlist requirement need a paid plan?

No. The Allowlist requirement, Discord and Telegram rewards and member exports with wallet addresses are on the free plan. Forms with manual approval need Pro or above. See Plans.

What happens when I remove someone from the list?

When they are next checked, they lose the role and whatever it unlocks, such as the Discord role or Telegram group. Members who are still on the list keep their access.

All Guild docs