UPDATESOverview

August 2026 release notes

August added Vault Projects for per-environment keys, sign-in with Google, Microsoft, or GitHub, and a Closure email inbox per team. Wiki pages can link to tickets, capture a resolution, and import Markdown. Forge initiatives got a status board and optional auto-completion, and Closure gained ticket archive, groups, and time tracking without the Customers module.

August highlights

Vault Projects stores per-environment keys in a matrix: reveal or export a value, review history, grant access, and import from a file. Missing keys show as gaps. Vault CLI can target a project and environment when writing values. Credentials also gained a first-class authenticator setup with a live rotating code.
People can sign in with Google, Microsoft, or GitHub. Invite links preview the team and put the person on it after they set a password or sign in.
Closure can accept tickets by email: each team gets an intake address, unknown senders land in quarantine, and technicians can hide attachments from the requester.
Wiki pages link to Closure tickets as reference, solution, or reply; completed tickets can capture a resolution into the Wiki. Spaces and folders can import Markdown or a zip, including Obsidian-style links.
Forge initiatives use one board column per status with drag-and-drop, can suggest or auto-complete when the work is done, and show delivery by developer. Coding sessions accept a spend ceiling and an effort level.
Closure technicians can archive completed tickets, filter and chart by group, turn off a category, edit a message for 15 minutes, and run a ticket clock without the Customers module. The mobile app opened a unified inbox for tickets and issues.

Availability

Availability depends on your plan, your role and permissions, and enabled modules. Vault Projects and authenticator codes need Vault. Email intake, archive, groups, and the ticket clock need Closure — time tracking without Customers is a Closure setting. Wiki links and Markdown import need Wiki. Initiative completion, delivery metrics, and coding-session budgets need Forge and, for some settings, admin access. Social sign-in appears when providers are enabled. Boleto and fiscal profile apply to Brazilian billing.

August 27-31, 2026

Search the Wiki from a ticket, link a page as reference, solution, or reply, and capture a completed ticket into a Wiki page.
Wiki spaces and folders import Markdown files or a zip, with preview, title overrides, and Obsidian-style link rewrite.
Closure email intake: a per-team address, quarantine for unknown senders, registered redirects, and settings for the team.
Technicians can mark ticket images as hidden from the requester.
Ticket messages can be edited for 15 minutes; board filters accept more than one value at once.
The Closure dashboard charts tickets opened by group.
Closure can run a ticket clock without the Customers module — no billing chrome.
Members and teams can have a picture.
Linked pull requests show the repository name on the list and the pull-request page.
Billing settings let you choose who receives invoices, store the fiscal profile, and generate a boleto with the invoice for Brazilian billing.
Closure settings save as you change them.

August 24-26, 2026

Technicians can archive a completed Closure ticket and browse archived tickets from the list; archive is a ticket status.
Closure board, list, and dashboard filter by group, and requester groups appear on the ticket.
Ticket categories can be turned off so the create form no longer offers them.
Inviters can pick groups when sending an invite, and the member joins those groups on accept.
The daily Tasks digest shows fail and not-done streaks.
Mobile inbox gained a queue selector for technicians.

August 18-21, 2026

The Forge initiatives board uses one column per status, with drag-and-drop to change status.
Initiative progress bars show the mix of issue statuses.
Cycle overlap conflicts show what collided and offer a one-click fix.

August 13-17, 2026

Any Forge member can raise a blocker, not only the assignee.
Silent device digest emails name the device owner.
Forge domain filters include a No domain bucket.
Cycle pages show delivery by developer across recent cycles.
Forge settings can suggest or automatically complete an initiative when its issues are done, with a readiness panel on the initiative.
Coding sessions accept a spend ceiling and an effort level; a session that hits the ceiling pauses instead of failing.
MCP clients can turn a ticket into a Forge issue and write coverage and supplier records.

August 5-8, 2026

The mobile app replaced the tickets tab with a unified inbox for tickets and issues, with search and folder filters.
WhatsApp tickets can be re-evaluated as more messages arrive: category, severity, and description update, and a clarification question waits for the quieter pass.
MSP teams can assign or change a member's client.
After an Inventory import, the wizard shows what was created, anything worth acting on, and a path to Movitera Link.
Embedded AI actions default to a smaller, lower-cost model, and published model prices were updated.

August 1-4, 2026

Sign in and sign up offer Google, Microsoft, and GitHub when those providers are enabled.
Vault Projects: create a project, manage environments, reveal or export a value, grant access, import a file, and promote an environment-bundle credential to a project. Vault CLI addresses a project and environment when writing values.
Vault credentials gained a dedicated authenticator setup: paste a URI or key, preview the current code, then reveal, copy, replace, or remove it on the credential.
Invite email lands on a preview of the team; new people set a name and password and join, and existing accounts sign in to accept.
Forge can keep an issue from moving when a linked pull request is accepted until the issue is marked tested.
Remote sessions show when a Windows elevated window cannot be controlled.