> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/housekeeping/housekeeping-module/hk-queries1/faq-on-queries/how-do-i-view-the-blocked-rooms-report.md).

# How do I view the Blocked Rooms report?

To view the Blocked Rooms report within the Housekeeping module, which allows you to check details like the reason for the block, the user who performed it, and the current status, follow these steps:

1. Navigate to the Queries menu and select Blocked Rooms.
2. Choose any additional options you want printed in the report or use the available filter options to narrow your results.
3. Click the display button to generate and view the report.

This report provides a comprehensive list of rooms currently out of service, including the blocked for reason, the room type, the username of the person who blocked it, the date it was blocked, and the room's current status


---

# 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://help.rbsgo.com/housekeeping/housekeeping-module/hk-queries1/faq-on-queries/how-do-i-view-the-blocked-rooms-report.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.