Read-only role, after save option and more
Today we added two small features, new integrations and also fixed a few bugs.
Read-only role
One highly requested feature after we introduced frontend authentication was a read-only role. Essentially a role that was only allowed to view the frontend (after authenticating), but without any access to edit or even view the workspace backend in any way whatsoever.
This is now possible. Roles can be set to new (invited) users, as well as existing users.
After-save redirect
After saving an article - either as a draft or published, you'll be automatically redirected to the category overview. It is now possible to change this behavior. As an alternative, you can now choose to stay in the article edit view after saving. This is a global setting per user, so if you have multiple workspaces, this change will apply to all of them. To change this setting, go to your account settings at https://eniston.io/settings and find the section "Redirect mode".
New integrations
We also added 3 new integrations:
- Brevo Conversations
- ChatNode AI
- Tawk.to
Bug fixes
And last but not least, we fixed a few bugs. Two of them were pretty annoying if you encountered them.
When changing the title of an article from "A" to "B" and later back to "A", the slug of that article would be changed from "domain.com/category/a" to "domain.com/category/a-1". If you manually linked to that article, a 404 would be thrown. This should be fixed.
We also fixed a bug when creating a new article within a category (not via the + symbol in the sidebar). The active category was not pre-selected and upon saving the article, it would be stored in a different category (the first one that was created within the workspace). This should now be fixed as well.