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

TeamSite Workarea/directory security

System

We are running Window 2003 on TS 6.7.2. We have found a security problem in out existing TeamSite environment (6.5 Sp3) where users submit content on a cross Business Area Branch but a specific workarea for each bus. area.

The problem is we have directories that the content exists in all workareas but we do not want specific content in those directories to be updated across all workareas.

We use the submit.cfg using the setaccess parameter and when the content is submitted the security is right on the data but we are trying to resolve the users being able to even submit the data.

example below:

branch1
wa1
dir1
dir 2
file 1
dir 3
wa2
dir 1
dir 2
file 1
dir 3

What we are trying to do is make sure only wa1 can submit content to staging from dir 2 (file 1) permissions are set in submit to reflect the security for wa1 but we are trying to configure TS to not allow users to submit from dir2 file1 and overwrite the file 1 in staging

I was not able to understand if a restriction on submit.cfg was an option for this in the administration doc.

Find more posts tagged with

Comments

Migrateduser

In the admin doc specfically looking at access it would appear this maybe a windows permissions issue on the workarea?

Does anyone have any ideas if this is correct or are there other possibilities?

Thanks

Pawan

If you want not to allow user to submit at all from the other workarea, then instead of making changes to submit.cfg, you can override or customise the default submit workflow and do not allow the user to submit any content from that particular path and transition the workflow to end.

I would like to know the purpose for this restriction and different ways a content can be submitted from the other workarea.

HTH

Migrateduser

We have 12 branches that are spread amongst different business areas. Each business area has been isolated by creating a workarea for each area.

All workareas deploy to the same web server and should deploy to specific locations on the web server. Each workarea has the entire data structure and we would like to remove the users ability to submit content from the directories in thier workarea that they should not deploy to.

We currently have submit.cfg setup to secure the directories after submission but were trying to find a way to basically remove (grey out) the directories and ensure they cannot accidentially update content.

I have been able to test changing the directory security within the workarea and have seen the directories grey out but then we start to have issues with teamplatedata when trying to edit the files.

The assumption is for future branch configurations that spread acorss different business lines we could create sub branches rather than workareas and this would solve the issue. The problem is migrating from a pre 6.5 TS environment (Windows 2003) to 6.7.2 and changing the way we have configured the environments in the past to put us in a good position for future TS implimentations.

Pawan

...All workareas deploy to the same web server and should deploy to specific locations on the web server. Each workarea has the entire data structure and we would like to remove the users ability to submit content from the directories in thier workarea that they should not deploy to.

We currently have submit.cfg setup to secure the directories after submission but were trying to find a way to basically remove (grey out) the directories and ensure they cannot accidentially update content.

I have been able to test changing the directory security within the workarea and have seen the directories grey out but then we start to have issues with teamplatedata when trying to edit the files.
....

You cannot have users able to edit the files under a workarea and at the same time the directories grey out. However, my understanding is you just do not want users to edit content in this workarea, then you can set readonly permissions for that workarea.
Please explain a bit more on your scenario as I am still not sure whether, I understood it correct.