How to make entire workarea/branch readonly

TS 6.5 sp1, Win 2003

We have number of projects/branches. When a project moving from one phase to another, new project will be created with existing data for new phase. The users should use the new project. How can we stop users without editing the old phase project/branch, ? We don't want to delete the old project. Any suggestions? Thanks

Find more posts tagged with

Comments

nipper

Can you remove the workareas ?

Srinivasa Talla

Actually we don't want to touch the old project(either workarea/branch), keep as it is, make it as readonly.

kajjubee

One way is to change your group for sharing of the workarea to another group which the users are not part of.

K

Srinivasa Talla

It is not allowing me to change the group of workarea(existing one). I can only change the Branch group. This is changing the branch color to grey, so that user can't able to see the contents at all in UI, but I can't able to stop them from email link. I tried for branch/folder/DCR.

Bhargav Coca

In windows it kind of hard to achieve what you are trying to do. One possible way is to create group with the user who needs access to one branch and readonly on other. On the windows explorer go to your Y:/../../Branch and add the group for this branch from the security tab and give permissions as you desire. See if this works. You can not meddle already exisitng groups, unless you already have a group with thos people with same branch readonly and write prmissions. Hope this is clear.
Thanks

gzevin

TS 6.5 sp1, Win 2003

We have number of projects/branches. When a project moving from one phase to another, new project will be created with existing data for new phase. The users should use the new project. How can we stop users without editing the old phase project/branch, ? We don't want to delete the old project. Any suggestions? Thanks

you might want to back your branch somewhere else, so the users won't be able to find it easily, and leave only staging in place, as nipper has suggested..Or, in fact, rename your original branch, while creating some empty branch

Srinivasa Talla

Thanks Greg. This question we can talk in two ways.

1. How to hide the branch/workarea - we can do this by changing the name or copying to somewhere else.

2. It should be available to user, so that they will see the information about the old project, but should not allow them to edit the contents.
(Already user have email with series of DCT links for that particular branch/workarea). If there is any setting with workarea, we could change that.

JonathonG

This may not work for a branch that you already have, but it is an option for future branches if this is going to be an ongoing requirement:

1. Create the branch using "Mandatory Write Locking" (read your documentation for caveats about performance related to this locking mode)
2. When the project completes, lock all the files to an administrative user.

Frederik

2. When the project completes, lock all the files to an administrative user.

That gave me an idea: whatever the locking model for the existing branch... wouldn't the requirement be fulfilled by creating a new workarea on the branch (owned by admin, no sharing group), in which ALL files are being locked...

That may not stop users from editing files (depending on the locking model, they will probably just receive "are you sure you want to edit, because this file is locked" warnings). But it should stop users from submitting changed files from the original workareas, because file is locked in another workarea.

It will take a bit of scripting to easily lock each and every file.

This is all "If I remember the documentation correctly".... It's been a while since I last had my Teamsite Locking 101 reading... but lunch is waiting ;-)

... of course, deleting workareas and just keep STAGING for read-only viewing, would be a **** of a lot easier ;-)