-
Notifications
You must be signed in to change notification settings - Fork 241
Add multi-tenancy user journey to Teams documentation #1934
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
Conversation
# Common use cases {% #use-cases %} | ||
|
||
## Multi-tenancy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This part of the docs is for high-level introduction to the concept. I don't think we should delve into a use-case here. This type of content seems to fit more under Journeys. Separating it out as a Journey will also make it more visible.
See https://github.com/appwrite/website/blob/main/STYLE.md#products for info about the different sections and what belongs where.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That makes sense. What do you think about the update?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! Just a couple things.
title: 'Q2 Invoice', | ||
amount: 2500.00, | ||
customer: 'Example Customer', | ||
status: 'pending' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the tenant_id would need to be set here too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
What does this PR do?
Adds information about implementing multi-tenancy and other common use cases. Address developer confusion about whether Appwrite supports multi-tenancy and how to implement it.
Test Plan
/docs/products/auth/teams