# GenericForeignKey field not shown in admin?

**URL:** <https://forum.djangoproject.com/t/genericforeignkey-field-not-shown-in-admin/24446>\
**Category:** Using the ORM\
**Created:** [October 10, 2023, 4:58pm UTC](https://forum.djangoproject.com/t/genericforeignkey-field-not-shown-in-admin/24446 "2023-10-10T16:58:06Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![KenWhitesell](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/kenwhitesell/32/280_2.png) [@KenWhitesell](https://forum.djangoproject.com/u/KenWhitesell)\
**Post date:** [October 12, 2023, 3:03pm UTC](https://forum.djangoproject.com/t/genericforeignkey-field-not-shown-in-admin/24446/5 "2023-10-12T15:03:02Z")

</div>

`<opinion>`  
GFKs in general are an anti-pattern, truly useful in far fewer situations than many people believe. (In that sense, I put them in the same category as Django signals.)

I believe they’re supported well-enough, for what they’re supposed to do.  
`</opinion>`

For more on this, see:

- [Avoid Django's GenericForeignKey - lukeplant.me.uk](https://lukeplant.me.uk/blog/posts/avoid-django-genericforeignkey/)
- [Generic relation vs Many to Many - #2 by KenWhitesell](https://forum.djangoproject.com/t/generic-relation-vs-many-to-many/16967/2)

---

_[View the full topic](https://forum.djangoproject.com/t/genericforeignkey-field-not-shown-in-admin/24446)._