Purely for academic discussion!​

[LauWoods]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

​​I noticed that there is a tenant_idfield in your database tables. Could you shed some light on where this value is assigned? I was under the impression that the Community Edition doesn't have multi-tenancy features. Purely for academic discussion!​

[dosubot[bot]]

The tenant_id field is present in many Dify database tables and models, even in the Community Edition. This is because the codebase is designed with multi-tenancy in mind, likely for future-proofing or compatibility with enterprise features. In the Community Edition, tenant_id is not actively assigned or used for tenant separation—it's just part of the schema and may be set to null or left unassigned in practice. There is no core logic for tenant resolution or enforcement in this edition, so the field acts as a placeholder rather than an operational feature. You can see this pattern across models like Dataset, Document, DocumentSegment, and others, where tenant_id is defined and indexed but not actively managed or enforced in the Community Edition’s business logic source.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}