Hi guys, I am little confuses about the permissoin definition with "Pages" prefix, such as "Pages_Administration_Roles_Create", instead of it with "Administration_Roles_Create" will more simple, why add the prefix? Is there a reason to do that?
3 Answer(s)
-
1
Hi, using
Pageprefix is to indicate view permission.There are some cases where view permissions have to be separated from API permissions.
also certain view permission might not present at API permission level. e.g.
View Dashboardview permission cannot be directly mapped to API, instesd it can be mapped a view controller.Markdown is supportedCopy & paste or drag & drop images (max 30 MB per image) -
0
@ryancyq, Thanks for your explaination. In this case should I different the permissions between MVC controllers and API Services, this also will make the permission definitions more complex and let user confuses on permisson management UI, which pattern you recommend?
Markdown is supportedCopy & paste or drag & drop images (max 30 MB per image) -
1
Hi @trendline it depends on your API requirements.
In general if your API permissions do not differ much from your view permissoon, you can use the same permission.
However, if you intent to expose the API to third party developer or external application, you can consider using different permission sets
Markdown is supportedCopy & paste or drag & drop images (max 30 MB per image)
