> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/updates/development-updates/2025-dev-updates/august-15-2025-dev-update.md).

# August 15, 2025 - Dev update

Explore what new changes the Dev team has deployed in the last week!

This can be anything from new features, bug fixes, or QoL changes!

<details>

<summary><strong>New features and items</strong></summary>

* **Check back next week!**

</details>

<details>

<summary><strong>Bug fixes and chores</strong></summary>

* **DevOps**
  * Various improvements to Rewsts CI/CD pipeline to make releasing more efficient.
* **App Builder**
  * Corrected site cloning permissions so pages inherit permissions from parent pages.
* **Organization variables**
  * Fixed error when persisted organization filter is a deleted organization.

</details>

<details>

<summary><strong>Coming Soon</strong></summary>

* To make sign-in clearer for users, we will be updating the Microsoft login button from **Sign in with Entra ID** to **Sign in with Microsoft**. There's no change in functionality, and your login process for Microsoft stays the same.
* DropSuite integration
* BVoIP integration
* Leader Integration
* Hourly dashboard updates

</details>


---

# 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.rewst.help/updates/development-updates/2025-dev-updates/august-15-2025-dev-update.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.