More granular permissions
Separate the permission out that allows staff to change the timing of notices in a consortium, as this should be set at the system level and remain consistent system-wide. Staff should be able to design and manage notices without needing this permission.

-
Sarah Kasprzak commented
We need an LX Starter Role with the ability to create and edit Blocks of content without the ability to update the notices themselves. Because Marketing staff are responsible for the creation of content, but they are not familiar with the particulars of the ILS and Lending Services, we want them to be able to create blocks of content directly in the LX Starter admin, which an admin user can then add to our notice templates. We want them to be able to play around with the design of their elements directly, rather than having an admin do this and send them multiple drafts, tweaking formatting. We do not want them to have the ability to edit the core elements of the notices (ie. the required fields and repeated elements that are pulled from the patron record) or to edit the schedule for notice delivery.
Another way to approach this could be to add the ability for an admin to "protect" certain elements within the notice template so that a user with a lesser role could have the ability to add and remove some content blocks but have no ability to edit the sections determined to be core to the notice template. This would be an ideal solution since it would give staff creating variable content the ability to do this directly without worry of them impacting essential notice elements.
-
Jennifer Moakler commented
Agreed, not just for consortia -- permissions in LX Starter need to be more granular. We would like some staff to be able to edit notice templates without having access to notice history. We also have staff who can view notice history, but can't see the details of what items were included in a notice without admin-level permissions, which hinders troubleshooting.