# 機能提案：プライマリグループメンバーシップに基づくカスタマイズ、別名「テナンシー・ライト」

**URL:** https://meta.discourse.org/t/feature-proposal-customizations-based-on-primary-group-membership-a-k-a-tenancy-lite/101608
**Category:** Feature
**Created:** [2018 年 11 月 8 日午後 2:45 UTC](https://meta.discourse.org/t/feature-proposal-customizations-based-on-primary-group-membership-a-k-a-tenancy-lite/101608 "2018-11-08T14:45:20Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [2018 年 11 月 8 日午後 6:43 UTC](https://meta.discourse.org/t/feature-proposal-customizations-based-on-primary-group-membership-a-k-a-tenancy-lite/101608/5 "2018-11-08T18:43:01Z")

</div>

> [@trudat](#):
>
> I can’t support multiple forums and it defeats the purpose of Discourse

Why not [Multisite](https://meta.discourse.org/t/multisite-configuration-with-docker/14084)? Running a separate discourse database and front end within the same footprint? It’s going to be much easier to support a partition at that level than it is to embark on any of the above.

When you get to the point that you’re separating the theme, front end and content you’re effectively talking about separate Discourse instances. That’s pretty much why multisite exists. The added benefit is that they can make use of different site settings and sign-on.

New plugins and code changes aren’t just adding stuff to accommodate a new forum with the above, you’re adding complexity and a big risk of blowback onto your existing customers.

---

_[View the full topic](https://meta.discourse.org/t/feature-proposal-customizations-based-on-primary-group-membership-a-k-a-tenancy-lite/101608)._