Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rethink default permissions and allowed types #1616

Open
tusmester opened this issue Feb 7, 2022 · 0 comments
Open

Rethink default permissions and allowed types #1616

tusmester opened this issue Feb 7, 2022 · 0 comments

Comments

@tusmester
Copy link
Member

tusmester commented Feb 7, 2022

As we added more types, default containers, user, groups and sample content, the default permissions and allowed child type settings became cluttered and too complicated.

Goal

Clean up default permissions and set default values that let new users work with the repo easily.

Allowed child types

  • what can and cannot be put in a container
  • inheritance: inherited types may be added automatically by adding the 'parent'
  • handle on the ui as a separate allowed childtypes setting view (like permissions editor) not as a field on the edit view
  • search for allowed childtypes (where is it allowed)
  • separate lists for 'set in the ctd', allowed, denied types for a content
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant