![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Stop Read Inheritence from Database Root Topic Summary: Created On: 24-Nov-2003 22:15 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
DOORS 7 - Is there a way to stop inheritence of the Read privilege for "Everyone else" from the Database root to modules or folders created at the root? Since it won't let me remove Read access for "Everyone else" at the database root, I can't figure out a way to stop it inheriting.
We're setting up a new DOORS 7 DB. There will be a small group of individuals, our DB Admins, granted full access to the database root. They are the only ones who will be able to create or delete folders or projects at the root. We want to then explicitly force these admins to assign access rights only to the necessary groups for the new folder or module they created. As it stands now, by default, any folder or project created at the DB root always gets Read access to "Everyone else". I know the Admins can remove that access on the newly created folder/project, but since this is something we always want to do, it would be nice if the Admins didn't have to remember to do it. Thank you. |
|
![]() |
|
![]() |
|
If you remove a user's "R" access to a folder and then give them access to modules under the folder, they would not be able to see those modules in the DB Explorer. I suppose they could open such modules with explicit DXL commands or by following a link, but it wouldn't make much sense.
Denying "R" access to the DB root would mean the users would see nothing, even if you granted it to projects. I guess that's why Telelogic disallows it. Yes, it means your core group will need to explicetely set access to everything they create under the root, specifically denying "R" access to those projects you want to hide. - Louie |
|
![]() |
|
![]() |
|
Well, that's what I was afraid of.
I'm not arguing against removing Read access from the root, I understand the reason for it. I'm just hoping there's a way to prevent that access from inheriting to folders or projects created directly at the root to prevent the Admins from having to do an extra step (a step that might be forgotten). Not that I don't trust Louie (I'm afraid that is the answer), but does anybody else have any other ideas? Thanks again! |
|
![]() |
|
![]() |
|
Cory
The only way around this problem, that I can see, is to write some DXL that will create a project at the database root and set access control to selected users or groups. Using a tool like this your administrators will be forced to include your required access controls. Kind regards John Stevenson john.stevenson@mbda.co.uk ------------------------- John john.stevenson@mbda.co.uk |
|
![]() |
Telelogic DOORS
» Administration
»
Stop Read Inheritence from Database Root
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.