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

Support labelling system protected objects #1

Closed
Firstyear opened this issue Feb 2, 2019 · 0 comments
Closed

Support labelling system protected objects #1

Firstyear opened this issue Feb 2, 2019 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@Firstyear
Copy link
Member

We should have a label or class that prevents (some) modifications, deletions of objects. It should also not be used during creates. This is so that we can mark types as protected to prevent accidental damage.

A consideration is with dynamic schema, we need uses to be able to edit must/may, but not the schema elements themself, so this could be achieved with a system protected access profile, then use that access profile over the schema types.

Perhaps an approach is a self-referring access control that prevents this kind of change?

@Firstyear Firstyear added the enhancement New feature or request label Feb 2, 2019
@Firstyear Firstyear added this to the v1 milestone Feb 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant