Overview of Widgets - Lists - Best practice ?

Hi DSA, great question!

Adding a List to a Board does not automatically mean that everyone who can access the Board can modify that List (for example add, delete, or reorder items). In Pigment, those actions are controlled by role permissions, not by the fact that the List is displayed on a Board.

To change the items in a List, a user needs specific permissions in their role, such as:

• Add List Items
• Remove List Items
• Reorder List Items

If a user does not have these permissions, they can still open the Board and view the List widget, but they will not be able to make structural changes to the List.

OK, so to make things clearer on the best practice / recommendation is : 

“Use or Add Lists that ONLY Administrators and Modelers can access to avoid unplanned changes to your data structure.”

So we should read something like “make sure that only Admin or modelers that have role permissions for : 

• Add List Items
• Remove List Items
• Reorder List Items

...To avoi unplanned changes.” ?

• As it is in the academy, the way the recommendation is worded is a bit confusing about what is required / intented behind this in terms of managing unplanned changes in data structure.
• It make look like that as soon as you add a list to a board, you need to make sure the board is only accessible to admin or modelers (e..g. having access to a board with a list in it autogrants you rights to manage the list published including adding and removing list items...)
• Yet the role permissions around lists grants more control it seems around removing / changing list items

One more question : Does the role permissions grants rights for the whole lists altogether or is it a permission distinct for each list ?