> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/profiles/creating-a-customer-profile/security-notes.md). # Security Notes Security Notes are messages and reminders that staff can attach to a Profile for future reference. The Security Notes on a Customer’s Profile can be from a Reservation, an Event, or left directly on the Customer's Profile. To find the Security Notes on a Customer: * Navigate to the Customer tab of the Admin Dashboard * Search for a specific Customer * Click into the Customer’s Profile * Click on the Security tab at the top * View any notes connected directly to the Customer Profile * Review any notes from Reservations and Events the Customer has attended There is also space to take a Customer's photo. By click on the photo, your computer will ask to access your camera (normal on any browser). If you have a camera connected to the front desk computer and want to take a photo of Customers coming in to the Club, take it here.

### Related Updates * [Read a Customer Note from the Has Notes Tag](/profiles/creating-a-customer-profile/read-a-customer-note-from-the-has-notes-tag.md) --- # 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.podplay.app/profiles/creating-a-customer-profile/security-notes.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.