Comment 12 for bug 1645862

+1 to comments and suggestions from Terran and Jennifer P.
> Release notes needed to explain how this works & where it will display
> New permission needed & only display option when permission is present
> Selected org unit display
> Failure/Success toasts

Notes from my few testing results:
(1) When I save a setting from the grid using the "Save Grid Settings to Org" and then check the Lib Setting, it just shows "[object Object]" as the value.

(2) When entering a value directly into the Lib Setting for Grid Config: user.bucket.view, it does break the interface and no columns or values are visible on that screen. I then realized this is not an Angular interface and that was the problem. So, should we have options for org unit settings available for the AngularJS grids when they cannot be successfully applied? Even with release notes, that could be confusing.

(3) To enter a value directly into a Lib Setting, will we need to know the column names and enter a flex value for each column? or will we not be able to enter/edit values in the Lib Setting at all?

Overall, I agree with the last note in comment #11 questioning the usefulness of having these in the library settings editor. It adds tons of new settings which most likely would be edited rarely (once defaults are established) and makes browsing more difficult. If they are going to live here, a new group would be beneficial.