Feature Request: Combined "Save & Approve" Button for Proofreaders within Filtered Views

Hi everyone,

I’d like to suggest a small but impactful addition to the Editor workflow: a combined Save & Approve button, visible only to users with Proofreader permissions or higher.

Current workflow:
When working under a filtered view (e.g., QA Issues > All, or Unsaved Translations), editing and saving a string causes it to disappear immediately from the list, since it no longer matches the active filter. To approve it, I then have to switch filters, locate the string again, and approve it separately — doubling the effort.

What already exists (and works well):
I’m aware of Auto-approve and the recently improved Approve button placement right after Save (April 2026 update). Both are helpful, but they don’t fully address this specific case.

Auto-approve approves everything automatically, which isn’t always desirable, especially when working in batches where context comparison across similar strings is part of the quality check before committing to an approval.

The proposed addition:
A Save & Approve button (shown only to Proofreaders and above) that saves and approves in a single action. This would be especially useful when:

  • Correcting confirmed errors or false positives under QA filters
  • The translation is already verified and context-confirmed
  • The proofreader wants to avoid a second pass through a different filter

This keeps full manual control for cases requiring more review, while eliminating unnecessary navigation for cases that are clearly resolved.

Happy to hear if others have faced the same friction. Thanks for considering it!

Hi @fateh-bouyahiaoui

We have auto-approval option already in-build:

Would that be the one you’re looking for?

Or maybe a shortcut to approve?

Hi Dima,
It seems you didn’t read my feature request thoroughly.

I was hoping for a genuine discussion on optimizing the proofreader workflow and Crowdin’s user experience, unless creating new feature requests is simply unwelcome anymore in the Crowdin Community.

Fateh,

Thanks for clarifying your thoughts on this.

When I looked at your suggestion initially, I was mainly thinking about it from the perspective of UI layout and overall platform complexity. Our main goal is always to keep the editor clean and avoid doubling up on features or workflows that the platform already supports in other ways.

About improvements, we are definitely happy to hear any suggestions for improvements. We love getting feedback from our users because it helps us understand how teams interact with the editor in real-world scenarios.

I really appreciate you taking the time to share your perspective on how to make the proofreading workflow smoother.

I will share the Save+Approve idea with our product team so they can consider it for future design updates :slightly_smiling_face:

upd: Submitted a request, CN-66652 internal number

1 Like