Feature requests

Add an option to filter keys directly by specific import batches so users can easily manage and review newly imported translation files.

Currently, we export all translations, even empty ones. However, it would be better to automatically export only non-empty translations without requiring the ONLY_TRANSLATED option, allowing Android's native fallback mechanism to handle the rest.

DeepL benefits from descriptions if they are written in the same language as the source or target language. Currently, we do not have an option to store additional metadata for translations - only keys.

Currently, all projects have separate configurations. We could add an option to create common settings at the group and/or organization level. Related: https://feedback.simplelocalize.io/feature-requests/p/shared-across-projects-auto-translation-excluded-words-or-phrases

Introduce a Git-like versioning and branching system within the Translation Editor, allowing teams to create isolated environments for translation updates while maintaining a simple, non-technical user interface.

Currently, the 'Publish translations' permission grants users the ability to publish across all environments. The goal of this feature request is to introduce environment-specific, granular permissions.

Currently, any user within an organization can sign in to SimpleLocalize. This feature request aims to add an "invitation-only" toggle so administrators can maintain an allowlist of permitted users. When enabled, only explicitly invited users will be allowed to sign in and get access to the team/organization. Alternative approach: Allow open account registration, but mark new accounts as "pending" until approved or rejected by a team administrator.

It would be useful, if the default prover could be specified per project. Currently the app always falls back to google translate, and I have to set it manually every time to my desired provider (openai)

Add an option to change the default nesting delimiter (.) to another char or string.

Currently all JSON formats don't benefit from key types configured in the key details. The goal of this task is to add export option that will automatically convert translations into selected types.