# Guest checkout / User Table

**URL:** <https://community.glideapps.com/t/guest-checkout-user-table/83340>\
**Category:** Ask for Help\
**Created:** [July 21, 2025, 6:06pm UTC](https://community.glideapps.com/t/guest-checkout-user-table/83340 "2025-07-21T18:06:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anickl](https://avatars.discourse-cdn.com/v4/letter/a/9de0a6/32.png) [@anickl](https://community.glideapps.com/u/anickl)\
**Post date:** [July 21, 2025, 6:06pm UTC](https://community.glideapps.com/t/guest-checkout-user-table/83340/1 "2025-07-21T18:06:16Z")

</div>

Hello! I’ve been trying to figure this out on my own and I’m coming up with mixed answers.

I’m creating a Glide app to white-label and embed on a company’s website so that their customers can shop on their site. Ideally, I’d like these customers to be able to shop on the site as a guest, no sign-up required, and then enter their email at checkout and can have that set-up an account for them where they’ll be able to see their order history.

Right now, I have the company employees set up in the Users table and they’re set as an Admin and that goes towards our “user” allotment for our Glide app. And then, I created a separate customers table.

My questions:

- Wondering if this is the correct set-up so far, or if I’m way off base?
- What would the customers table set-up look like so that they could shop as a guest and then add their email to sign-up/create an account, view order history, save their shipping address etc.

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [July 22, 2025, 12:31am UTC](https://community.glideapps.com/t/guest-checkout-user-table/83340/2 "2025-07-22T00:31:29Z")

</div>

If you plan for customers to see their order history, that implies they will log in at some point right?

I would store both employees and customers in the same table, and have something like an “appRole” column to differentiate them.

I would have:

- 1 table for line items.
- 1 table for orders, where customers can add their email for linking to their actual profile.
- 1 table for customerAddresses, where you can link back again using the customer email.