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; } } }

Workarea folder visibility

RichieRich

It's been a while since I had time to work with our Interwoven box, mainly because it's just one of many hats I wear. So please excuse this question.

I currently have a workarea which is used for our IT staff who manages one of our websites. We are looking at giving other people the ability to manager their own folders. The problem is that the folder they wish to manage is three folder levels down and we only want them to have access to just that folder and just that workarea.

What I want to achieve is to have each group (new users will be in one of three groups) to be able to only view their own workarea and have visibility to just their own folder. (Nothing above that folder level.)

Is there a way I can filter out all folders except just the one folder I want and hide an other workarea under that branch?

I hope I articulated this question clearly.

e.g., visual of the folder structure.


 BRANCH [Parent]
  WA1 [Basis of all child workarea's I plan to create]
   regions
    region1
    region2
    regionNth
  WA2 [For Region1]
   regions
    region1
  WA2[For Region2]
   regions
    region2
  WANth
   Regions
    regionsNth

Thank you for your help.

P.S. Thank you -fish for your last response.

-[ Richie Rich ]-

Find more posts tagged with

Comments

akshathp

In my opinion the best way to achieve this would be by controlling at the branch level and not WA level. I mean, as an author, I will still have access to STAGING and will be able to view any information there. Unless viewing the information is not a problem. Ofcourse with groups I won't be able to edit anything unless I am part of that group as author.

SO, is it OK if they are able to view the content? Although they won't be able to edit it.

With branches, all branches could be configured to deploy to same production server with combined file structure.

Hope this helps!

Akshat Pramod Sharma
Interwoven Inc.

Adam Stoller

Actuall, as an Author, I don't believe you currently have *any* access to the staging area (except perhaps through the filesyste interface).

In order to get to a directory 3 levels deep - you need to be able to get to that directory. On Unix this means having read/execute permissions on the parent directories (and probably pretty much the same thing on Windows) - and then once you get to the level where ownership takes place, you grant write access in addition to read and execute for the users / groups you wish to have access.

As Akshat mentioned - if you can do this at the branch level, it might be easier - but if you want to do it at the folder level within the workareas keep in mind that the permissions that exist in one workarea should be the same as the permissions that exist for those same files and folders in any other workarea on that branch. You cannot set workarea-specific folder/file permissions and expect it to work (they share a common repository and are essentially just links to that repository until something is edited - therefore you cannot change the permissions on a file based solely on which workarea it is being viewed from).

If this doesn't answer your questions - please try to add a bit more detail and scenarios for what you are trying to accomplish.

--fish
(Interwoven Senior Technical Consultant)

RichieRich

Ok, let me see if I'm understanding the feed back correctly.

You're saying that I should configure my branch to give "other" read/execute, so the user will be able to navigate to their folder which resides three folders deep. At that point They would have ownership of the files (The group permissions would be configured so they have read/execute/write) and the group owner will be their own group.

e.g.,


BRANCH [GFS: agroup] 775
    regions
        regionb [[Group: bgroup] 
        regionc [Group: cgroup] 
        regiond [Group: dgroup]

I can always setup the user's homepage to their respective folders so they won't have to navigate to that directory and visibility really isn't an issue. Some people just preferred to have them view only their folder.

Thank both of you for the feed back.

Akshat and Dr. -fish

-[ Richie Rich ]-