Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Shared Groups(s) for Workflow
Internewbie
Hi there,
i just do my first steps with interwoven.
Right now i'm wondering how to add users or a group to a workarea when it's already created.
thx a lot for any hint
Find more posts tagged with
Comments
mmb
You dont add users to a workarea.
When you create a workarea, you assign it a group for sharing. When you then want users to be able to edit content in that workarea, you grant them access to the security group that the workarea is shared with.
You could just create another new workarea and assign it a group for sharing that your users have access to.
- mark
Internewbie
Hi Mark,
thx for Your answer.
So if i got u right, there's always exactly _one_ OS security group shared for exactly _one_ workarea. There is no way to assign two groups to one workarea?
Daniel
mmb
not as far as I am aware. What you can do though is for 1 branch, have 2 or more workareas with different group permissions associated to them.
e.g
BRANCH1 ----Staging
|
|---Workarea 1 shared with group1
|
|---Workarea 2 shared with group2
This means that users with access to group1 can edit files in workarea 1 but not workarea2 and vice versa. Both workareas feed the same Staging area, so you could configure the submit.cfg to apply generic permissions to the Staging area files.
Does this help you?
- mark
Internewbie
Hi,
the complete requirement is the following:
i have one branch within i need several 'sections', each assigned to a specific group of several authors and one or more editors. These sections should be independ and not accessible (best not even visible) by memebers of other groups. There should be workflows/jobs running wich get assigend only to members of the specific group.
Furthermore i need one section wich all users can access.
And i need one group of editors with acess to all groups.
the current ideas are:
Either have just one workarea, with a tree of several folders as 'sections', managing all right just by the OS filesystem.
Or 'copy' this tree to several workareas, assigning one group to each workarea.
Since this decision seems basic to me for further development of the system, any explanations for one or the other possibility will be appreciated
.