# Two separate user tables? **URL:** \ **Category:** Ask for Help\ **Created:** [October 26, 2022, 10:14am UTC](https://community.glideapps.com/t/two-separate-user-tables/52603 "2022-10-26T10:14:58Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [October 26, 2022, 12:11pm UTC](https://community.glideapps.com/t/two-separate-user-tables/52603/2 "2022-10-26T12:11:54Z")
Technically no. There is only one user profile table as far as glide is concerned. You would either have to join both user types into one table, or create a hybrid system. You could still have a basic user profile table with RowID, name, email, and image, but then create a separate candidates table and a separate company table. Then you can use relations to link the user profile table and the other two tables together. Check out @Robert_Petitto’s video to see how he created a private user profile table with a public user table. > [@locked\_with\_key Secure Your Data with Row Owners and Public Profiles](https://community.glideapps.com/t/secure-your-data-with-row-owners-and-public-profiles/52139): > > wave Hey fellow Gliders! Are you using Row Owners and Public Profiles to secure your user data? If not, you might accidentally expose private info. Let’s fix that. In this important tutorial, I demonstrate how and why to enable Row Owners, create a Public Profiles table, and onboard new users in order to safely create a community app that doesn’t reference the User Profile table. [[Glide: Secure Your Data with Row Owners and Public Profiles] ](https://www.youtube.com/watch?v=JPgZeDSPQMw) You can also reference this article in… --- _[View the full topic](https://community.glideapps.com/t/two-separate-user-tables/52603)._