You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[x] edit experience / UI
[x] admin experience UI
[x] Content Types or data management
Feature request
Is your feature request related to a problem? Please describe.
For 2sxc toolbars to show, edit permissions on DNN must be given, and the persona bar must show.
Describe the solution you'd like
Work with the new DNN10 permissions settings so that 2sxc content editors can work without the persona bar showing and without resorting the public forms.
The text was updated successfully, but these errors were encountered:
All permissions that allow editing also allow the persona bar, so edit page access.
I really just whish there was a way to create a content editors role that can access the 2sxc toolbars to crud any item, but no PB involved. Public forms is a path I would like to stop taking.
Just for context: the new, restricted DNN roles still have the pages, so that content-editors could create / move pages and also work with global site assets.
Are you sure that you would want them to not have that?
I understand that the sidebar could be "in the way" but it does provide some basic features a content editor needs...
Let's replace the concept of "content" for something clearer.
They are data editors. CRUD for entities.
They must never even get near web design, page editing or module editing. Something only puplic forms achieve for now.
This Feature is About
[x] edit experience / UI
[x] admin experience UI
[x] Content Types or data management
Feature request
Is your feature request related to a problem? Please describe.
For 2sxc toolbars to show, edit permissions on DNN must be given, and the persona bar must show.
Describe the solution you'd like
Work with the new DNN10 permissions settings so that 2sxc content editors can work without the persona bar showing and without resorting the public forms.
The text was updated successfully, but these errors were encountered: