Monthly changelog

Write Trestle's marketing changelog email for September 2026, "What's new in Trestle: September". It goes to everyone who subscribed to Trestle updates and walks through the month's releases, one feature at a time, followed by a compact list of smaller changes. Cover the facts below, in this order.

Headline: What's new in Trestle: September. One short introduction paragraph: returning users can now sign in to the Trestle mobile apps with device biometrics, workspace plans support discounts and promo codes, and OAuth apps can be given custom scopes, with more below.

Seven features follow, in this order. Each has its own heading, a product screenshot in the Trestle style shown at the full content width above or below the heading, one paragraph, and a "Read more" text link to that feature's changelog page. No feature has a button.

Feature 1, Biometric sign-in for the mobile apps. Reference artwork: assets.illustrations.changelogBiometric Returning users can sign in to the Trestle iOS and Android apps with Face ID, Touch ID, or Android biometrics. After a first sign-in, a user can enroll that installation as a trusted device and skip their usual sign-in method on return. The private key never leaves the device. Workspace admins can require trusted devices to re-authenticate every 30 days from Settings, Security. Read more: https://trestle-email.s3.amazonaws.com/changelog/biometric-sign-in

Feature 2, Discounts and promo codes for workspace plans. Reference artwork: assets.illustrations.changelogDiscounts Trestle Billing supports percentage and fixed-amount discounts that last one billing period, a set number of periods, or indefinitely. An admin can apply a discount directly to an active subscription from the billing page, or Trestle can issue a promo code that a workspace redeems at checkout. Codes can be capped at a total number of redemptions, restricted to new workspaces, and tracked from Settings, Billing. Read more: https://trestle-email.s3.amazonaws.com/changelog/discounts-and-promo-codes

Feature 3, Custom OAuth scopes for API apps and MCP clients. Reference artwork: assets.illustrations.changelogOauthScopes Custom OAuth scopes are defined in Settings, API to match the resources an integration touches, such as issues:read or cycles:write. Each OAuth app is granted only the scopes it needs, and admins choose which scopes Trestle advertises through OAuth metadata so MCP clients can discover them. The API rejects any token that lacks a scope the request requires. Read more: https://trestle-email.s3.amazonaws.com/changelog/custom-oauth-scopes

Feature 4, Initiatives. Reference artwork: assets.illustrations.changelogInitiatives An initiative groups related projects under one company goal. It shows a rolled-up progress bar across its projects and a health status taken from each project's latest update. Initiatives can be pinned to the sidebar, and an initiative update can post to a Slack channel. Read more: https://trestle-email.s3.amazonaws.com/changelog/initiatives

Feature 5, Trestle CLI. Reference artwork: assets.illustrations.changelogCli The Trestle CLI links a repository to a team with trestle init, then creates and lists issues from the terminal, opens a git branch named after an issue, and relays webhooks to localhost for local testing with trestle webhooks listen. It installs through Homebrew or npm. Read more: https://trestle-email.s3.amazonaws.com/changelog/trestle-cli

Feature 6, Required fields on issue templates. Reference artwork: assets.illustrations.changelogTemplates Any field on an issue template can be marked required. The create dialog blocks submission until every required field is filled, and the same rule applies to issues created from Slack and through the API. Each team can keep up to 20 templates. Read more: https://trestle-email.s3.amazonaws.com/changelog/template-required-fields

Feature 7, Deploy tracking. Reference artwork: assets.illustrations.changelogDeploys Deploy tracking connects a deployment provider or accepts deploys through the API, matches each deploy to the pull requests it contains, and marks the linked issues as deployed. A deploy timeline appears on the project page, and anyone subscribed to an issue is notified when it reaches production. Read more: https://trestle-email.s3.amazonaws.com/changelog/deploy-tracking

Also shipped, a heading followed by a compact list of six inline text links, one per line, in this order:

• Connect OAuth clients with Client ID Metadata Documents. https://trestle-email.s3.amazonaws.com/changelog/client-id-metadata-documents
• Google Workspace directory sync. https://trestle-email.s3.amazonaws.com/changelog/google-workspace-directory-sync
• Sign-in-or-up now works with strict enumeration protection. https://trestle-email.s3.amazonaws.com/changelog/sign-in-or-up-enumeration
• Self-serve SSO for OIDC providers. https://trestle-email.s3.amazonaws.com/changelog/self-serve-sso-oidc
• Hosted sign-in pages for the mobile apps. https://trestle-email.s3.amazonaws.com/changelog/mobile-hosted-sign-in
• Composable profile and workspace settings views in the Trestle SDK. https://trestle-email.s3.amazonaws.com/changelog/composable-settings-views

Closing: the full list of changes is on the changelog at https://trestle-email.s3.amazonaws.com/changelog, and feature requests can be posted or voted on in the community at https://trestle-email.s3.amazonaws.com/community. Sign-off from Maren at Trestle.

The recipient receives this because they subscribed to Trestle updates. Use the Trestle marketing footer: it names Trestle, Inc., gives the postal address 418 Span Street, Portland, OR 97209, and links to Privacy at https://trestle-email.s3.amazonaws.com/privacy, Terms at https://trestle-email.s3.amazonaws.com/terms, and Unsubscribe at https://trestle-email.s3.amazonaws.com/unsubscribe

Use /world/trestle-email for brand chrome and CSS (the product family). Use the absolute HTTPS URLs from tokens.json; do not use /world/ paths as image src. Keep the HTML under 100 KiB.

Dark mode should be supported.

Leave the HTML in output/email.html, a plain-text version in output/email.txt, and the subject in output/meta.json as {"subject": "..."}. Don't include From, To, or Date headers.