> For the complete documentation index, see [llms.txt](https://docs.claimr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.claimr.io/campaigns/campaign-sign-in-options.md).

# Campaign Sign-in options

To ensure the claimr widget works correctly with your dApp, make sure to configure the campaign settings accordingly.

To access these settings

1. Log in to your claimr account.
2. Select the **Campaign** you want to apply settings to.
3. Navigate to the campaign's **Settings** section.
4. Select **Sign-in options** from the settings menu.

<figure><img src="/files/zzfMBRUQOb9005JZM9z4" alt="" width="375"><figcaption><p>Campaign access rules settings</p></figcaption></figure>

### Require login to start a task

Ensure that users must log in (e.g. via wallet) before they can begin any task. This is necessary for claimr to associate actions with an authenticated wallet address.

### Require token to start campaign

If enabled, this would require a specific token to access the campaign.

### Wallet change is disabled&#x20;

Prevent users from switching wallets mid-session.

### Disable users merge&#x20;

Disables automatic merging of user identities across sign-in methods.

### Select sign-in services

Choose the platforms users can log in with (e.g., Twitter, Telegram, Discord). You can enable one or multiple options.

### Chains

Select the blockchain networks supported by your campaign (e.g., Ethereum). These define where wallet-based actions will be validated.

### Wallet message field&#x20;

Enter a custom message that will be shown to users during wallet signature to identify the purpose of signing.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.claimr.io/campaigns/campaign-sign-in-options.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.