SITUATION:
Default access to the db - “No Access”
I have a current situation, that a User is in a group “XXAuthors” (with author access to the db) and this value was in a Authors field for the document. The user is not a member of “XXEditors” group.
I need to restrict the editing access to the documents for all the users, except for the group “XXEditors”.
CHANGES:
I’ve created another group (for other purposes) - “XXNew” (with current reader access to the db) and placed the user into this group.
I run an agent which replaced the “XXAuthors” in Authors field with 2 groups - “XXEditors”: “XXNew”.
From my opinion it should prevent the User from editing a current document, but he still can do it (again - the User is not a member of “XXEidtors” and “XXNew” group has a reader access only)!
What’s wrong in this picture?
SHould I change anything else as well to make it work?
Thanks!
Subject: Authors fields new values don’t work
I have a current situation, that a User is in a group “XXAuthors” The user is not a member of “XXEditors” group.
I’ve created another group (for other purposes) - “XXNew” and placed the user into this group.
I run an agent which replaced the “XXAuthors” in Authors field with 2 groups - “XXEditors”: “XXNew”.
What’s wrong in this picture?
As the user is in the XXAuthors group in the ACL, he has Authors access to the database.
As the user is in the XXNew group, he has Author access to the document that has XXNew in an Authors field.
If only XXEditors should edit a document, set your Authors field to “No-one” - that way, no author can edit the document. You don’t need the XXNew group at all. (This presumes that the XXEditors group has Editor authority in the ACL)
Subject: RE: Authors fields new values don’t work
Yeah,
I understand the logic. But unfortunantely the old “XXAuthors” should stay in a database, because id defines access to other type of the documents and I cannot make five it REad status or remove it. THe owner of the database also wants to be able to have q possibility “quickly enable-disable” the editing access for different group of people and the idea was to create this additional “XXNew” group, which we can change from “Author” to “Reader”, depending on a situation.
Sorry for the complicated situation!
Subject: Authors fields new values don’t work
Check Database ACL again - user can be member another group or stay alone in there.
Check document - form can have more than one Athour field.
Subject: RE: Authors fields new values don’t work
Sergey,
Thank you for your input. The user is a member of “XXAuthors” and “XXNew” groups only (Douple checked it) and is not listed alone in a group. I’ll double check for other Authors fields, but most likely (98%) - I have 2 Authors fields, where I placed my values
Subject: RE: Authors fields new values don’t work
When ever we change a author or a reader field through agent, we ensure that the field is again converted into a author and reader field.You could try running an agent which would ensure this by using
notesItem.IsAuthors= true
Subject: RE: Authors fields new values don’t work
Oh,
this might be a good idea, I’ll try it out.
Thanks!