> For the complete documentation index, see [llms.txt](https://docs.firecal.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.firecal.app/organizations/org-administration/departed-member-records.md).
# Departed Member Records
When a Member deletes their account, any Certs your Org relied on for compliance don't simply vanish from your records. CertLocker keeps a read-only copy for your department, so you still have the evidence you need. Officers and Admins can view them.
## Open Departed Member Records
Tap **Orgs** in the navigation bar, tap your **Org Card**, then tap the **Manage Icon** in the top right corner of the Org's profile, then tap **Departed Member Records**. You'll see each former Member, with how many records were kept and when.
## Browse a Former Member's Records
Tap a former Member, then a category, like **Certs** or **Training records**, and tap any record to see its details: who held it, its type, its credential number, when it was archived, and its **Archived documents**. These records are read only.
---
# 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.firecal.app/organizations/org-administration/departed-member-records.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.
