-
Notifications
You must be signed in to change notification settings - Fork 177
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
Labels
enhancement
New feature or request
Milestone
Comments
This was referenced Apr 30, 2022
This was referenced Dec 15, 2022
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
The text was updated successfully, but these errors were encountered: