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

permissions on dcrs in 1 workarea

ProfessorX

Ok we have a shared workarea called workarea...
We have a in our templatedata dir the following...

templatedata\general_content\FAQS...and then data

I want only each individual user to be able to edit thier own FAQ DCR. Is this possible? How?

i.e I want the Canadian editor to only be able to edit the faq_can.dcr
I want the South African editor to only be able to edit the faq_south_africa.dcr

Thanks in advance!
WIN2K TS/TST 5.5.2 sp5; OD 5.6.0.1; DD 5.5.2
The Professor-

Find more posts tagged with

Comments

Gregg Faus

Wouldn't this work:

1) Share "data" directory with group, but make sure it doesn't propogate to child object. And reset children (e.g. DCRs) when applied thus removing the group ACL from the DCRs.
2) Give each author user (e.g. the canuck the faq_can) permission to each respective DCR

If the S. African author tries to edit the faq_can they'd get a permission error.

Adam Stoller

I can see being able to do this with lots of manual administration - can you perhaps create sub-directories under data/ for each of the users (or groups of users) and then set specific rights on those sub-directories? That would be a lot easier to set up and maintain (you can utilize the submit.cfg file to make sure the permissions on files in those folders get the right access). Of course it might require additional logic elsewhere within the general CM processes - but ...

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

ProfessorX

Will this work for new DRC's as well?

Thanks in advance!
WIN2K TS/TST 5.5.2 sp5; OD 5.6.0.1; DD 5.5.2
The Professor-

ProfessorX

Hmmmm...yea I thought of this but we are looking at maybe 200 seperate countries....that would be 200 seperate folders to house 1 dcr.

Thanks in advance!
WIN2K TS/TST 5.5.2 sp5; OD 5.6.0.1; DD 5.5.2
The Professor-

Adam Stoller

Here's another idea - not sure if / how well it would work - but suppose you store the name of the user who initially creates the DCR in the DCR [potentially as a hidden field] - as long as you can ascertain who the current user trying to edit the DCR is and compare the two values - you could use FormAPI code to either disable, or make read-only, all the fields if the userids *do not* match (or conversely only make them enabled / read-write if the userids *do* match)

This way it doesn't matter whether the DCRs are in separate directories - you can use submit.cfg or whatever to make sure that everyone has access at the file-system level - but you use FormAPI to safeguard who has access at the GUI level.

What do you think? Potential?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Jens

if you still haven't a solution, here is another idea.
using a rule in submit.cfg is good.
This should work without subfolders too. you can set permission to each dcr under data. in your case you can remove the write-permissions for the group, so only the owner of the dcr can edit it.
but there are problems if an other user should edit the dcr!
Maybe this is an option anyway.

Ciao,
Jens