> 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/members/details.md).

# Details

This is the details view of a member. You can find a lot of (sensitive) information like their address, age, gender, phone, ... Phones and email addresses are clickable for your convenience. Phones even show the country where the phone number exists.

You can find more buttons on the top of this page

* **Check in / out**: Open up the [personal checkin page](https://docs.eventication.com/event/accreditation/check-in-out.md) of this person.
* **Lock / unlock**: Lock or unlock this persons current event data. This way the member can't edit their current shiftpicker, catering, ...
* **Block**: Block this person from accessing this event.

{% hint style="info" %}
We'll do the following automatically after blocking:

* Disable all working wristbands this person currently has. This results in rejection when trying to get a [meal](https://docs.eventication.com/event/general/food-and-beverages.md) or traveling to [zones](https://docs.eventication.com/event/accreditation/zones.md)
* Show the block on the [checkin page](https://docs.eventication.com/event/accreditation/check-in-out.md)
* Forbid from printing or adding a new [wristband](https://docs.eventication.com/event/accreditation/wristbands.md)
* Forbid giving [rewards](https://docs.eventication.com/event/general/rewards.md)
* Forbid [checking in](https://docs.eventication.com/event/accreditation/check-in-out.md)
* Forbid from [leasing more stock](https://docs.eventication.com/event/stock/leases.md)
  {% endhint %}

{% hint style="danger" %}
Blocking doesn't remove the person from your event yet.
{% endhint %}

* **Delete**: Permanently delete this person from this event.

### Top Up integration

If you have enabled one of our top up [integrations](https://docs.eventication.com/event/general/integrations.md) for this event you can

* Sync this person with that service now
* View the roles attached to this person
* View the [top-ups](https://docs.eventication.com/event/general/integrations/anykrowd/top-ups.md) this person has received via the [reward](https://docs.eventication.com/event/general/rewards/top-up-rewards.md) system


---

# 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/members/details.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.
