docs: guideline on how to organize projects

Author: tianzhou

content/docs/concepts/data-model.md

@@ -57,6 +57,12 @@ A list of databases usually having the same schema structure. Examples like per-
 
 ## Project
 
+<HintBlock type="info">
+
+[How to Organize Projects?](/docs/onboarding/#how-to-organize-projects)
+
+</HintBlock>
+
 `Project` is a logic unit to model a team effort. It's similar to the project concept in other dev tools such as Jira, GitLab. `Project` is the container to group logically related `Databases`, `Issues` and `Users` together. In Bytebase, A `Database` or an `Issue` always belongs to a single `Project`. `Project` is also the peering entity with the VCS repository to setup [GitOps workflow](/docs/vcs-integration/add-gitops-connector).
 
 Most of the time, `Developers` work with the `Project`.

content/docs/onboarding.md

@@ -98,6 +98,17 @@ Related features (in addition to Phase 1):
 - [Changelist](/docs/changelist/)
 - [Online Schema Migration (MySQL only)](/docs/change-database/online-schema-migration-for-mysql/)
 
+## How to Organize Projects
+
+Bytebase has a `Project` concept to group logically related `Databases`, `Issues` and `Users` together. This
+is similar to the project concept in other tools such as Jira, GitLab.
+
+We recommend you to put databases sharing the same schema structure into the same project. For example,
+if you have a multi-tenant SaaS application, you can put all the tenant databases into the same project.
+
+If you have a single team managing databases with different schema structure, you can create a project for each
+schema structure, and create a [user group](/docs/administration/user-groups/) for the team. You then grant the project role to the user group.
+
 ## Configuration Guideline
 
 Bytebase provides settings at the workspace, environment, project levels. Below we provide a sample configuration settings for a typical scenarios: