Skip to main content
Solved

Team member can give himself write permissions

  • August 11, 2021
  • 1 reply
  • 105 views

Bhanuka Ranaweera
Hero (Employee)
Forum|alt.badge.img+9

Please refer the test flow below ;

• Created Project-Team AA with only one person BX

• Project Access is on and XX is the Manger for project and subproject

• To give a team read access to project documents team AA is added

• BX opens the Project and has only access to subproject “A”, fine!

• XX intention was to grant BX reading rights to the documents attached to this subproject.

• But now... BX can give himself the write permissions.... or even Admin Access?!

Any ideas on this behavior?

Best answer by Peshala Fernando

Hi Bhanuka,

 

It is the designed functionality and I have seen may customers do have this concern. Hence this will be a good functional enhancement in future releases.

Below will be the results as per your question.

1.            As mentioned in the test plan Project Manager will only be permit to enter this combination message appeared when following conditions are matched:

                   Check if the access record is for all sub projects %

                   Check if the logged in user is NOT APPOWNER

                   Check if the logged in user (and the connected person) is NOT the project manager

 

2.            And also "You cannot perform this function because your user does not have access to the project or all the subprojects belonging to the project. Contact the project manager to review your project access privileges." message appeared when trying to add a new record in Access Definition by a user who doesn’t t have appropriate access privileges.

 

3.            But in the reported scenario since user is trying to modify the access rights of a subproject which he already has access and changing the logic of the existing Team Access property will associate high risk as that will have an impact on all other existing customers.

 

Hope this will answer your question.

 

Regards,

Peshala,

View original
This topic has been closed for comments

1 reply

Forum|alt.badge.img+9

Hi Bhanuka,

 

It is the designed functionality and I have seen may customers do have this concern. Hence this will be a good functional enhancement in future releases.

Below will be the results as per your question.

1.            As mentioned in the test plan Project Manager will only be permit to enter this combination message appeared when following conditions are matched:

                   Check if the access record is for all sub projects %

                   Check if the logged in user is NOT APPOWNER

                   Check if the logged in user (and the connected person) is NOT the project manager

 

2.            And also "You cannot perform this function because your user does not have access to the project or all the subprojects belonging to the project. Contact the project manager to review your project access privileges." message appeared when trying to add a new record in Access Definition by a user who doesn’t t have appropriate access privileges.

 

3.            But in the reported scenario since user is trying to modify the access rights of a subproject which he already has access and changing the logic of the existing Team Access property will associate high risk as that will have an impact on all other existing customers.

 

Hope this will answer your question.

 

Regards,

Peshala,


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings