The power is in your hands this month, literally. Hmmm, or maybe fingertips is more accurate.
Anyhoo, let’s get to the meat of the matter (note to self: don’t write this at lunchtime).🥩
This month, we released updates to Lokalise permissions. Sounds like such a small change but it’s a huge deal. Those nodding along will know what I mean.
For those who don’t let’s go over what this change could mean for you.
Managing permissions in localization should be a simple piece of the puzzle. However, existing permissions inside Lokalise were causing disruptions.
So, we set out to solve these problems. The result?
Improved permission management gives you more control to streamline workflows, safeguard critical actions, and keep projects running smoothly.
Here’s everything you need to know about what’s changed and why it matters.
First, let’s give it up for the Contributors page, which got a complete overhaul. You’ll still add contributors to your project as usual (and team owners are still part of every team project), but now it’s a lot easier to understand roles and fine-tune permissions.
Now you can choose from roles like Content Manager, Localization Manager, and Developer, or create a custom role. Each role gets a predefined set of permissions, like upload files, manage keys, merge branches, and delete glossary terms, which you can customize based on your preferences.
It’s now possible to specify who gets to view or edit each language within your projects. This means better organization, fewer unwanted changes, and teams that work together without stepping on each other's toes. Hoorah!
Introducing bulk actions for everyone! Not just admins. Don’t forget to specify which bulk actions users can and cannot perform, from translating all keys in multiple languages to adding tags to multiple keys in one go. Your localization operations are about to get even faster.
⁉️ Wait, bulk actions for everyone?
Yes — but with just the right options for each user, tailored to each user’s permissions, keeping workflows smooth and secure.
Accidents happen – we’re all human after all. So we made it easier for you to minimize mistakes by giving you the power to restrict who can manage high-impact actions, like merging branches of a project, contributing to the main branch, or adjusting glossary terms. Protect your brand, terminology, and branches with granular permissions, and have one less thing to worry about.
Who can merge branches or edit the main branch?
That’s up to you, but make sure you limit who can merge or edit the main branch to one or two people, to avoid unfavorable surprises.
Adding users to multiple projects and tailoring permissions to their roles is more straightforward and less repetitive – with just one click you can add contributors to multiple projects. If you’re importing teams from other projects, you can now exclude certain users – making compliance with privacy and security standards a priority.
💡 Good to know
• If you add someone individually to a project, only their individual permissions apply, not their user group permissions.
• Importing users from another project? You can now exclude anyone who doesn’t need access—because privacy matters.
Last, but not least, last activity insights let you easily spot inactive users and keep your team lean.
With these updates, you’ll have greater flexibility when it comes to managing teams and putting languages, projects, and permissions, in the right hands.
What’s more, you’re setting your team up for success from the very start.
Ready to get started? Check out our comprehensive guide and discover how these changes can make a difference in your workflows. And as always, we’re here to help if you have any questions or feedback.
And that’s a 🌯… Off to grab some lunch now.
Author
Meet Rachel, our Content Manager and Lead Copywriter, who pivoted from advertising to SaaS and has never looked back.
Born and raised in the UK, Rachel has lived in London, Paris, Buenos Aires, and now Brussels. Through city-hopping, traveling, and her studies in French and Journalism, she’s picked up French and Spanish, and is now inventing her own language with help from her three-year-old daughter: Franglospanish!
Outside work, Rachel enjoys making (and eating) fresh pasta, drawing, and spending as much time as possible outside, cycling, hiking, or running.
We’ve been dusting off the cobwebs this month, and getting the back end back on track with API improvements that will surely make us the record holder of fastest file downloads—blink and you’ll miss ‘em.
Great news for our Figma community! You can copy and paste Frames or Artboards without having to manually link keys. This means you can iterate quickly, ensure consistency, and save valuable time. What's changing with our Figma plugin? All translation keys will be linked when duplicating design elements. This means: When you copy and paste Frames or Artboards, all keys wil
We have lots of updates for you (and it’s only February), so let’s cut to the chase. First up, localization workflows that manage themselves Let your localization projects flow solo with Workflows We're excited to announce the release of Lokalise Workflows—no-code workflow templates with multiple steps that you set up once, so tasks run automatically and without delay. Lokalise Workflows changes how you manage projects—you barely need to manage them! Inst
Localization workflow for your web and mobile apps, games and digital content.
©2017-2025
All Rights Reserved.
