Any updates for this bug?
/// <summary> /// If ParentTenantId is null, then it is associated directly to the Main Host Tenant. /// </summary> public virtual int? ParentTenantId { get; set; }
[ForeignKey("ParentTenantId")]
public virtual Tenant ParentTenant { get; set; }
/// <summary>
/// Associate Parent Tenants to its Children Tenants
/// </summary>
public virtual ICollection<Tenant> Children { get; set; }
I am implementing the extension of the Tenants with something like this.
I think it's somehow similar to the Organization Units wherein they have root and children.
Any thoughts?
There is a critical bug in the visual settings > menu.
Kindly see the screencast for more info
[https://drive.google.com/file/d/17Ad8qBUTAswtpGvS6vQ9d0n61XMOYIvP/view?usp=sharing])
Our host company has multiple tenants.
Then one of those tenants would also have tenants under them as well.
For example,
Host has Tenant a and Tenant b.
Then Tenant b has tenant c and tenant d.
All of these tenants regardless of hierarchy must be in control of the host regarding the subscription and other administrative functions.
I'm thinking in extending the permissions for the Parent tenants and making a linking table between the parent tenant and its tenants. In this example, adding a link between (parent) Tenant b and (child)tenant c and also Tenant b to tenant d.
The host admin will add a tenant management permission available for the Tenant b and will give Tenant b's admin an access to their tenants.
What are your thoughts about this?
May I know how this scenario can be done inside aspnetzero and how much of an effort do we need to make in applying the necessary changes?