![]() This means that they have access to the Space (read-only access) and thereby can access the Space administration. They also have the “View All” permission. nobody else can change permissions so we can be sure that this configuration is managed by the most Confluence-savvy people in our company. In the screenshot above we can see that only the Confluence administrators can administer this space i.e. “QMS WIP” space should have these following permissions: We now need to define correct permissions for our usergroups and remove everything else that can potentially be a threat to our security. Just open Space tools -> Permissions and you will see a page where you can define permissions for user groups, individuals and for anonymous access. In Confluence we should now also have two spaces: ”QMS WIP” (work in progress) and “Approved QMS”.Įach space in Confluence has a separate set of permissions. Second usergroup, “Product team”, consists of all the employees who should have access to the approved QMS documents. Let’s call them:įirst usergroup, “Quality team”, should consist only of people who have the right to work with the QMS documents. Let’s start by naming the usergroups and spaces we work with before going into the space settings to define permissions.įirst, in Confluence user management we need to create 2 usergroups. Once the Quality team is ready to publish the work-in-progress page, they can “push” the new version to be seen as a draft to everyone in the company.įollowing the steps described above, we now have two different interest groups and two different spaces in Confluence – we must now define and review the permissions, so that the right people have all the necessary permissions. Since every minor update of a page creates a new version of that page, it is wise to keep work-in-progress pages in a separate space. In Confluence this means hiding the work-in-progress versions (drafts) from others in the company. Typically, there are several draft versions, reviewed by different people, until the final agreed version of this document is ready to be published. To achieve this, we need to agree that in most cases the QMS document changes are updates are not just made one-time by one person only. We will describe how to set these permissions without implementing fully automated document workflows but by using Confluence’s own features and setting your in-house processes for approving drafts, publishing content, etc. The Quality team must have permission to work with the content and everyone else just views and uses it. In other words, we have two distinct groups of users with different responsibilities and user needs – in the context of Confluence permissions we have two separate groups with different set of permissions. In addition to that, we have a whole set of users who are actively using the approved QMS templates and SOP-s. For example, we have a Quality Manager and other employees in the Quality Department who own the QMS documents (update the QMS templates, approve and publish new versions). permission to edit Confluence page allows user to change content.Ī controlled Quality Management System is such where a few users can change the QMS documents and the rest of the users can use the already approved documents. Permission – the action of officially allowing someone to do a particular thing e.g.Space – A collection of pages in Confluence.Pages can be created and updated as needed. Page – page is an online document that can store text, tables, pictures, etc.Usergroup – A set of people who have similar interests, goals, or concerns. ![]() User – A Confluence user is a person who can read or update a Confluence site.Understanding how Confluence users can be guided and/or restricted we need to know a few basic terms: Let’s first review a few definitions, we will then describe the goal of Quality Management System control and finally we’ll look at how this control could be achieved in Confluence. Controlled actions performed by the right people is the cornerstone of developing a safe product. In order to have a safe, traceable and manageable Quality Management System in Confluence we need to first take care of our user management.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |