Skip to content

v17.7.0 - Granular permissions & connector flexibility

Choose a tag to compare

View all tags
@KevinJump KevinJump released this 11 Aug 11:49
v17.7.0
937d944

This release splits translation approval from publishing so a third party can handle translations without publish rights, adds a "Lock connector" option to translation sets, and closes a gap where mutating API endpoints didn't check translation permissions at all.

⚠️ Behaviour change on upgrade

Mutating job/node/set/memory/connector endpoints previously only required generic backoffice access. They now require the appropriate translation permission — a group holding only jumoo-send-to-translation can no longer archive, remove or reset jobs, or edit sets.

The new approve/publish permissions are migrated automatically on upgrade — the admin group and every group that already held jumoo-manage-translation are granted both, so no one loses access and there's nothing you need to do. The one exception is a group that was set up with jumoo-send-to-translation only and no manage permission: those groups will see the tightened endpoint checks above, since they never held broader access to begin with.

What's changed

  • Split approve and publish permissions. A translator can now be given rights to approve translated content without also being able to publish it back to the site, so a third party can do the translation work without publish access. Fixes #101.

  • Write endpoints now check translation permissions. Job, node, set, memory, and connector-settings endpoints previously allowed any authenticated backoffice user through; they now require the relevant translation permission.

  • "Lock connector" option on translation sets. A set's default connector is now a starting point rather than the only option — untick "Lock connector" to let editors choose any active connector when creating a job.

  • Bumped the Microsoft, Xliff, Jumoo.TranslationManager.AI, Jumoo.Processing, and Jumoo.Json dependencies.

Published to NuGet.

Assets 2
Loading