> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/planning/settings/members/double-confirmation.md).

# Double confirmation

Just to make sure

This feature will allow you to collect members, create or edit their planning and request final confirmation about the schedule via email.

{% hint style="info" %}
Our double confirmation is a great option for those events who

* do not use the [Gamma](https://docs.eventication.com/event/planning/settings/members/shiftpicker.md#gamma) shiftpicker and would still like confirmation from the member about their working hours and jobs
* make a lot of changes to the planning and want confirmation once they are ready for it
  {% endhint %}

**Enabled**: Enable this feature. If you disable it, all buttons that cover "double confirmation" will be hidden from the views.

**Reset confirmation if a moderator changes a shift?**: If a member (or moderator) has confirmed the planning schedule and a moderator makes a change, should the platform reset the confirmation?

**Reset confirmation if the member changes a shift?**: Same as the previous setting, but when the member edits their planning. This might occur when a day or a job is removed.

**Allow confirmation change after confirmed?**: Once a member (or a moderator) has confirmed the planning, are they allowed to change their mind afterwards?

**Lock after confirm?**: After the member confirms their double confirmation, the platform will auto lock the membership.

**Hide days without shifts?**: Should a member be able to see days where they don't have a shift in their double confirmation view?

## Emails

When requesting double confirmation of a planning schedule, the platform will send an email to the member. This email is customisable.

**Email subject**: The subject of the email the platform sends out.

{% hint style="success" %}
This text field supports [variables](https://docs.eventication.com/event/misc/variables.md).
{% endhint %}

**Email text**: The body of the email.

{% hint style="success" %}
This text area supports [formatting](https://docs.eventication.com/event/misc/text-formatting.md) and [variables](https://docs.eventication.com/event/misc/variables.md).
{% endhint %}

**Email button**: Customise the title of the button in the double confirmation email that directs them to their confirmation page.

There are default values if you leave **subject**, **text** or **button** empty.

## Confirmation page

The double confirmation email contains a button that direct the member to their personal confirmation page. This page can also be customised.

**Page text**: The text at the top of this page.

{% hint style="success" %}
This text area supports [formatting](https://docs.eventication.com/event/misc/text-formatting.md) and [variables](https://docs.eventication.com/event/misc/variables.md).
{% endhint %}


---

# 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.eventication.com/event/planning/settings/members/double-confirmation.md?ask=<question>&goal=<user_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.
