nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can we hide a branch in teamsite?

dpmv

We have a requirement whereby a specific branch is hidden to all other teamsite users other than the members of this branch.

Thanks in advance.

Find more posts tagged with

Comments

nipper

Totally hidden as in not even able to see the branch name, not that I know of. But you can easily restrict access so they cannot see any content within the branch (Workarea/Staging/Edition)

ccprofessional

branch_security=on

pciDrillDown2.rptdesign

Ambuj

branch_security=on

will this completely hide the branch from other members?

Adam Stoller

will this completely hide the branch from other members?

Only if the users do not have any access to the branch directory (that includes read, execute, etc.

kaalraa

will this completely hide the branch from other members?

Will hide for the members who does not have the Read access even. In simple words - No Access at all.

ccprofessional

will this completely hide the branch from other members?

What is the documentation for?
Do you have your diapers on?!

artor

set the branch_security=on and workarea_security=on in iw.cfg file and all the branches that you have in teamSite set the permission to rwx-rwx-000.
permission depends on your environment and 000 says No access, same thing for workarea.

Regards,
A

nipper

set the branch_security=on and workarea_security=on in iw.cfg file and all the branches that you have in teamSite set the permission to rwx-rwx-000.
permission depends on your environment and 000 says No access, same thing for workarea.

Also, plan on time for debugging, you will see *something* outside fail. It may be a template, a CGI, a workflow, things are going to fail due to the very restrictive permissions. Plan on it and plan on time to figure out what and why.

Andy

CRB

om 6.7.1 w2k3
i tried the branch/workareasecurity=on and didnt work for me... then iwreset -a and didnt seem to make any difference.

as you know in 6.7.1 we have this new branch iwadmin and i was trying to see if i can hide it... it seems that everybody can see it and browse it, and edit files. i also noticed that on branch iwadmin properties theres iweveryone group which has reviewer role so that might be the reason TS allows everybody to see the iwadmin...
i logged in as a master, and i still dont see anywhere to remove the group "iweveryone" from iweveryone branch

moonkhanna

Go into the properties of iwadmin branch. You can edit roles there. TS 6.7 provides branch based roles. So for each branch you can specify which group would have which role on the branch

CRB

i did that... i created a group "admin_group" has just my usrrname as a member... and i changed the properties of iwadmin branch by deleting iweveryone group with role reviwer as a member/user of the branch, and i add the new group "admin_group" with admin role, i also uncheck the "unherit from parent" check box, and reset... but i still can see the iwadmin branch and browse it when i login with a user that is not a memmber of the "admin_group", the only change is that if you are not member of "admin_group" you can preview or edit the files.. but u can browse around the iwadmin branch and of course the branch is still visible to everybody!

ccprofessional

i tried the branch/workareasecurity=on and didnt work for me.

I hope you are not using that syntax.

What's in your iw.cfg?

moonkhanna

also, make sure you do not have anyone in the reviewer role. Group in the reviewer role will be able to see the branch and its contents

CRB

I hope you are not using that syntax.

What's in your iw.cfg?

lol

no, i have this way:
branch_security=on
workarea_security=on

suj

I had this problem with win2k and 6.1. We had to explicitly deny access from the folder properties. I know this may not be a good solution but we had to do this as the customer was adamant and we could deny access to ceratin groups.

SBR

Yes we can achive this by using Unix ACL`s( chmod 770) provided if it is a solaris system. We have a branch called "HiddenBr" and can be seen only by "Splusers" OS group users.

drwxrwx--- 8 iwmaster Splusers 512 Mar 18 23:24 HiddenBr