keeping users out of old branch

lj1958

Recently we migrated content management for our Intranet to a new branch in TeamSite. I've been trying to keep users out of the old branch which I have been requested to keep active for several more months.

We've had multiple cases of business users (ie - less technically-literate) stumbling into the old branch. I set the permissions on that branch for two groups that are the most likely to need to get in. I thought I'd done enough to keep other users out, but apparently not.

Right now I have a user who is getting error screens because she apparently clicked on the wrong thing yesterday, and is completely stuck. She's getting this error:

ASSERTION FAILED: Unable to find parent for vpath //(path to a file in
the old branch)

So first...I need to get her out back to the new branch. Second, I need to find out what more I need to do in order to keep these users out of the old branch.

We're running TeamSite 6.50sp2

Find more posts tagged with

Comments

interDev

I set the permissions on that branch for two groups that are the most likely to need to get in. I thought I'd done enough to keep other users out, but apparently not.

1. Did you change the permissions on the branch or workarea? You share the workarea with a group and if you remove the existing Group sharing from that workarea, your users will not be able to make any changes.
2. Marking the branch as 'private' is another option using which you can hide the branch itself so that users dont see it (i dont think it is possible in 6.5).
3. Also you can disable the workflows from that branch so that users dont accidentally deploy the content to webserver.
4. Rename the branch to something else (e.g. archive_branchname) so that users dont see their original branch.

lj1958

1) Yes, I changed permissions so that only users involved with developing content (beyond templates) could get in. This user is not included.

2) I think you're right - in 6.5 I don't think the branches themselves can be marked as private.

3) There are no workflows on the old branch

4) I am going to try changing the name of the branch, but I'm not sure what that will do for the user who is getting the errors.

Adam Stoller

Recently we migrated content management for our Intranet to a new branch in TeamSite. I've been trying to keep users out of the old branch which I have been requested to keep active for several more months.

We've had multiple cases of business users (ie - less technically-literate) stumbling into the old branch. I set the permissions on that branch for two groups that are the most likely to need to get in. I thought I'd done enough to keep other users out, but apparently not.

Right now I have a user who is getting error screens because she apparently clicked on the wrong thing yesterday, and is completely stuck. She's getting this error:

ASSERTION FAILED: Unable to find parent for vpath //(path to a file in
the old branch)

So first...I need to get her out back to the new branch. Second, I need to find out what more I need to do in order to keep these users out of the old branch.

We're running TeamSite 6.50sp2

The problem is most likely that during the user's last login they were within the branch that they no longer have access to and TeamSite is trying to put them back there when they login.

Hope that helps.