> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/developing-mods/sharing-mods/exposing-activation-time-mod-options.md). # Exposing Activation-Time Mod Options You may want to allow users to configure specific items when activating a mod, without requiring them to build the whole mod from scratch. For instance, you may do this if you created a mod for creating a new card on a Trello board. You might want to allow them to pick the boardId in the configuration so they can specify which board it goes to. ### Integration Configurations If you’ve added bricks requiring integrations to the mod, those integrations will automatically show up in the Mod Activation Wizard. ### Custom Options If you have non-integration onboarding options you want to add, you can add them by selecting the mod in the Page Editor and selecting the **Input Form** tab.
Similar to the Form Builder, you can add any number of options fields: * Name: the field name for referencing the configured value in the mod. For example, * Label: the human-readable label to display in the Mod Activation Wizard To add a new field. Click the **Add new field** button. To switch between fields, click the field in the Preview in the Data Panel on the right side of the Page Editor. ### Referencing the options items. You'll use `@options.{name}` If the name is `fieldName`, the field would be available in the mod as `@options.fieldName` --- # 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.pixiebrix.com/developing-mods/sharing-mods/exposing-activation-time-mod-options.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.