![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Access rights for Views Topic Summary: default rights don't include admin user Created On: 6-Oct-2005 18:26 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I'm having a problem with the way DOORS 7.1 assigns access rights to a custom view.
It seems that the default rights for a Public View are to give full access to the original creator and Read Only access to everyone else. Unfortunately, this means that even an Admin user only has Read access!
I'd vastly prefer that the Admin user always be able to manage the view. We often use standardized view names, and sometimes a particular view needs to be modified by someone other than the original creator.
Really, it'd be nice if DOORS would simply default to making the view permissions 'inherit from parent'.
Anyone else encounter this behavior? (Sorry if this topic has been covered elsewhere, but the forum's 'search' feature is broken right now.)
-Brian
Edited: 6-Oct-2005 at 18:30 by Brian Matis |
|
![]() |
|
![]() |
|
Workaround solution posted 5 july
quote::: Your problem is caused by using the standard view as a starting point. The standard view, is by definition READ-ONLY to everyone. DOORS creates new views as private by default, so when you set it as public it merely confirs read access to everyone else. Do this: Create a new view, say default view and explicity set the access right to inherited or RMCDA for all or whatever. Then use this view as the starting point for new views, setting them pblic as you go. ------------------------- Tony Goodman agoodman@hisltd.com endquote:::: https://support.telelogic.com/en/doors/forums/messageview.cfm?catid=58&threadid=2468&highlight_key=y&keyword1=view ------------------------- Cliff Bly |
|
![]() |
|
![]() |
|
Thanks for the link Cliff! That's a decent workaround.
Although, it looks like we shouldn't set new views as Public, since that will just reset the access rights to Read Only for everyone except the creator. Instead, the view must be left as Custom.
-Brian
|
|
![]() |
|
![]() |
|
I have a followup to this post. We have an employee that created many DOORS modules and created views for them. This employee has moved on, and we are left with a bunch of views that we cannot edit or delete since he is the only one with RMCDA permissions. Is there a way to give permission to another person (maybe the admin) to change or delete this view?
|
|
![]() |
|
![]() |
|
quote:And that's the exact reason why I worry about the current behavior! I haven't had to do this yet; but the best solution I have is for the Admin user to change the employee's password, log in as that employee, then change the permissions on the views. |
|
![]() |
|
![]() |
|
The database "administrator" user has RMCDA access to everything. Change the password as Matis has said, but if that user has been deleted then the "administrator" has to do it.
|
|
![]() |
Telelogic DOORS
» General Discussion
»
Access rights for Views
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.