Glossaries and models often need more than one set of eyes before they're final. With this release, you can turn any folder into a review workflow, so changes go through discussion before they become the version everyone relies on.
Review Workflow can be turned on for a selected folder in a folder's permissions. When enabled, instead of writing straight to the shared version, all edits land in a development branch. The master branch stays untouched—read-only, stable, and always reflecting the last approved state.
That separation means people can keep working and experimenting without putting the version everyone else depends on at risk.
The day-to-day flow is simple:
Reviewers work from a review sidebar right on the asset. They can accept or reject changes, leave comments, and check the dependencies tab to see what else is affected—no need to hunt for context elsewhere.
If you're merging a model, its glossary entities and relationships are merged along with it, so master never ends up in a half-updated state. By default, anyone can merge, even without full reviewer sign-off—Ellie just gives you a heads-up if nothing's been accepted yet. If you want to be more strict, a set of owners can be assigned to a folder. Only those selected people will be able to merge to master.
Notifications keep everyone in the loop, whether an asset was sent for review, merged, or someone was mentioned in a comment—so reviewers know what's waiting for them and editors know when their work has moved forward.
Review Workflow applies at the folder level and is set up by admins or folder owners in folder permissions. It's a one-way switch for now—there's no reverting a folder back to direct editing—so it's worth confirming with your team before turning it on.
Read the full Review Workflow guide for setup steps and role details, or reach out at support@ellie.ai if you have questions getting started.
