Skip to content

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

Merged
merged 7 commits into from
May 1, 2025

Conversation

ebenezerdon
Copy link
Contributor

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

@ebenezerdon ebenezerdon self-assigned this Apr 22, 2025
Comment on lines 13 to 15
# Common use cases {% #use-cases %}

## Multi-tenancy
Copy link
Contributor

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.

Copy link
Contributor Author

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?

@ebenezerdon ebenezerdon requested a review from stnguyen90 April 29, 2025 22:29
@ebenezerdon ebenezerdon changed the title Add multi-tenancy and common use cases to Teams documentation Add multi-tenancy user journey to Teams documentation Apr 30, 2025
Copy link
Contributor

@stnguyen90 stnguyen90 left a 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.

Comment on lines 200 to 203
title: 'Q2 Invoice',
amount: 2500.00,
customer: 'Example Customer',
status: 'pending'
Copy link
Contributor

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@stnguyen90 stnguyen90 merged commit 52ed430 into main May 1, 2025
3 checks passed
@stnguyen90 stnguyen90 deleted the update-auth-teams-doc branch May 1, 2025 00:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants