It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884

question asked: Jun 09 '08, 9:26 a.m.
question was seen: 4,973 times
last updated: Jun 09 '08, 9:26 a.m.

Related questions

Everyone can get access to each Project Area??

0
Jiong Xie (71●5●4) | asked Jun 09 '08, 9:26 a.m.
JAZZ DEVELOPER
Hi,all

I'm encountering the following problem.
There are several defined project areas on the Team Server beta3. One user tries to connect a project area which he is not a member of.
I expected that this user would not get access to that project area. But in fact, he's connecting to it successfully and even may delivery change-set to the repository.
Is it correct? :?
How can I define the different permission to project areas :?:

6 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
sébastien etter (216●8●7) | answered Jun 09 '08, 10:19 a.m.
You cannot restrict access to a project area.

If user doesn't have a Developer Client Access License, it will not be able to deliver change-set.

Moreover you can set Roles permission in Process Configuration (concerning source code : Deliver, Save Component, Save Stream)

Sbastien Etter
ESD/Alcatel-Lucent
0
permanent link
Jiong Xie (71●5●4) | answered Jun 09 '08, 10:57 a.m.
JAZZ DEVELOPER
Thx a lot!

So that means I have to customize my process for each team in the project area in order to restrict the user behavior, right?
0
permanent link
sébastien etter (216●8●7) | answered Jun 09 '08, 11:10 a.m.
You have to customize your process just one time :

In your Project Area click Process Configuration tab, in Team Configuration section click on Permissions and then restrict access on Source Control actions. Next, restrict access on Process actions in order to deny process customization by users.

Each team will have this process.

Sbastien Etter
ESD/Alcatel-Lucent
0
permanent link
Jiong Xie (71●5●4) | answered Jun 09 '08, 12:52 p.m.
JAZZ DEVELOPER
You have to customize your process just one time :

In your Project Area click Process Configuration tab, in Team Configuration section click on Permissions and then restrict access on Source Control actions. Next, restrict access on Process actions in order to deny process customization by users.

Each team will have this process.

Sbastien Etter
ESD/Alcatel-Lucent


Thx! I'll try it out.
BTW, sometimes we do want to only let the authorized users get access to the certain project areas. How can I realize this scenario? Otherwise, the project area concept would not make much sense.

Anyone has idea or experience?
0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Jun 09 '08, 3:14 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In Team Concert 1.0, you can control write-access on a per-project-area
basis, but read access is controlled only at the repository level.

We know that read permissions need to be defined at a finer granularity
than the repository level, but we didn't have time/resources to schedule
that work for the 1.0 release.

Cheers,
Geoff

jessekiki wrote:
BTW, sometimes we do want to only let the authorized users get access
to the certain project areas. How can I realize this scenario?
Otherwise, the project area concept would not make much sense.

Anyone has idea or experience?
0
permanent link
Jiong Xie (71●5●4) | answered Jun 10 '08, 2:30 p.m.
JAZZ DEVELOPER
Hi, Geoff

reasonable so far...
I'm just looking forward to seeing this improvement in the next release.

Cheers,
Jiong

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.