> 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/roc-open-mics/roc-open-mics-north-america/2025-roc-open-mics/march-28-2025-how-little-changes-and-small-updates-bring-big-value.md).

# March 28, 2025: How Little Changes and Small Updates Bring BIG Value

### **Join Live!**

Join us live every Friday at 3 pm EST!

[Download the Calendar Invite here](https://engine.rewst.io/webhooks/custom/trigger/02eb02e2-1177-43d9-9e13-8547414979fc/c47fdd7f-4075-47a8-ba92-94e790e67c06?request_type=open_mic_link&)!

## Open Mic Video Recording

{% embed url="<https://youtu.be/nLZePQvTBDs>" %}

### Contents of the Recording:

* 🗣️ Aaron emphasizes the importance of asking questions, engaging on Discord, tracking time savings in workflows, and reminds that the call is geared toward technical users.
* 🎤 Ashe announces a fun internal and community April Fools’ workflow challenge.
* 🌍 George launches Europe and ANZ Open Mics and requests feedback via an App Builder usage survey.
* 🧰 Danial shares updates on App Builder UX, Shortcut & Traceless integrations, and invites testers to try the new beta PowerShell interpreter.
* 🛠️ JP highlights new Marketplace crates for inactive users/devices, login anomaly detection, and password reset improvements.
* 🎓 Brandon gives certification shout-outs, previews LMS progress, and reviews new documentation and transform actions.
* 📨 \[External Demo] Gareth demos a simple completion handler workflow to onboard users and send portal instructions.
* 🧩 \[External Demo] Tre shows a templated approach to managing user groups and permissions at scale.
* 📊 \[External Demo] Justin presents an automated, modular workflow for M365 reporting using direct API registrations.
* 🛡️ \[External Demo] David demonstrates how to sanitize Jinja input and redact sensitive data to prevent injection.
* 🎬 Aaron wraps with thanks to demo participants and a PowerShell beta sign-up update.

<details>

<summary><strong>How to Get Help</strong></summary>

* 💬 Chat (Discord): [https://discord.gg/rewst​​](https://discord.gg/rewst%E2%80%8B%E2%80%8B)
  * Private #{{ msp }} channel
  * \#the-kewp
* 🎫 Submit Tickets to: <the_roc@rewst.io>
* 📝 Feature Request + Integration Requests: <https://rewst.canny.io/>

**CLUCK UNIVERSITY – REWST TRAINING:**

* 👨‍🏫 Live Instructor-Led Training: <https://calendly.com/cluck-u/>
* 🏁 Rewst Foundations Training: <https://docs.rewst.help/cluck-university/rewst-foundations-10x>
* ▶️ On-demand Videos: <https://docs.rewst.help/cluck-university/rewst-foundations-10x>

**DOCS:**

* 🥚 Rewst Docs: <https://docs.rewst.help>
* ⛩️ Jinja Docs: <https://jinja.palletsprojects.com/>

**KEY LINKS:**

* 📝 Feature Request + Integration Requests: <https://rewst.canny.io/>

</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 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.rewst.help/updates/roc-open-mics/roc-open-mics-north-america/2025-roc-open-mics/march-28-2025-how-little-changes-and-small-updates-bring-big-value.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.