> For the complete documentation index, see [llms.txt](https://help.bloomsharing.com/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bloomsharing.com/doc/getting-started-with-bloom/taking-a-break.md).

# Ways we roll

## Reservations <a href="#taking-a-break" id="taking-a-break"></a>

If you'd like to allow users to reserve a ride in advance you can specify how long to hold a mobility asset. &#x20;

## Taking a break <a href="#taking-a-break" id="taking-a-break"></a>

If you’d like users to be able to take a break and hold their ride open while securing the locking mechanism, allow users to pause their rides. To enable, in the System Settings, activate the Pause needed feature.

With the Pause feature enabled, when a user ends the ride, they will be asked if they’d like to take a break or end their ride. If they choose to take a break, the rental will still be open and attached to the user. When they return to the mobility, they can re-activate and continue their ride. If this is a paid system, they will be responsible for the time during the break.

## Parking images

Want to get a peek at how user's parked their asset or ended their ride? You can require users to submit an image at the end of the ride.


---

# 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://help.bloomsharing.com/doc/getting-started-with-bloom/taking-a-break.md?ask=<question>&goal=<endgoal>
```

`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.