Security role for KB not working as described in help section
According to the help file:
Add Articles: Allows a user to create new Knowledge Base articles.
Always Edit Articles: Allows a user to modify Knowledge Base articles even if the user did not create the articles.
This implies that the user with Add Articles should be able to edit articles that they created without needing the Always Edit Articles role assigned. But it does not seem to be working this way. One of my users created an article, and he is not able to edit it. Gets an error message. (Article ID {omitted}).
Answers (3)
Hi Bodek,
This has been brought to our attention in the past, so we actually have created a KB article dedicated to creating and submitting articles. It outlines the basic permissions needed and involved with performing this action. You can view the article at this link. You will notice at the end of the "Submitting for Review" section it mentions that simply owning/creating an article does not inherently give a user the ability to edit their article after it has been Submitted or if it is then Approved by a reviewer or person with the "Always Edit Articles" permission. Having only the "Add Articles" permission means you can create and edit your own articles prior to submission, and if they are rejected, but you would not be able to go do anything with another user's article that they might have created, saved, and not yet submitted.
Hopefully this has fully addressed your question about the "Add Articles" permission. If you have any further questions or concerns please let me know.
Sincerely,
Mark Sayers
TeamDynamix
Bodek,
In order to edit articles once they have been submitted or after they are approved, a user would have to have the "Always Edit Articles" permission. If a user only has the "Add Articles" permission, they can only edit them in the situations I described previously, which the KB I linked to also covers.
Please let me know if you have any additional questions or concerns.
Sincerely,
Mark Sayers
TeamDynamix
Thank you for that answer Mark. Hopefully your documentation will be updated with this helpful explanation in the future.
Just to confirm, with the existing functionality the editing rights are "all or nothing" approach? It is not possible to have any more granularity beyond this, right?