# Protected Columns Impacting Multiple Apps that Utilize Same Airtable Table

**URL:** <https://community.glideapps.com/t/protected-columns-impacting-multiple-apps-that-utilize-same-airtable-table/72996>\
**Category:** Report a Bug\
**Tags:** glide-escalated\
**Created:** [May 1, 2024, 7:46pm UTC](https://community.glideapps.com/t/protected-columns-impacting-multiple-apps-that-utilize-same-airtable-table/72996 "2024-05-01T19:46:03Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![dharmaapps](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dharmaapps/32/88260_2.png) [@dharmaapps](https://community.glideapps.com/u/dharmaapps)\
**Post date:** [May 1, 2024, 7:46pm UTC](https://community.glideapps.com/t/protected-columns-impacting-multiple-apps-that-utilize-same-airtable-table/72996/1 "2024-05-01T19:46:03Z")

</div>

I have 2 apps that reference the same tables in Airtable. The users and functionality of the two apps is quite different, however, the data references are the same.

When I mark columns protected in one app, it’s automatically marking them as protected in the other app as well (something that I do not want to happen). Is this the intended functionaltiy? Is there any way to stop this? I don’t see this referenced in [the Protected Columns docs](https://www.glideapps.com/docs/protected-columns).

My goal: two apps referencing the same Airtable table can have different Protected Columns.

Note: I am able to set Row Owners differently between the two apps.

Thank you!

---

<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:** [May 2, 2024, 12:30am UTC](https://community.glideapps.com/t/protected-columns-impacting-multiple-apps-that-utilize-same-airtable-table/72996/2 "2024-05-02T00:30:08Z")

</div>

Is this intended @NoCodeAndy ? Sounds like a bug to me.

---

<div class="post-metadata">

**Author:** ![dharmaapps](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dharmaapps/32/88260_2.png) [@dharmaapps](https://community.glideapps.com/u/dharmaapps)\
**Post date:** [July 10, 2024, 5:30pm UTC](https://community.glideapps.com/t/protected-columns-impacting-multiple-apps-that-utilize-same-airtable-table/72996/3 "2024-07-10T17:30:13Z")

</div>

I’m still seeing this behavior. @NoCodeAndy can you confirm if this is intentional behavior or a bug?

---

<div class="post-metadata">

**Author:** ![glide](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/glide/32/53398_2.png) [@glide](https://community.glideapps.com/u/glide)\
**Post date:** [July 10, 2024, 11:24pm UTC](https://community.glideapps.com/t/protected-columns-impacting-multiple-apps-that-utilize-same-airtable-table/72996/4 "2024-07-10T23:24:46Z")

</div>

This thread has been escalated. Support will follow up via the Messenger in the Builder or through email.

---

<div class="post-metadata">

**Author:** ![dharmaapps](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dharmaapps/32/88260_2.png) [@dharmaapps](https://community.glideapps.com/u/dharmaapps)\
**Post date:** [July 12, 2024, 5:28pm UTC](https://community.glideapps.com/t/protected-columns-impacting-multiple-apps-that-utilize-same-airtable-table/72996/5 "2024-07-12T17:28:54Z")

</div>

Response from Glide team:

> I heard back from engineering and this is actually the expected behavior with Airtable data sources. Each table in an Airtable database is synced once per team, whereas other data sources (like Google Sheets) are synced per app.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [July 19, 2024, 5:29pm UTC](https://community.glideapps.com/t/protected-columns-impacting-multiple-apps-that-utilize-same-airtable-table/72996/6 "2024-07-19T17:29:25Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
