I have a table called “articles” where I’m using “row owner” with user’s email. So far so good.
I recently performed a bit of refactoring and started using statuses from another table, in order to have something smarter than just text. See screenshot below.
The problem is that now users don’t see the status at all - if I remove row owner, they do.
Actually I figured something out. Turn out the column is user-specific. I didn’t select that. For a reason I can’t remove the user specific setting, nor create non-user specific columns. It’s selected by default and greyed out.
You can only set a column as user specific when it’s created. Due to the differences in how user specific and non user specific columns work, you cannot change them after they have been created. You will need to recreate the column.
I’m not sure I follow how a user specific column applies to your issue with row owners. They are different things and work differently. As for row owners, if a user does not have ownership of a row, then they will not have any kind of access to unowned data. It doesn’t matter how many relations/lookups you use. If that data is not owned, then it’s not even sent to the end user’s device for the relation/lookup to look at.
You are right, row owner and user specific should not have anything to do with one another.
About your solution: my problem is that I can NOT create non-user specific columns at all. I have deleted all user-specific columns, but still not way to add a non-user-specific column. Is it because I am using an Airtable table?
I don’t know much about Airtable, and it’s been a bit flaky lately. I assume you are adding a column through the Glide data editor? You may need to create the column through Airtable. That’s not the normal way to do it, but for now that may be your only option.
