Actions
Bug #9622
closedWhen the user has module admin rights alone for the particular site say siteA and not having group rights in site A , then the documents should not be displayed in TOC
Start date:
10/30/2018
Due date:
% Done:
0%
Estimated time:
Steps To Reproduce:
1.Login as the user who has module admin rights for site a and site b. In site a, the user has groups rights and in site b the user doesnt be a part o f group
2.site a the user has full access for the documents in level a
3.site b the level a from site a is integrated
4.Login as the user a
5.check the site b where the user doesnt have group access
6.check the TOC
MODULES:
DOCPRO
Build Cycle:
Cycle 6
Customer:
Issue Dependency:
Dev Commitment to Resolve in::
Description
When the user has module admin rights alone for the particular site say siteA and not the group rights in site A , then the documents should bot be displayed in TOC
Files
Actions
#1
Updated by Anonymous over 6 years ago
- File ScreenShot2662.png ScreenShot2662.png added
- File ScreenShot2661.png ScreenShot2661.png added
Updated by Anonymous over 6 years ago
- Subject changed from When the user has module admin rights alone for the particular site say siteA and not the group rights in site A , then the documents should bot be displayed in TOC to When the user has module admin rights alone for the particular site say siteA and not having group rights in site A , then the documents should bot be displayed in TOC
Updated by Anonymous over 6 years ago
- Subject changed from When the user has module admin rights alone for the particular site say siteA and not having group rights in site A , then the documents should bot be displayed in TOC to When the user has module admin rights alone for the particular site say siteA and not having group rights in site A , then the documents should not be displayed in TOC
- Steps To Reproduce updated (diff)
Updated by Jacqueline Antonette over 6 years ago
- Status changed from Open to Resolved
Updated by Anonymous over 6 years ago
- Status changed from Resolved to Not Fixed with Hotfix
Updated by Jacqueline Antonette over 6 years ago
- Status changed from Not Fixed with Hotfix to Resolved
Actions