Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Everyone can get access to each Project Area??

Questions
Tags
Users
Badges
Jiong Xie
JAZZ DEVELOPER (71●5●4) Jun 09 '08, 9:26 a.m.
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 :?:

0 votes

6 answers
5,074 views
0 votes

6 answers

Permanent link
sébastien etter
(216●8●7) 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 votes

Permanent link
Jiong Xie
JAZZ DEVELOPER (71●5●4) Jun 09 '08, 10:57 a.m.
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 votes

Permanent link
sébastien etter
(216●8●7) 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 votes

Permanent link
Jiong Xie
JAZZ DEVELOPER (71●5●4) Jun 09 '08, 12:52 p.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


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 votes

Permanent link
Geoffrey Clemm
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER (30.1k●3●30●35) Jun 09 '08, 3:14 p.m.
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 votes

Permanent link
Jiong Xie
JAZZ DEVELOPER (71●5●4) Jun 10 '08, 2:30 p.m.
Hi, Geoff

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

Cheers,
Jiong

0 votes

Your answer

Register or log in 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.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Jun 09 '08, 9:26 a.m.

Question was seen: 5,074 times

Last updated: Jun 09 '08, 9:26 a.m.

Confirmation Cancel Confirm