It's all about the answers!

Ask a question

Stopping users deleting artifacts in RRC


1
1
Nigel Hopper (1032625) | asked Dec 19 '11, 12:52 a.m.
Simple enough question. In RRC is is possible to only allow certain roles the ability to delete artifacts/work items. I've been through all the settings I can see under permissions and cannot see one.

It seems far to easy to have people do this and I'd like the ability to restrict it to certain people.

Thanks, Nigel.

2 answers



permanent link
Canberk Akduygu (99237371) | answered Dec 19 '11, 9:30 a.m.
in CLM 3.0.1.1 solution there's a capability to do so.

https://jazz.net/downloads/rational-requirements-composer/releases/3.0.1.1?p=news

At the bottom, you can find what you are looking for.

permanent link
Robin Bater (3.4k47) | answered Jul 13 '12, 6:09 p.m.
JAZZ DEVELOPER
In RRC V4, we also added

https://jazz.net/downloads/rational-requirements-composer/releases/4.0?p=news#write-access

You can configure process permissions for each project area and for individual team areas in a project area. You can configure the create, modify, and delete permissions for folders, artifact types, and link types. You can also specify whether users can modify the team ownership assignments that are associated with each folder and artifact. For artifact types and link types, you can configure the permissions at various levels of granularity. For example, for artifacts you might configure the following permissions:
  • Can create artifacts
  • Can create artifacts, but not Vision artifacts
  • Can modify artifacts, but not the Priority attribute for Business Goal artifacts
  • Cannot delete Vision artifacts

For links, you can configure permissions such as "can create links," "can create links, but not Decomposition links," or "cannot delete Decomposition links."

Each project area might be associated with one or more team areas. You can configure the default permissions at the project level. To configure permissions, go to the Team Configuration area in the Permissions section of the project. To assign finer-grained permissions, you can create a team area for the project in which you configure its permissions to be more specific to address your needs.

For example, you might want a particular folder to contain only certain kinds of artifacts. In this case, you might specify at the project level that the create permission is enabled for all of the artifact types, but for a particular team area, the create permission is enabled only for Business Goals. Then, you can associate a specific folder with the team area by right-clicking the folder and clicking Assign Team Ownership. As a result, users will be permitted to create only Business Goal artifacts in the folder.


Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.