> ## Documentation Index
> Fetch the complete documentation index at: https://developers.essal.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog — July 1, 2026

> Essal platform release notes for July 1, 2026.

## What's New

### Essal Office — Template Library

The Office app now ships with 30 pre-built document and spreadsheet templates covering common business needs: meeting notes, project briefs, budget trackers, and status reports. Templates are available via the dashboard and the API:

```bash theme={null}
POST /v1/office/documents
{ "title": "Project Brief", "template_id": "tpl_office_project_brief" }
```

### Essal Guard — Policy Simulation Mode

Before activating a policy, you can now simulate its effect against all recent API requests in your workspace. The simulation report highlights which requests would have been affected, making policy validation significantly safer.

```bash theme={null}
POST /v1/guard/policies/{id}/simulate
{ "lookback_hours": 24 }
```

### Essal Sales — Revenue Forecasting Enhancements

The forecast endpoint now supports quarterly and annual period groupings, and forecasts can be broken down by both stage and deal owner simultaneously. See [Pipelines API](/api-reference/sales/pipelines) for updated parameters.

### Essal Project — Sprint Analytics

Sprint summary reports are now available via API. Retrieve velocity, completion rate, and scope change data for any completed sprint:

```bash theme={null}
GET /v1/project/sprints/{sprint_id}/summary
```

***

## Bug Fixes

* Fixed an issue where deleting a Guard policy in `inactive` status returned a `500` error in some edge cases
* Resolved a race condition in the Office real-time collaboration engine that occasionally dropped operations during reconnection
* Corrected pagination cursor behaviour on the `/v1/sales/deals` endpoint when filtering by `status=lost`

***

## Deprecations

* The `X-Workspace-ID` header is deprecated and will be removed in **v2**. The workspace is now inferred from the API key. Existing integrations continue to work until the v2 cutover.