Restricting quest access to Discord role

Learn how to restrict quest access to specific Discord roles or other requirements using Domino's quest prerequisite system.

---

Prerequisites

• A Domino account with quest creation access

• A Discord server connected to your Domino community

• Existing Discord roles you want to use for access control

Overview

Domino's quest system allows you to create gated content that only specific community members can access. By using the quest prerequisite system, you can require users to verify certain credentials (like Discord roles) before accessing your main quests. This creates a powerful access control system that integrates with your existing community infrastructure.

Creating a Role Verification Quest

The first step is creating a special verification quest that checks if a user has the required Discord role.

Setting Up the Verification Task

1. Create a new quest in your Domino dashboard

2. Add a Discord role verification task

3. Configure the task to check for the specific role(s) you want to require

Verification Quest Best Practices

• Give your verification quest a clear name like "Discord Role Verification"

• Use a descriptive explanation so users understand what's happening

• Keep verification quests simple - usually a single task is sufficient

Publishing Your Verification Quest

After setting up your verification task:

1. Review the quest configuration

2. Publish the quest to make it available to your community

3. Test the verification process to ensure it correctly validates the role

Setting Up Quest Prerequisites

Once your verification quest is published, you can use it as a prerequisite for other quests.

Configuring Required Quests

When creating or editing your main quest:

1. Find the "Required quests" field

2. Select your verification quest from the dropdown

You can require multiple prerequisite quests if needed. Users will need to complete all listed quests before accessing the gated quest.

Advanced Locking Configuration

Domino provides options to customize how locked quests appear to users who haven't completed the prerequisites.

Disable When Locked Option

Under the Advanced Options section:

• Enable "Disable when locked" to completely hide the quest from users who haven't completed prerequisites

• Disable this option to show the quest but prevent completion until prerequisites are met

Configure visibility behavior for users who haven't completed prerequisites

If you disable the "Disable when locked" option, users will see the quest but get a notification explaining they need to complete prerequisites first. This can provide better guidance but might confuse some users who can see but not access the content.

Beyond Discord: Other Verification Methods

While Discord role verification is common, this prerequisite pattern works with any verification method Domino supports.

Alternative Verification Types

You can create verification quests that check for:

• Ownership of specific NFTs or tokens

• Twitter follow status

• Community membership duration

• Completion of other community activities

• Custom validation through automations

Creating a Token-Gated Quest

For Web3 communities, create a wallet verification quest that checks for specific token holdings, then use this as a prerequisite exactly as you would with Discord verification.

Troubleshooting

Common Issues

• Missing Discord Connection: Ensure your community has a valid Discord connection

• Role Sync Issues: Verify that role information is properly syncing from Discord

• Prerequisite Not Showing: Make sure your verification quest is published before using it as a prerequisite

• Users Can't Access: Check that users are completing prerequisites in the correct order

Role verification happens at the time of quest completion. If a user loses their role after completing the verification quest, they may still access gated content.