-
Notifications
You must be signed in to change notification settings - Fork 16
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
Give granular control over who can perform tasks in custom web parts #765
Labels
customer funded
Issues funded by customer
enhancement
Request that will enhance the product
priority: high
Issue with high priority
Milestone
Comments
Remi749
changed the title
Replace 'Is admin' used for access control within PP365
Replace 'isAdmin' used for access control within PP365
Sep 7, 2022
Remi749
changed the title
Replace 'isAdmin' used for access control within PP365
Replace 'isAdmin' usage for access control within PP365
Sep 7, 2022
This comment was marked as outdated.
This comment was marked as outdated.
Kontrollerer nå denne med brukere av portalen |
pzljanb
added
customer funded
Issues funded by customer
and removed
funding required
Requires funding for development
labels
Sep 21, 2022
okms
changed the title
Replace 'isAdmin' usage for access control within PP365
Give granular control over who can perform tasks in custom PP365 WebParts
Sep 30, 2022
olemp
added a commit
that referenced
this issue
Oct 3, 2022
olemp
changed the title
Give granular control over who can perform tasks in custom PP365 WebParts
Give granular control over who can perform tasks in custom web parts
Oct 5, 2022
Completed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
customer funded
Issues funded by customer
enhancement
Request that will enhance the product
priority: high
Issue with high priority
Is your feature request related to a problem? Please describe.
Currently we only check if a user is Site Collection administrator when deciding wether or not they are allowed to perform certain tasks within our custom WebParts. For example to edit project properties, you need to be Site Collection administrator.
This is too blunt a tool for many larger customers, where only a select few are Group owners (and thus are admins). We should allow our customers to allow other functions such as Project owner, Project leader or some custom roles defined centrally, to use these features.
Describe the solution you'd like
There is need of a more granulated access control for these functions:
Roles that must be selectable for this configuration are the following:
As a "fallback" solution we can keep 'IsAdmin' as is, and add the new functionality in this Issue as a supplement.
The text was updated successfully, but these errors were encountered: