Add multi-tenancy user journey to Teams documentation

src/routes/docs/products/auth/teams/+page.markdoc

@@ -8,7 +8,27 @@ Teams are a good way to allow users to share access to resources.
 For example, in a todo app, a user can [create a team](/docs/references/cloud/client-web/teams#create) for one of their todo lists and [invite another user](/docs/references/cloud/client-web/teams#createMembership) to the team to grant the other user access.
 You can further give special rights to parts of a team using team roles.
 
-The invited user can [accept the invitation](/docs/references/cloud/client-web/teams#updateMembershipStatus) to gain access. If the user's ever removed from the team, they'll lose access again. 
+The invited user can [accept the invitation](/docs/references/cloud/client-web/teams#updateMembershipStatus) to gain access. If the user's ever removed from the team, they'll lose access again.
+
+# Common use cases {% #use-cases %}
+
+## Multi-tenancy
+
+Appwrite Teams is an excellent solution for implementing multi-tenancy, allowing you to create a team for each organization, company, or tenant to handle multi-organization apps with built-in data isolation.
+
+With Appwrite Teams, you can:
+- Create a team for each organization/tenant in your SaaS application
+- Use team-based permissions to ensure users can only access their organization's data
+- Use team roles to set up different access levels within each organization (admin, member, viewer, etc.)
+- Scale to support unlimited organizations without code changes
+
+## Other common uses for teams
+
+- **Collaborative workspaces**: Create teams for project collaborators, each with specific roles and permissions
+- **Family plans**: Group family members together for subscription services
+- **Educational platforms**: Organize students and teachers into classroom teams
+- **Business departments**: Separate company functions like Marketing, Sales, and Engineering
+- **Event management**: Create teams for event organizers, speakers, and attendees
 
 # Create team {% #create %}
 For example, we can create a team called `teachers` with roles `maths`, `sciences`, `arts`, and `literature`.
@@ -219,7 +239,7 @@ Learn more about permissions
 
 # Memberships privacy {% #memberships-privacy %}
 
-In certain use cases, your app may not need to share members’ personal information with others. You can safeguard privacy by marking specific membership details as private. To configure this setting, navigate to **Auth** > **Security** > **Memberships privacy**
+In certain use cases, your app may not need to share members' personal information with others. You can safeguard privacy by marking specific membership details as private. To configure this setting, navigate to **Auth** > **Security** > **Memberships privacy**
 
 These details can be made private: