I’d like to be able to run queries, aggregations, and analyses on the User Table content. Obvious use cases that come to mind would be to generate email or SMS distribution lists, check for abberant unique values, and provide dashboards to make user activity visible to non-admin folks.
Got it, Jim, keep the great ideas coming 
1 Like
Based on this suggestion, @Beth can you confirm that there’s no way to do a Query on the User Table? If that’s the case, how would you use the Custom Fields if there’s no way to look up the information? The use case I am trying to use is to have a unique ID (sort of like the Badge ID) which is assigned to the user and I need to look up that Unique ID associated with the User object type.
Hi @gbzOA !
Currently you cannot do a query on the User Table like you can a normal Tulip Table. The custom fields could still be helpful, however, because you can access them in trigger logic when interacting with the User Table and or you can use them to store information about each user for reference.
However, if you want to lookup an associated ID for a specified user, it may be best to make a Tulip table with the user information and then you can use queries and aggregations to do that (but I understand that is a not necessarily an ideal workaround, and the Tulip Team is looking into this product suggestion!)
Got it, thanks for the explanation!
1 Like
I wanted to follow up here that I was able to create a Custom Widget that passed in the User object type and then output the ID which is part of the user javascript object.
1 Like
@gbzOA thats awesome!! Thank you for sharing your workaround here. If you are willing to share the actual Custom Widget you made, that could be really helpful for other Community members. We have a Show and Tell - Tulip Community category and you could post the code directly or upload the CW file directly if you’d like 
Is the Users Table info (standard fields + Custom Fields) available through an API?
No Users API currently. Tulip has considered this (based on feedback here: Vote for the next Public Tulip API) but it is currently not a high priority among some of the other work the team has going on.
Current recommendation is to put user information in a normal Tulip Table and then you would be able to do normal queries / aggregations and use Table API there.
This is becoming an issue for us in many different apps. We want to be able to limit the user list in a single select field dependent on the facility a user is assigned to in the custom user fields. Having a query option in the user table would allow us to use the user table as the source of truth for any user information instead of having an alternate table. It is quite a task to manage user data in two places. Is there any plans for implementing this in the near future?
As a secondary note, I thought about using user groups to create a subset of users for a single select…but user groups are not listed in the selection options. This would be a great addition as well.
I think I have posted about this before, but for posterity,
In the absence of any progress on the Tulip Users table, I would recommend that anyone relying on the Tulip user table switch to their own created “Users” table. This is unfortunately more work and triggers but offers the amazing flexibility and exportability that regular tulip tables have.
The easiest way to maintain this table is to have On App Enter triggers in all of your apps which will create or load a record in your users table based on either the badge ID or the email of the logged in user. At this point you can use your custom Tulip Table in the exact same way that you would use the users one. There are some small downsides, but in general this will give you everything you need and more.
Happy Tulip-ing!