# DiscourseConnect and user time zone / location

**URL:** <https://meta.discourse.org/t/discourseconnect-and-user-time-zone-location/221461>\
**Category:** WordPress\
**Created:** [March 19, 2022, 10:38pm UTC](https://meta.discourse.org/t/discourseconnect-and-user-time-zone-location/221461 "2022-03-19T22:38:16Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![troygrady](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/troygrady/32/232574_2.png) [@troygrady](https://meta.discourse.org/u/troygrady)\
**Post date:** [March 22, 2022, 4:39pm UTC](https://meta.discourse.org/t/discourseconnect-and-user-time-zone-location/221461/10 "2022-03-22T16:39:40Z")

</div>

Right, we’d like to display arbitrary fields on the user card, generated by WP, relating to the user’s account on the main site — like their homepage URL, and potentially other fields as well. They’re not intended to ever be user-supplied, even during account creation. They’re just inteded to be user-displayed. In our case it sounds like a custom “user” field is the best approach since it already includes display options for profile and card. And the user never sees a signup form anyway.

The edge case would be if you weren’t using SSO — the user would see those fields on the signup form, even though they’re not intended to fill them out. I suppose the workaround there would just be to hide them via CSS?

Anyway for our case, it sounds like we have our solution(s) here. Thank you!

---

_[View the full topic](https://meta.discourse.org/t/discourseconnect-and-user-time-zone-location/221461)._
