> For the complete documentation index, see [llms.txt](https://docs.loopit.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.loopit.co/people-companies/trupass/blocked-status.md).
# Blocked status
* **Person Blocking Policy**
* Users have the ability to block or unblock people on the Loopit platform. When an individual is blocked, any other people/companies with matching details will be automatically blocked across the Loopit platform within 24 hours.
* If an individual with matching details is later added to a different workspace, they will be automatically marked as blocked in that workspace as well.
* Individuals who enroll directly through the website will not encounter any restrictions during the signup process if they identified as blocked. However, workspace retains the authority to review the status of such individuals after enrollment and may take appropriate action on their bookings.
* **Managing block status**
* A person can be blocked by navigating to the **Trupass > Blocked Status** section within the platform.
* Once a person is blocked, an Unblock option will become available. Unblocking can only be performed from the same workspace where the individual was originally blocked. For example, if Person A is blocked and another individual, Person Z, is created with the same identifying details, Person Z will also be automatically marked as blocked. However, unblocking is only possible for Person A—the original blocked user. Once Person A is unblocked, all associated users with matching details, such as Person Z, will also be automatically unblocked.
* At present, only individual persons can be blocked on the platform—companies cannot be directly blocked. However, if a company's details match those of a blocked individual, the blocked status will be reflected on the company’s dashboard.\
\
* **Criteria for Blocking**
* The following personal details are considered when determining whether to apply a block status to an individual:
* Email address
* Phone number
* Residential address
* Billing address
* Driver’s licence number and address
* Passport number and address
* **Address Matching Logic**
* For address-based blocking, the system evaluates all the following address types:
* Residential address
* Billing address
* Licence address
* Passport address
* If **any** of these addresses match between individuals, a block will be triggered.
* **Example:** If *Person A* is blocked and has only a **residential address**, and *Person B* has a **billing, licence, and passport address**, but *Person A’s residential address* matches *Person B’s passport address*, then *Person B* will also be identified as blocked.
*
```
```
* **Block Status Visibility**
* The block status of an person or company is displayed in the following areas of the platform:\
* **Summary section** of the person or company dashboard
* **Menu > Search** when searching for a person or company
* **Summary section** of the booking dashboard, if the primary driver is blocked
* **Booking creation flow**, during the selection of a person, company, or additional driver
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.loopit.co/people-companies/trupass/blocked-status.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.