If it is necessary to restrict components and make them available only to certain users, sections can be used.
Note: Using sections often leads to problems and confusion, such as when a user creates a job for another user on a component that belongs to a section the second user does not have access to. Therefore, ensure it is absolutely necessary to use sections before implementing them, as they can cause more confusion than benefit if not managed properly.
Rules
- A user assigned to a section can see components and jobs in that section, as well as components and jobs that are not assigned to any section.
- A user who is not assigned to a section can see all components and jobs. For this reason, administrators typically should not be assigned to any section. To hide components and jobs from other users, those users must be assigned to a section.
- A user can only be assigned to one section.
- A section can have multiple subsections.
- If a parent component is assigned to a section, all its child components will automatically belong to the same section.
Example
We have a component called HSQE (Health, Safety, Quality, and Environment), which is for all jobs related to HSQE tasks. We want to hide these jobs from all other users except our HSQE personnel. To achieve this, we create an HSQE section and assign this section to our HSQE users.
Note: As mentioned earlier, other users must also be assigned to a section; otherwise, they will be able to see all components and jobs, including those assigned to a section.
In this way, components and jobs linked to the HSQE component (including subcomponents of the HSQE component) will only be visible to users assigned to that section or users who are not assigned to any section.
Comments
0 comments
Article is closed for comments.