...
PageBuilder on Microsite Pages other than their own.
SiteManager Access to manage-showroom pages other than their own
FileManager access on Microsite pages not their own
FileManager access to Folders other than their own
EDIT:
Most likely, the customerID will be used to match the page’s groupID for simple association.
User Creation
When a new user has a memberShowroom record added, they will be assigned a groupID showroomURL in that record.
Use the customerID in the pages' groupID columns, matching a user to a pageThat showroomURL will govern which pages they own by setting an extra session var when they log in filemanagerChrootDir.
Login
Plumb Club members log in as administrators. Upon Login, additional ‘extra_data’ is set in the session based on values in their memberShowroom record(groupID, etc). Grab the namespace (showroom URL) from the memberShowroom table and place into the session. FileManager will use that session namespace to chroot the folder access.
...
Each page will decide to be editable on the front end based on the ID filemanagerChrootDir extra session var of the logged-in user. If necessary, use a hook for this. Pages will can also be created for user with groupID of user – groupID being stored in session extra data. A page hook for custom pages will set the pageDetails['additionalJSInfo'] value to pass to pageBuilder, or change the value of ‘enablePageBuilder’ that is sent via pageInfoJS. That hook will determine whether user can edit the current page by comparing the page’s groupID URL with the user’s group IDfilemanagerChrootDir.
The main way to determine whether SiteManager bars or pagebuilder show on a particular page is through the use of the sitemanagerview class, specifically its userOwnsPage function.
Limiting Folder Access in File Manager
...