How HoneyGate works for owners

The big picture for running your server: the "rules give roles" model, and where to start.

This is the starting point for the owner/staff guides. If you've just added HoneyGate, do First-time setup first, then come back here.

The core idea: rules that hand out roles

Most of HoneyGate follows one simple pattern:

When [something is true] → give this role.

You set a rule once. HoneyGate then enforces it for everyone, automatically, for as long as you leave it on. A few examples:

• When someone reacts to this message, give them a colour role.
• When someone reaches Level 10, give them the "Regular" role.
• (Pro) When someone's cross-server reputation reaches Trusted, give them an "Insider" role. A brand-new joiner qualifies the moment they arrive if they earned that reputation in other HoneyGate servers. You set it up under Passport → Reputation Gates, and the role stays once earned by default.
• (crypto, optional) When someone holds your token, give them the "Holder" role.

Almost everything here grants roles, so the single most important setup step is your role hierarchy. Drag the HoneyGate role above any role you want it to manage. If you only read one troubleshooting page, make it Bot permissions & role hierarchy.

Where to start (recommended order)

1. Welcome messages greet new members.
2. Self-assign roles let members pick their own roles.
3. Points & XP rewards activity.
4. Leveling & role rewards (Free) turns that XP into levels and unlocks roles.
5. From there, add what you need: quests, giveaways, a shop, tickets, moderation, and the rest.

Once you're set up, Recommended setup walks you through a sensible starting configuration.

Gating by token or NFT (optional, for crypto communities)

If your community is built around a token or an NFT collection, HoneyGate can check a member's wallet and grant roles based on what they hold. You build a gate:

One-time setup: crypto gating reads the Solana chain through a free Helius API key you paste into Web3 settings — the same key that powers the other crypto tools. Add it once. Without it, token and NFT gates stay dormant, and they never remove a role they couldn't check.

1. Make sure wallet verification is on. Members link a wallet with /verify.
2. Create a gate. Choose the condition (a token with a minimum amount, an NFT collection, or a specific NFT trait), say how many they need to hold, then pick the role to grant.
3. (Pro) Combine conditions with AND/OR logic, or gate on individual NFT traits.

Every gate on the Gates page shows the rule it enforces in full — "≥ 500 of $BONK", "≥ 3 NFTs from Pixel ZomBabiez" — so you can see at a glance what each role actually costs. The number on screen is always the number being enforced. NFT and trait rules count whole NFTs, so a part-number is rounded up (2.5 becomes 3) and the smallest you can ask for is 1; token amounts keep their decimals, because half a token is a real amount. If what you type isn't what gets saved, the confirmation message says so and gives you both numbers — it never just says "saved".

To change a threshold later, open the gate and edit the number in place; you don't remove the condition and add it back, which would leave the gate briefly asking for the wrong amount.

Roles update in real time as holdings change. When a member buys or sells, HoneyGate hears about it and adjusts their roles right away, and it runs a full re-check of every verified wallet roughly every 5 minutes as a backstop. The free plan includes up to two token gates and two NFT gates. Pro adds combo and trait gating, raises token gates to 10, and lets you add unlimited NFT gates. None of this is required. If you're not a crypto community, skip the whole section.

Free vs Pro

Some features below are marked Pro. See Free vs Pro for the full split. You never pay for anything you haven't turned on.