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

Give granular control over who can perform tasks in custom web parts #765

Closed
pzljanb opened this issue Sep 7, 2022 · 3 comments
Closed
Assignees
Labels
customer funded Issues funded by customer enhancement Request that will enhance the product priority: high Issue with high priority
Milestone

Comments

@pzljanb
Copy link
Contributor

pzljanb commented Sep 7, 2022

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:

  • Edit project properties
  • Alter phase
  • Project status (optional)

Roles that must be selectable for this configuration are the following:

  • Roles from project properties:
    • Projectmanager
    • ProjectOwner
    • Project support
    • Gains responsible
  • Groups defined on portfolio level in 'Tillatelseskonfigurasjon'

As a "fallback" solution we can keep 'IsAdmin' as is, and add the new functionality in this Issue as a supplement.

@pzljanb pzljanb added the enhancement Request that will enhance the product label Sep 7, 2022
@Remi749 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 Remi749 changed the title Replace 'isAdmin' used for access control within PP365 Replace 'isAdmin' usage for access control within PP365 Sep 7, 2022
@pzljanb

This comment was marked as outdated.

@okms okms added this to the 1.7.0 milestone Sep 14, 2022
@okms okms added the funding required Requires funding for development label Sep 14, 2022
@pzljanb
Copy link
Contributor Author

pzljanb commented Sep 20, 2022

Kontrollerer nå denne med brukere av portalen

@pzljanb pzljanb added customer funded Issues funded by customer and removed funding required Requires funding for development labels Sep 21, 2022
@pzljanb pzljanb added the priority: high Issue with high priority label Sep 30, 2022
@pzljanb pzljanb assigned Remi749 and olemp and unassigned Remi749 Sep 30, 2022
@okms 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 added a commit that referenced this issue Oct 4, 2022
@olemp olemp mentioned this issue Oct 4, 2022
6 tasks
olemp added a commit that referenced this issue Oct 4, 2022
@olemp 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
olemp added a commit that referenced this issue Oct 5, 2022
@olemp
Copy link
Collaborator

olemp commented Oct 7, 2022

Completed

@olemp olemp closed this as completed Oct 7, 2022
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
Projects
None yet
Development

No branches or pull requests

4 participants