A multi tenant branch was started some time ago to support this natively (
https://gitlab.com/mayan-edms/mayan-edms/commits/feature/multi-tenant). It 
implements an Organization class to handle each tenant's data. It is still 
not complete. The tests for the 300+ views are not yet finished. Feel free 
to work on it if you have the time.

Until native database agnostic multi tenant is finished, a plugin that 
provides tenancy using database schemas is available in the app store: 
https://www.mayan-edms.com/store/

On Friday, August 11, 2017 at 2:37:04 AM UTC-4, Tony Nys wrote:
>
> Ideally in mayan, a concept/class Tenant should be there: where a Tenant 
> has 
> * Id
> * Name
> * External-ID (reference), Unique but optional : eg. the Syneton tenant id
> * StorageCollection: container name used eg. in Azure/AWS/... or local 
> subfolder-name in the 'document_storage' folder
>
> A Group has a FK id to a Tenant
> A documenttype  has a FK id to a Tenant
> A Cabinet  has a FK id to a Tenant
>
> so the tenant is actually a group of groups
>
>
> In a first phase, the FK could just be an optional attribute, 
> In a later phase, ACLs could be assigned to a Tenant,
>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to