generated from hackforla/.github-hackforla-base-repo-template
-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Labels
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
Milestone
Comments
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? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature: Architecture
Feature: Infrastructure
Changes to site technical Architecture
Feature: Security/Regulatory Compliance
points: 2
Can be done in 7-12 hours
Role: PM
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:
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.
The text was updated successfully, but these errors were encountered: