> 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/accreditation/wristbands.md).

# Wristbands

Our company offers a comprehensive solution for event wristbands, providing event organizers with the flexibility to choose between personalised [wristbands printed on the spot](https://docs.eventication.com/event/misc/wristbands.md#on-site-printed-wristbands) or [pre-created wristbands](https://docs.eventication.com/event/misc/wristbands.md#bring-your-own-wristbands). The unique QR code makes it easy for seamless check-in, scanning between zones, and meal distribution.

The personalised locally printed wristbands serve as a multi-functional tool for attendees, providing them with a convenient way to access different areas of the event. The QR codes on the wristbands enable efficient check-ins at designated checkpoints, ensuring secure and streamlined entry into different zones. Additionally, attendees can seamlessly scan their wristbands to access meals during the event.

For organizers who prefer pre-created wristbands, we offer a range of options with unique QR codes that provide the same functionalities as the printed wristbands. While these wristbands are not personalised, they still offer the convenience of quick and secure access to different event areas and services.

Want more information about our wristband solutions? Click [here](https://docs.eventication.com/event/misc/wristbands.md).

## Details

Opening up the details page of a wristband shows you a wealth of data.

**Code**: The code behind the QR code. You can copy the code text of download the QR code image.

**Owner**: The person wearing this wristband.

**Created at**: The date when this wristband was added to/printed on the platform.

**By**: The moderator that added/printed this wristband

**Printed by Eventication**: As you can combine on the spot printed wristbands with pre-created wristbands, this indicates which is which.

**Preview**: Regenerate a preview of this wristband.

## Enable / disable

There is a "Disable" button on the top of the page to disable the wristband you're viewing right now. This change is immediate and every scan of this wristband will show that it has been disabled. Scanner screens will always return <mark style="color:red;">red</mark> in stead of <mark style="color:green;">green</mark>. A disabled wristband shows an "Enable" button instead, so you can activate it again.

These buttons are only visible to moderators who are allowed to edit wristbands.

{% hint style="info" %}
You can also enable or disable wristbands in bulk using the **Bulk enable** and **Bulk disable** [filter actions](https://docs.eventication.com/event/general/filters/actions.md).
{% endhint %}

## Delete

Moderators who are allowed to edit wristbands can delete a wristband using the trash button on top of the details page. A wristband can be deleted when it was not printed by Eventication, or when it has been disabled first.

Deleting a wristband does not delete its history: zone travels, given food & beverages and the print history are kept, they are just no longer attached to the deleted wristband.

## Filters

Wristbands have their own [filter](https://docs.eventication.com/event/general/filters.md) category. Next to parameters like enabled or disabled and created between dates, you can also filter on **printed or created by certain moderators**: select one or more moderators and the result contains all wristbands they created or sent to a wristband printer.


---

# 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/accreditation/wristbands.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.
