# Creating client portal with separate user data

**URL:** https://community.glideapps.com/t/creating-client-portal-with-separate-user-data/64836
**Category:** Ask for Help
**Created:** [August 9, 2023, 12:59am UTC](https://community.glideapps.com/t/creating-client-portal-with-separate-user-data/64836 "2023-08-09T00:59:13Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)
#### Post date: [August 9, 2023, 1:33am UTC](https://community.glideapps.com/t/creating-client-portal-with-separate-user-data/64836/2 "2023-08-09T01:33:53Z")

</div>

> [@JSC](#):
>
> I set up a Glide \> Google Sheets zap so when the user creates a profile it adds them to a master data sheet but how do I assign those separate spreadsheets to those specific users. e.g. Bob signs up, how do I now assign that list of spreadsheets to Bobs account. Is there a way to automate it so the data is integrated with the new spreadsheet it made on Google Sheets?

hmmm, that sounds a bit dodgy, almost as if you’ve ignored our previous advice?  
Why would each user have his own dedicated set of Google Sheets?  
This would mean that every time you add a user, you’d have to create an entire new set of screens and associated flows and logic in Glide. That will never scale, and that isn’t how Glide is supposed to be used.

The correct way to set this up is with all users “sharing” a single set of tables, and use row owners to segregate the data.

> [@JSC](#):
>
> I need to Glide to able to recognize if someone is a paying subscriber via Stripe. My customers will pay a monthly subscription and I only want subscribers to be able to access the “premium” version of the app. So Glide needs to be able to recognize my “premium” subscribers are different from the free users. According to my attachment I cant do any actions with Stripe \> Glide because Glide cannot be used as a destination app in Zapier. How will I be able to differentiate those users and set up and integration to recognize and allow user to subscribe, cancel, upgrade, and etc.?

This is all very doable. You can update Glide from Zapier via the API. There is a [tutorial in the Docs](https://www.glideapps.com/docs/essentials/data-sources/getting-started-with-the-glide-api) that specifically shows how to work with the Glide API with Zapier.  
You won’t be able to do a subscription model with Stripe on its own, but it can be done by combining with Payhere. @Robert_Petitto has a [template package](https://community.glideapps.com/t/create-a-membership-app-using-payhere/26646/79) that covers this in detail.

---

_[View the full topic](https://community.glideapps.com/t/creating-client-portal-with-separate-user-data/64836)._