> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/changelog/2022/june-2022.md). # June 2022 ### New features * The s[ervice outage edit API ](https://api.ilert.com/api-docs/#tag/Service-Outages)is now available * All public facing incident communications emails now support beautifully crafted html email versions * We have introduced a new feature for private status pages to make them available to any user within an organization even if the entity itself is owned by a private team or hidden from stakeholders "Account Wide View" * we have launched a [public roadmap](https://roadmap.ilert.com/roadmap) * we have launched a completely new onboarding experience for new accounts * added a new subscription API endpoint for status pages to add or remove a single subscriber ### Improvements * the MFA status is now visible in the user list * browser caching of certain script and style resources has been optimized for faster page load ### New and updated integrations * [Samsara Inbound integration](/integrations/inbound-integrations/samsara.md) has been added --- # 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.ilert.com/changelog/2022/june-2022.md?ask=&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.