> 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/marketplace-updates/2024-marketplace-updates/december-13th-2024.md).

# December 13th, 2024 - Marketplace Update

Explore the new changes to the Marketplace in the last week!

This can be anything from new crates, enhancements, or bug fixes!

<details>

<summary><strong>New crates and enhancements</strong></summary>

* **Refactor of the following crates:**
  * Alert when Mailbox Quota Full
  * Document Shared Mailboxes
  * JIT Admin Access (new features on this one including M365 support!)
  * Change a User's Password

</details>

<details>

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

* Notify on Conditional Access Changes Crate:
  * Handling if the CA policies couldn't be pulled
  * Modified Jinja for input policy objects
  * Added GSA (Global Secure Access) support and fixed issue for if no match could be made for GUID (resulting in empty return) that was failing list comp.
* New Employee:
  * Form: Add check for missing username and email domain. Reporting back as option gen result to user.
  * Updated template to adjust \`if\` statement in the Jinja to work correctly for "Create-OnPremExchangeMailbox V2"
* Billing Count Report Crate:
  * Added a output for `workflows_dev_process_psa_create_ticket` and created a ticket\_id data alias.
  * Added automation logs to the \[PROD - TASK] Rewst: Send Email with Attachment subworkflow including a automation\_log output.
  * Added automation log to inner m365 action and replaced the pulling method with a get on the `subscribedSkus` endpoint
  * M365 User Licenses: instead of returning the whole object, only returning the `skupartnumber` if it doesn't find a match in the template
* Disabled Users with Licenses Crate:
  * Add protection in the org lookup workflow of the Disabled Users With Licenses crate to prevent the workflow from failing if a user decides to put bad JSON into the org var and run it with the json\_serialize set to true.
* Pax 8 License Purchase: Updated license name in template
* Amend Mailbox Permissions Crate:
  * Added a noop check for company\_id to gracefully fail if the org variable is missing

</details>

<details>

<summary><strong>Coming soon!</strong></summary>

* App Builder Apps
  * Operational Analytics Portal - aggregates data from various tools and outputs actionable insights for MSPs to further streamline operations.
  * Forms Portal - allows employees and clients to easily access the necessary Rewst forms based on granular permissions.
  * All-In-One Client Portal - The portal transforms service delivery by empowering clients to instantly self-serve common IT requests —not just submit tickets.
* Top 10 crates - Improving success rates and implementing Rewst Best Practice
  * Detailed MFA Reporting
  * Document User Details v2

</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/marketplace-updates/2024-marketplace-updates/december-13th-2024.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.