Best practice for restricting edit access to PageBuilder content?

It seems like many LO admins use PageBuilder to store, edit, and reuse content that is not necessarily any sort of page, but html snippets, javascript, tracking, etc, all loaded into giving pages via S-Tags.


Our goal is to give specific users access solely to their own PageBuilder content, not to any custom scripts (Currently in the default General category) that only admins should have access to. The secondary goal is to keep all users out of the fragile "Design Donor Screens" section of giving pages, though not necessarily lock them out, as all they need to do is maintain the sidebar content.

We understand that there are PageBuilder folders and Security Categories.


A PageBuilder security/permission use case we are trying to solve involves:

• Creating a PageBuilder "page" HTML snippet that will simply be the sidebar content on one or more giving pages, loaded via S-Tag.
• The content will be frequently updated by a specific user.
• This user should have no access to any other PageBuilder content, not even in General, unless we instead need to move the General content to a more secure group.

Questions:

• Do the content/scripts in PageBuilder need to remain in the General security category to be visible to anonymous visitors when the content is loaded into giving pages via S-Tags

I have a secondary test user I've been experimenting on permissions/groups with, but I am not at all finding it intuitive or seeing much documentation for this use case.


Thanks!