# Extend Existing Controller?

**URL:** https://meta.discourse.org/t/extend-existing-controller/266411
**Category:** Development
**Created:** [May 28, 2023, 1:59am UTC](https://meta.discourse.org/t/extend-existing-controller/266411 "2023-05-28T01:59:19Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [May 28, 2023, 8:12am UTC](https://meta.discourse.org/t/extend-existing-controller/266411/9 "2023-05-28T08:12:49Z")

</div>

> [@petermarkley](#):
>
> Bearing in mind that there are close to 200 units in our community, it didn’t seem feasible to use the groups feature to accomplish this. See also #3 below, which groups would also conflict with.

Groups will work fine for that purpose, and you can easily have 200 groups.  
All you would need to do is to manually or programmatically map the field onto a group. But you might also want to have people send in some kind of "proof’ after registration.  
You could do it manually, code that yourself, [use Pavilion’s custom wizard plugin](https://custom-wizard.pavilion.tech/) for that.

> [@petermarkley](#):
>
> My impression is that the core custom fields feature offers this option only per field (not per user)

That’s true, but you could have users who want to make it public display that field somewhere else, i.e. have a “private” building field and a “public” building field.

---

_[View the full topic](https://meta.discourse.org/t/extend-existing-controller/266411)._