W21 Product Update: Audit logs
Audit logs are now available – an append-only record of every state-changing action in your organization.
Each change to engines, glossaries, instructions, brand voices, AI reviewers, API keys, members, and roles is captured with the actor, action, target, and request context. The log lives in the dashboard and filters by user, action category, target, and date – so you can see exactly who created, updated, or removed a glossary item three weeks ago, even if the actor is no longer on the team.
Also this week:
Organization invites in the MCP server. Adding a teammate or checking pending invites no longer means switching to the dashboard – the Lingo.dev MCP now exposes invite creation and listing, so an AI assistant can handle it alongside engine configuration.
Recursive globs in i18n.json. The CLI's include and exclude now match files across nested directories, so a single pattern can cover a deep folder tree instead of listing paths by hand.
Full changelog: lingo.dev/changelog
Replies
this is a welcome update. I've often found myself needing a clearer record of changes when investigating issues or reviewing workflows.
@pappu_bind Great addition. For me, audit logs aren't just about security—they're also about learning from past actions and improving process
Audit logs are one of those features that do not feel exciting until a team actually needs them. Then they become essential.
I like that this captures state-changing actions across glossaries, instructions, brand voice, reviewers, API keys, members, and roles. For AI-assisted localization, that trace matters because quality issues can come from many places: the source, the engine, the glossary, the reviewer, or a human edit. Knowing who changed what and when makes the system much easier to trust.