N1ED in a Custom Multisite CMS
A lot of SaaS CMSs and online website builders help a wide audience of people and companies create their own websites.
The main difference between single-website CMSs and multisite CMSs is that the latter manage multiple websites independently, ensuring their preferences, file storages, and custom Bootstrap block templates do not intersect between different users (websites) until you explicitly use block template sharing feature.
So you need to use an individual API key for every website your CMS users have and load the editor (N1ED, TinyMCE+N1ED, or CKEditor+N1ED) with these personal API keys.
SaaS API basics
How to make requests to N1ED server from your CMS
Automate API key creation
Generate API keys when a user registers and pre-create keys for existing ones
Separate file storages
Isolate users of different websites in their personal directories
This SaaS API is available to everyone on the SaaS plan. If you have a different plan but wish to scale in the near future, please contact support and we can enable it for you too.
After signing up for the SaaS plan, you will receive a secret SaaS token for accessing the SaaS API. Please keep it secret and do not share it with your users, as this token can be used to make changes to all configurations of the websites you manage. Also, try to limit the number of developers who have access to this token. The best practice is to store it outside your repository, just like any other sensitive data.