Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define Tenant Boundaries for Data Isolation #623

Open
paulespinosa opened this issue Oct 11, 2023 · 4 comments
Open

Define Tenant Boundaries for Data Isolation #623

paulespinosa opened this issue Oct 11, 2023 · 4 comments
Labels
dependency Issues that are being blocked by another issue or other thing that needs to be completed first Feature: Architecture Feature: Infrastructure Changes to site technical Architecture Feature: Security/Regulatory Compliance points: 2 Can be done in 7-12 hours Role: PM

Comments

@paulespinosa
Copy link
Member

paulespinosa commented Oct 11, 2023

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.

@tylerthome
Copy link
Member

Moved to ice box, the feasibility of this will depend heavily on DB integration design in upcoming Incubator migration

@sanya301
Copy link
Member

sanya301 commented Jun 12, 2024

@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?

@tylerthome
Copy link
Member

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

@sanya301 sanya301 added the dependencies Pull requests that update a dependency file label Jun 28, 2024
@sanya301 sanya301 modified the milestones: 6- MVP, 7- Post MVP Jun 28, 2024
@ExperimentsInHonesty ExperimentsInHonesty added dependency Issues that are being blocked by another issue or other thing that needs to be completed first and removed dependencies Pull requests that update a dependency file labels Aug 2, 2024
@lola3736
Copy link

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency Issues that are being blocked by another issue or other thing that needs to be completed first Feature: Architecture Feature: Infrastructure Changes to site technical Architecture Feature: Security/Regulatory Compliance points: 2 Can be done in 7-12 hours Role: PM
Projects
Status: Ice Box
Development

No branches or pull requests

6 participants