HomeUniteUs
HomeUniteUs copied to clipboard
hackforla
Define Tenant Boundaries for Data Isolation
Dependencies
When this project moves to supporting more than one organization
Overview
A tenant is a group of users. A tenant may want to isolate its data from other tenants for security, policy, legal, compliance reasons.
An example:
- OrgA is a client of HUU. OrgA provides two programs that carries out Host Homes and empty beds initiatives.
- OrgB is a client of HUU. OrgB provides five programs that carries out Host Homes and empty beds initiatives.
- OrgC is a client of HUU. OrgC provides one program that carries out Host Homes initiatives.
For data isolation, tenant could be defined as either the client organization or each of an organization's programs.
Action Items
Research policies and regulations that organizations have to follow. Define a tenant as an organization or as an organization's program. Ideally, choose one to define as the tenant.
Moved to ice box, the feasibility of this will depend heavily on DB integration design in upcoming Incubator migration
@tylerthome thanks for the ice box comment, do you mind adding a dependency section at the top of the issue and linking to the DB integration design issue? Also is the role:PM assignment correct here? Do you need anything from PMs or is this more an engineering story?
I believe we have the info we needed from Bonnie for this one now - we will design the system for a single tenant/customer, with the ability for multiple organization entities for which the application can be configured and deployed. There will not be a need to create a multi-tenant architecture where resources are deployed with strict data and resource isolation.
Since we have addressed this question, but dropped the potential system requirement set that would have come from this, I am not sure whether it's appropriate to close this as Not Planned or as Completed
@tylerthome Is this issue still open? in the above comment you indicated that the question has been addressed, to clarify the conclusion is that we dont need create a multi-tenant architecture? Does it need to be revisited post MVP? CC: @lasryariel
