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

Access Control for Custom Actions and Custom Pages #2877

Closed
VinayaSathyanarayana opened this issue May 3, 2020 · 1 comment
Closed

Access Control for Custom Actions and Custom Pages #2877

VinayaSathyanarayana opened this issue May 3, 2020 · 1 comment

Comments

@VinayaSathyanarayana
Copy link
Contributor

Feature request

How should one implement access control for Custom Actions and Custom Pages?

@MadeByMike
Copy link
Contributor

Access control relates to lists and fields so you'd get access control on these for free, when executing graphQL queries from the client.

There is not really a concept of access control for pages in the Admin UI. It only attempts to validate and remove fields where appropriate. For example it can know update: false should be removed but it assumes that update: () => false is true, and will render a field that fails on update.

At the moment we have no plans to change this. So for anything beyond the above or not related to lists and fields you'd add your own access control checks and bake these into the page.

It's a neat little demo idea. And it might be possible to make use of the authenticated user to do that. If you create and share a demo this might generate so idea for how we can make it easier for people wanting to do this.

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

No branches or pull requests

2 participants