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

STAGING Permissions

andrew_yeo

Why is it that my STAGING area is not viewable by ALL. Some folders show "N/A"... though the default for STAGING is to allow all workareas users to be able to QA the submitted contents???

Find more posts tagged with

Comments

Adam Stoller

Can you provide a bit more information?

1) What version of TeamSite
2) What platform
3) What *are* the access rights on those directories in STAGING?
4) What *are* the access rights on those directories in an up-to-date workarea?
5) Do you have a submit.cfg file? If so - does it have any entries that might pertain to those directories?

It is fully possible to alter/ restrict the access rights on files or directories either through the submit.cfg file or directly through the file system interface. In either case, the change is actually made to the file within the workarea and it is when it gets submitted that those access rights get noted in STAGING and subsequently in any new workareas or old workareas that get updated from STAGING afterwards.

--fish
(Interwoven, Curriculum Development)

andrew_yeo

Here goes,

1) What version of TeamSite
> v5.0.1
2) What platform
> WinNT 4.0
3) What *are* the access rights on those directories in STAGING?
> The access rights to the individual folders are that of the respective workarea... i.e. i submitted a folder "jscript" from "webmaster_wa", it (staging) inherits the exact rights. Which makes user from another workarea sees "N/A" when they look at the STAGING contents.
4) What *are* the access rights on those directories in an up-to-date workarea?
> The "Get latest" cmd will pull the exact folders with access rights intact, i.e. if I get latest on "jscript" folder which was submitted by "webmaster_wa" I will see the folder in my workarea as "N/A".../??
5) Do you have a submit.cfg file? If so - does it have any entries that might pertain to those directories?
> No, I do not have a submit.cfg

thanks.

Adam Stoller

Okay - then it sounds like you're seeing exactly what you are supposed to be seeing. If a folder is protected against access within the workarea it *should* be protected against access in the staging area.

If it didn't, you would have a big security hole.

If you're concerned about directories that were created in one workarea - but meant for all - not being accessible after the files have been submitted to staging because they pick up the access rights of the workarea in which they were created - then you want to look at submit.cfg (it's documented in the TeamSite Administrator's Guide)

Does that clarify it for you?

--fish
(Interwoven, Curriculum Development)