> For the complete documentation index, see [llms.txt](https://docs.guild.xyz/guild/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guild.xyz/guild/how-to-setup-rewards/secrets.md). # Secrets Share hidden text, codes, or exclusive content that only qualified members can access. Perfect for coupon codes, private links, exclusive announcements, or special instructions. #### Setting up Secret rewards **1. Create the secret** * In the role editor, click **"Add reward"** and select **Secret** * Add a **Reward image & title** to represent your secret (e.g., "Secret Code", "Hidden Content") * Write your **Secret Text** using the rich text editor * Format your content with bold, italic, lists, and links as needed * Click **"Create Secret Reward"** #### How Secret rewards work for members * Members see the secret reward title and image but cannot view the content until they meet role requirements * Once qualified, members click **"Reveal Secret"** to access the hidden content * Secret content remains accessible as long as they maintain role eligibility * If members lose role access, they can no longer view the secret content --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.guild.xyz/guild/how-to-setup-rewards/secrets.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.