# Add custom user fields to App Info data

**URL:** <https://community.tulip.co/t/add-custom-user-fields-to-app-info-data/14030>\
**Category:** Product Suggestions\
**Tags:** users, user, user-fields\
**Created:** [March 4, 2025, 10:57am UTC](https://community.tulip.co/t/add-custom-user-fields-to-app-info-data/14030 "2025-03-04T10:57:26Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![fti](https://avatars.discourse-cdn.com/v4/letter/f/fbc32d/32.png) [@fti](https://community.tulip.co/u/fti)\
**Post date:** [March 4, 2025, 10:57am UTC](https://community.tulip.co/t/add-custom-user-fields-to-app-info-data/14030/1 "2025-03-04T10:57:26Z")

</div>

Greetings.

I’ve noticed today that, surprisingly, user custom fields are not available from the _ **App Info** _ data in the app editor. This currently forces me to read them via a table record on the _ **Users Table** _ table, which is annoying.

Have I missed something? If not, I think this would be a valuable addition.

---

<div class="post-metadata">

**Author:** ![thorsten.langner](https://avatars.discourse-cdn.com/v4/letter/t/4bbf92/32.png) [@thorsten.langner](https://community.tulip.co/u/thorsten.langner)\
**Post date:** [March 4, 2025, 12:39pm UTC](https://community.tulip.co/t/add-custom-user-fields-to-app-info-data/14030/2 "2025-03-04T12:39:29Z")

</div>

In Triggers you have the fields available under “user”.

For displaying as Widget, you are right. You need to provide that data by a trigger or a record Placeholder.

---

<div class="post-metadata">

**Author:** ![fti](https://avatars.discourse-cdn.com/v4/letter/f/fbc32d/32.png) [@fti](https://community.tulip.co/u/fti)\
**Post date:** [March 4, 2025, 1:34pm UTC](https://community.tulip.co/t/add-custom-user-fields-to-app-info-data/14030/3 "2025-03-04T13:34:02Z")

</div>

@thorsten.langner You are correct 🙂 I was in a situation where I didn’t want to use triggers though. Also, this would be very interesting to have in buttons’ _ **Enabled state** _ expressions.

---

<div class="post-metadata">

**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\
**Post date:** [March 4, 2025, 2:30pm UTC](https://community.tulip.co/t/add-custom-user-fields-to-app-info-data/14030/4 "2025-03-04T14:30:52Z")

</div>

Hi Fabien, I understand your suggestion. It is tricky to find the best place for User Fields- one thing that distinguishes them from other user info is that you can actually write to them from an app, unlike other user metadata and other things within App Info. So, this was our best way to indicate that they are more similar to table records.

---

<div class="post-metadata">

**Author:** ![fti](https://avatars.discourse-cdn.com/v4/letter/f/fbc32d/32.png) [@fti](https://community.tulip.co/u/fti)\
**Post date:** [March 4, 2025, 3:25pm UTC](https://community.tulip.co/t/add-custom-user-fields-to-app-info-data/14030/5 "2025-03-04T15:25:50Z")

</div>

@kevin.kononenko So, if I understand things right, this sounds more like wishing to have a neat and tidy approach rather than a technical impossibility. I totally understand the importance of this.

Some random ideas:

- A) Find another name for _App Info_ to reflect that some of its content can be updated?
- B) Create a new _Users_ category for users if we consider they are neither an app info nor a variable nor a table record?
- C) Always have the _Users Table_ listed in the _Records_ tab with a _Logged-in User_ table record?

I tend to like C since it is both logical and probably close to true technically. If anyone reading this has a suggestion, I’d be happy to hear it.

---

<div class="post-metadata">

**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\
**Post date:** [March 4, 2025, 7:30pm UTC](https://community.tulip.co/t/add-custom-user-fields-to-app-info-data/14030/6 "2025-03-04T19:30:03Z")

</div>

Yes, I think option C is the preferable solution here. Will review this internally and reply with updates on this thread.
