Docs

Security

Configure who can access your community and claim quests.

Security

Security settings decide who can reach a Zealy community and who can claim its quests. A community can be made private so only invited people join, and can require members to connect a wallet, Discord, X (Twitter) or Telegram — or to hold X Premium — before they claim anything. Regional access blocks people by the region or country they connect from. The same panel controls how invites count toward invite tasks.

Overview

Configure who can access your community and claim quests.

Basics

From the security panel you can configure if you need an invite to access the community and if you need the users to authenticate with specific methods - either to link to other services or to have additional bot protection.

Private community

Enable this if you don’t want anyone to be able to access your community. Once enabled, only people who received an invite will be able to join.

Invites

Configure how invites are calculated for the invite tasks. Configure a higher XP than 1 to validate in order to reward quality invites rather than quantity. Enabling consuming the invites will mean that if the user claims an invite task requiring 10 invites and he has 15 in total, 10 of those will be consumed meaning that he after claiming only has 5 left. With this option enabled, you can set the invite task as recurring.

The state of a user’s invites can be inspected by herself or an admin from her profile.

Quest access verification

Enable the connections a member must have before claiming any quest in the community. A member missing one is asked for it at their first claim.

  • Wallet — connect a wallet on the community's blockchain.
  • Address — an extra toggle that appears when the community has a blockchain set and Zealy supports no wallet connection for it, labelled with that chain's name. The member types the address in rather than connecting it, which is why the toggle says the authenticity of the address can't be verified. Read those addresses as self-reported.
  • Discord — connect a Discord account.
  • Twitter — connect an X (Twitter) account.
  • Twitter Premium — require that the connected X account carries the verification badge.
  • Telegram — connect a Telegram account.
  • Email — no longer a toggle in this panel, but still a live requirement. A community that has it set keeps it: claims stay blocked until the member has a verified email address, and the setting can still be changed through the community settings API.

These are connection requirements rather than identity checks. They raise the cost of running several accounts, and they do not establish that two accounts belong to two different people. Separately from this panel, and not configurable from it, Zealy restricts accounts that reuse identifiers: accounts sharing a canonical email address, a connected social account or a verified wallet address are linked together, and an account is restricted from claiming once enough of those linked accounts have claimed themselves.

Regional access

Turn on Restrict by location to control which regions and countries can use the community, then choose a mode:

  • Block selected locations — everyone can take part except people connecting from the listed locations.
  • Allow only selected locations — only people connecting from the listed locations can take part.

Add locations with Add a region or country. Regions cover Africa, Asia, Europe, North America, South America, Oceania, the European Union and the European Economic Area, and you can mix them with individual countries. Block unknown locations also blocks people whose connection Zealy can't place in a country, in both modes.

The restriction applies to every quest in the community. A person connecting from a restricted location can't:

  • join the community, including through an invite link. They see This community is not available in your region. and the Join button is disabled;
  • claim any quest.

Existing members are affected too. They keep the XP they already earned, and rewards they already earned are still paid out; they just can't claim while they connect from a restricted location. Changes reach every server within a minute.

Zealy detects the location from the IP address of each connection, at country level. It does not use the country a member wrote on their profile, and states, provinces and cities aren't supported. A VPN or proxy changes the country Zealy sees, so treat regional access as a strong deterrent rather than a compliance guarantee.

To restrict a single quest instead of the whole community, add a Location condition to it.

The Public API and the MCP server can read and change the same setting through the community security settings.