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

Treat safe members/permissions as their own individual resource #3

Open
aaearon opened this issue Oct 30, 2024 · 0 comments
Open

Treat safe members/permissions as their own individual resource #3

aaearon opened this issue Oct 30, 2024 · 0 comments

Comments

@aaearon
Copy link

aaearon commented Oct 30, 2024

Is your feature request related to a problem? Please describe.

Safe members/permissions should be treated as their own separate resource and not an attribute of a safe resource nor be limited to one of the template permissions (permission_level).

Describe the solution you would like

Safe members/permissions should be their own resource, separate from the existing safe resource today. Safes can have multiple members with a combination of permissions that fall outside of the provided template permissions/permission_levels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant