Edit function not available to users

TS 741, WS8

-----------------

1) I have created CT_Editor group and added 4 users under this group

Users are granted access to a branch and then I have granted Editor access to a workarea for this group.

When a user is checkin a DCR in file system, he can only view DCR in Preview mode. Edit button besides DCR name in TS UI is greyed out. I even made this group as owner of workarea.

So if user is given an access as an Editoe, why can that group not edit DCR ?

2) In continuation of above issue, when user opens DCR in preview mode, only some fields appear populated, others don't. When a user downloads this DCR, he can see content in many more fields. So, why is content nit appearing in all fields in Preview mode ?

Thanks

Find more posts tagged with

Comments

Rick Poulin

1) There are four things you need to check here:

* user is a member of the group that owns the workarea

* ACLs on the file and folder in question allow this user/group to edit files

* a role that has 'edit form' operation is assigned to the user/group

* the content store is not frozen

If you can't edit the DCR, one of the above does not hold true.

2) Perhaps the DCT field definitions do not line up with the structure of your DCR? I can't imagine why you'd want your authors downloading DCRs and editing them locally...

anjanas

* user is a member of the group that owns the workarea

User is not a member of the group that owns workarea (workarea owner is a user and not a group). User ia added to a different group by the name Content_Editor. This group is added on the branch and to the workarea. This group has Editor role. So user does not need to be member of a group that owns workarea OR does he ? If he belongs to a group with Editor role, then it should suffice.

* ACLs on the file and folder in question allow this user/group to edit files

ACLs on file and folder allow this group to edit files

* a role that has 'edit form' operation is assigned to the user/group

Editor role is asigned to Content_Editor group, to which this user is added.

* the content store is not frozen

Content store is not frozen

I have tried following

Removed Content_Editor group from workarea and added it to Content_Admin, which has editor role on that workarea. After doing this, user can not even see workarea, Everything under branch is invisible.

I checked branch level permission, Content_Editor group and Content_Admin group, both are added at branch level with Editor role.

I checked parent branch of this branch, here only Content_Editor group is added with Editor role. Content_Admin group is not added here. Will this matter ?

Please explain, why is Content_Editor group unable to edit content ?

Adam Stoller

Chances are that you have branch and/or workarea security enabled in iw.cfg.

As such, unless the users are members of the group directly associated with the branch, they will not be able to see the branch or workarea. And yes, they would need to have access through any-and-all parent branches in order to see the branch you want them to work on.

The way I usually organize this is by having branch-specific groups like (assuming b2 is a sub-branche of b1):

b1_admins
b1_editors
b1_authors
b1_reviewers
b2_admins
b2_editors
b2_authors
b2_reviewers

I then create a group called b2_users that contains: b2_admins, b2_editors, b2_authors, b2_reviewers

I then create a group called b1_users that contains b1_admins, b1_editors, b1_authors, b1_reviewers, and b2_users.

I make b1_users the group associated with the b1 branch

I make b2_users the group associated with the b2 branch

All the other groups I associate with roles on the respective branch

My guess is that somewhere you failed to make the correct association between users / groups / branch access - and if you cannot figure it out from what you have I'd suggest starting over again using the above as a guide on how to do so.

Rick Poulin

anjanas wrote:
* user is a member of the group that owns the workarea
User is not a member of the group that owns workarea (workarea owner is a user and not a group). User ia added to a different group by the name Content_Editor. This group is added on the branch and to the workarea. This group has Editor role. So user does not need to be member of a group that owns workarea OR does he ? If he belongs to a group with Editor role, then it should suffice.

The short version of ghoti's post is that your assumption here is incorrect. Having a role only defines *what* you can do, but permissions (and indirectly, ownership) defines *where* you can do it. Your workarea should be shared with a group that either directly or indirectly includes your user.

The only exception to this rule is the Master role, which allows users to do everything everywhere.

RSSE.wsdl.txt