> For the complete documentation index, see [llms.txt](https://docs.guardianservice.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardianservice.app/whats-new/release-notes/beta-releases/mgs-beta-v2.md).

# MGS Beta v2

## New

Below is a list of improvements that are included in the Managed Guardian Service Beta v2

* Upgrade to core open-source Guardian v2.8 (Retirement process for assets, Matched Assets, 3rd Party Content Providers, Modular Benefit Projects, and LedgerWorks Eco Explorer Implementation)
* Adding 2 DOVU CRU methodologies to the preloaded policies (Agrecalc and Cool Farm)
* Extend the POST/tenants/invite endpoint with the ability to return the inviteId in response
* Updated Swagger Documentation for Beta V2
* Enable Admins to manage users
* Improved Internal Alerts
* Enhanced Autoscaling for performance loading
* Bug fixes

{% hint style="info" %}
This will only cover what is new and improved with the Managed Guardian Service. For the full changelog and release notes on the open-source Guardian please visit: <https://github.com/hashgraph/guardian/releases>
{% endhint %}


---

# 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.guardianservice.app/whats-new/release-notes/beta-releases/mgs-beta-v2.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.
