Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Link Module Access Rights
Topic Summary:
Created On: 9-Oct-2008 17:32
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
Answer This question was answered by Kevin Murphy, on Monday, October 13, 2008 1:13 PM

Answer:
Laura,

Giving a user D access to a module means that they can delete the module.

You need MC access to an object in a module in order to create a link from that object, right? So my method is to keep things simple--I give "Everyone else" RMC access to all link modules.

If I don't have rights to the source module, I can't create a link, even if I have RMCDA to the link module.

This keeps link module access right management extremely simple.
 9-Oct-2008 17:32
User is offline View Users Profile Print this message


Laura Doyle

Posts: 16
Joined: 15-Sep-2004

What are the correct rights of users for link modules?
I have all my link modules in one folder called Link Modules. I had given the groups the RM access rights on link modules which was fine. But one user tried to clear suspicious links from her module it wouldn't let her. So I gave the group RMCD access rights, is this correct? I just don't want to give more access then I have to.
Thanks in advance for your help.
Report this to a Moderator Report this to a Moderator
 10-Oct-2008 14:42
User is offline View Users Profile Print this message


Kevin Murphy

Posts: 120
Joined: 16-Jan-2008

Answer Answer
Laura,

Giving a user D access to a module means that they can delete the module.

You need MC access to an object in a module in order to create a link from that object, right? So my method is to keep things simple--I give "Everyone else" RMC access to all link modules.

If I don't have rights to the source module, I can't create a link, even if I have RMCDA to the link module.

This keeps link module access right management extremely simple.

-------------------------
Kevin Murphy
http://www.baselinesinc.com

Edited: 10-Oct-2008 at 14:45 by Kevin Murphy
Report this to a Moderator Report this to a Moderator
 10-Oct-2008 15:16
User is offline View Users Profile Print this message


Pekka Mäkinen

Posts: 276
Joined: 18-Mar-2004

Link creation from a source object needs at least "RM" access to that object. Linkset creation in a link module needs at least "RMC" access to link module and link creation through an existing linkset needs "RM" access to link module. So the minimum you need to create a link (if the linkset exists already) in "RM" both to source module / object and link module.

Though this does not answer why the clearing of suspicious links needs more than that...

Edit: Tried this setup with a link module with "RM" access and to clear a suspicion on link DOORS gives out an error message "Create rights are required on link module" (this on DOORS 8.3).

-------------------------
Pekka.Makinen@softqa.fi
SoftQA Oy -http://www.softqa.fi/

Edited: 10-Oct-2008 at 15:19 by Pekka Mäkinen
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.