# Release Notes — 2.102 Covers the `2.102.x` Helm chart series. Most recent patch: **2.102.1**. _Unless a subsection says otherwise, changes apply to both Monad SaaS and self-hosted._ ## New features & improvements - **Contributors can create API keys with a lesser role** — the Contributor role can now see the organization's roles, so Contributors can give a new API key a narrower role such as Data Sender. They still can't assign a role with permissions their own role lacks. [Docs →](https://app.monad.com/docs/guides/api-keys) (2.102.1) ## New connectors - **Serval Audit Logs (input)** — collects audit events from Serval, the AI-powered IT service and access management platform: access requests, approvals, provisioning, access reviews, policy and role changes, sign-ins, workflow changes, and API key activity, each with the actor, source, outcome, and justification. [Docs →](https://app.monad.com/docs/inputs/serval/serval-audit-logs) (2.102.1) - **Tsuga (output)** — sends records to Tsuga, a bring-your-own-cloud observability platform, through its logs intake API, so you can search, alert on, and build dashboards over them in your own Tsuga cluster. [Docs →](https://app.monad.com/docs/outputs/tsuga) (2.102.1) ## Fixes **SaaS & self-hosted** - **SQS and CrowdStrike Next-Gen SIEM outputs stay within request size limits** — SQS batches are now kept under AWS's 1 MiB batch limit and CrowdStrike Next-Gen SIEM requests are split at 5 MB, so large batches are delivered instead of being rejected and retried. (2.102.1) - **DocuSign Monitor input shows why a token request failed** — when DocuSign rejects the credentials, the input now reports DocuSign's error instead of an empty 401, so you can see what to fix. (2.102.1) **SaaS only** - **Signing in after a password reset opens the sign-in form** — users returning from a password reset no longer land on the sign-up form. (2.102.1) **Self-hosted only** - **Database passwords with special characters work** — a password containing URL-reserved characters such as `@`, `:`, `/`, `?`, `#`, or `%` no longer breaks the connection to a database you provide. Keep the password in the Secret unencoded. (2.102.1) ## Breaking changes None. ## Need help? See the [Monad docs](https://app.monad.com/docs) for setup guides and reference, or reach out to Monad Customer Support at [support@monad.com](mailto:support@monad.com) or via your dedicated Slack customer channel. :::note Self-hosted deployments upgrade to a `2.102.x` release with `helm upgrade`. Review the **Breaking changes** section above before upgrading; when it says "None," the upgrade is drop-in. :::