You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you for creating such a great collaborative markdown editor. I've been using CodiMD and really appreciate its features and ease of use.
I'd like to propose adding support for multi-tenant data isolation. This would be particularly valuable for organizations that want to use CodiMD while ensuring that documents and data are properly isolated between different tenant groups (e.g. different departments, teams or customer organizations).
Some key benefits of implementing multi-tenant support would be:
Enhanced Security: Ensuring that users can only access documents within their tenant boundary
Better Organization: Allowing administrators to manage permissions and content at a tenant level
Compliance: Making it easier for organizations to meet their data governance requirements
Would the team be interested in adding this feature? I'd be happy to provide more specific requirements or use cases if helpful.
Looking forward to hearing your thoughts on this!
Best regards
The text was updated successfully, but these errors were encountered:
Hi CodiMD team,
First of all, thank you for creating such a great collaborative markdown editor. I've been using CodiMD and really appreciate its features and ease of use.
I'd like to propose adding support for multi-tenant data isolation. This would be particularly valuable for organizations that want to use CodiMD while ensuring that documents and data are properly isolated between different tenant groups (e.g. different departments, teams or customer organizations).
Some key benefits of implementing multi-tenant support would be:
Would the team be interested in adding this feature? I'd be happy to provide more specific requirements or use cases if helpful.
Looking forward to hearing your thoughts on this!
Best regards
The text was updated successfully, but these errors were encountered: