Hello @Nils.Srvd
Thanks for your idea, but I don’t think this is easy to achieve. Perlite doesn’t just display provided .md files, so you can’t easily view them via iframe. Each .md is parsed by the PHP engine and the markdown is translated into HTML, so PHP without an interface (e.g. to CryptPad) does not know which user has access to the file or not.
Also keep in mind that the free CryptPad plan only gives you 1GB of storage.
Access restrictions, based on single .md files could be implemented, for example with some special prefix in the filename or content, but then the next question is, should the file name be displayed in the navigation? What about the parent folder? Also without a database in the backend you cant handle multiple useres or different access levels.
One way to create a private space would be: create two main folders or vaults, one private and one public, and then separate them with two perlite instances and two nginx vhosts, secure the vhost configuration for the private one with a client certificate authentication (mutal authentication). Then provide the certificate to the users you want to grant access to. Alternatively, extend the private Perlite instance with a simple http authentication.
But Perlite is open source, so feel free to fork it and implement any authentication or third-party service if you like.
BR,
Sec77