# Help with splitting an app into two & navigating new privacy / security features,

**URL:** https://community.glideapps.com/t/help-with-splitting-an-app-into-two-navigating-new-privacy-security-features/18230
**Category:** Ask for Help
**Created:** [November 10, 2020, 11:23pm UTC](https://community.glideapps.com/t/help-with-splitting-an-app-into-two-navigating-new-privacy-security-features/18230 "2020-11-10T23:23:32Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Rasha](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rasha/32/4585_2.png) [@Rasha](https://community.glideapps.com/u/Rasha)
#### Post date: [November 10, 2020, 11:23pm UTC](https://community.glideapps.com/t/help-with-splitting-an-app-into-two-navigating-new-privacy-security-features/18230/1 "2020-11-10T23:23:32Z")

</div>

I’d like to separate an app into two, both reading from the same sheet. There are two user groups, we’ll call them vendors and consumers. The new Glide offerings and security/privacy options have left me a little unsure how best to approach the split to avoid major hiccups.

The app I’m splitting is a PRO with a legacy subscription benefitting from the flexibility of a private sign-in option if that makes sense. The diagram lays out the setup I think would work along with some context.

I’ll take comments, general tips, but have **two specific questions here:**

  
1️⃣ Currently, the user profiles sheet contains data for both consumers and vendors. I have a UserRole (access level) column with 2 options: \*\*Vendor & Consumer\*\*. 
- Question: Should this sheet remain as is (one sheet) for both apps or is it better for Vendors and Consumers to have separate user profile sheets for their corresponding apps?  
  

2️⃣ For added security, I considered enabling **Row Owners** , however:

**(a)** Unsure if Vendors (ADMINs) processing individual orders can easily be **added to an array  
column** to access consumer’s info related to an order/order history – this is key.

Aware that computed columns **cannot** be converted to Row Owner columns. Plus the need for a new column for each new ADMIN not ideal.

**(b)** Fairly certain Row Owners prevents users (consumers) from seeing _ **any** _ data related to other users in product reviews, for instance (e.g., profile photo, name).

Addressing this w/ **role-based security** where consumer’s UserEmail is **“Owner 1”** and "ADMIN is **“Owner 2”** translates to a Private app which, again, means not benefiting from user-specific columns.

- Question: has anyone implemented role-based security in a similar context without incident? tradeoffs?  
  

* * *

 ![App_ Admin vs Consumer](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/c/5/c5eb6f05ff76a399d8a8084d69eca7b004b82c3d.jpeg)