Bug #3105
closedAccess rights should be site specific when the same user is in different sites
0%
1.Login to Ewqims
2.Go to Doc pro
3.Give access rights as per the above settings
4.Check the new document request level popup
Description
Access rights should be site specific
Create a folder say Folder A
PPT1
Create a user in PPT1 say user A
In use the folder
Give access rights as no access for the site and inherit the same for groupA and users
PPTSS
Add the user A in the group A of PPTSS
In use the folder
Give access rights as no access for the site and full access for the groupA
When access rights are set like above
In pandora db
In PPT1, Folder A has full access for the user and inherit is checked for the user
Access for site and group shows no access
New document req not showing the folder A
In Blank db
In PPT1, Folder A has full access for the user and inherit is checked for the user
Access for site and group shows no access
New document req is showing the folder A
Files
Updated by Anonymous over 7 years ago
- Subject changed from Access rights should be site specific to Access rights should be site specific when the same user is in different sites
Updated by User Admin over 7 years ago
- Status changed from Open to Future Release
This issue might have more impact, and QA is in the last lap of testing hence this issue is moving to Future release. Issue discussed with Sabu.
Updated by Anonymous over 7 years ago
- Project changed from EwQIMS SP710 to EwQIMS SP730
- Build Cycle changed from Cycle 6 to Cycle 0
- Issue Dependency set to SP711
Updated by User Admin almost 7 years ago
- Status changed from Future Release to Resolved
Updated by User Admin almost 7 years ago
- Status changed from Resolved to Yet to Verify
Updated by Anonymous almost 7 years ago
- Project changed from EwQIMS SP730 to SP810 - QA build
- Issue Dependency changed from SP711 to SP730
- Dev Commitment to Resolve in: set to SP810
Updated by Anonymous over 6 years ago
- Status changed from Yet to Verify to Not Resolved
Updated by Jacqueline Antonette over 6 years ago
- Status changed from Not Resolved to Resolved
Updated by Anonymous over 6 years ago
- Status changed from Resolved to Yet to Verify
Updated by Anonymous over 6 years ago
- Status changed from Yet to Verify to Not Resolved
Updated by Jacqueline Antonette over 6 years ago
- Status changed from Not Resolved to Resolved
Updated by Anonymous over 6 years ago
- Status changed from Resolved to Fixed with Hotfix
Updated by Anonymous over 6 years ago
- Status changed from Fixed with Hotfix to Resolved
Updated by Anonymous over 6 years ago
- Status changed from Resolved to Yet to Verify