Advanced User Permissions

[Jonathan_Fuller]

Again running into issues with not having more granular control of User Permissions. Wondering if this is on the Roadmap and if so (Though I know you can’t say when) is it one of the higher priority items?

You all are awesome. Thanks!

[FourDots]

Would be nice if Airtable exposed it’s roadmap in a public table in Kanban view :slightly_smiling_face:

[Chantal_Carter]

Is there any update on this?

[nnnnneil]

Does this help? What's new - Airtable

[Jarvis]

The What’s New is a good list for new features, but he’s probably looking for something like this:

[Karo_Castro-Wun]

+1 Looking to restrict Collaborator Acces to tables

[Garland_Coulson]

No, this doesn’t solve the problem because the viewer can just view it but can’t edit it or add comments.

We need to create views that a staff member or client can work in where they ONLY see their own tasks.

I don’t want one staff member to be start questioning why someone else got the assignment and they didn’t.

And a task like “Prepare to terminate Bob next week” can be seen by everyone instead of just the HR person you wanted to get things ready.

[Jarvis]

Haha, seems like an oddly specific example :stuck_out_tongue:

[David_Isaac]

Having experience managing permissions in other systems, I agree with keeping it simple.

My use case: restrict the ability to approve an item (e.g., update the “approved” column on an expense request or vacation request) to a group (managers). Another: limit the ability of a group of users (say employees) to see a specific table (say salary data) while still allowing access to other related info (say, employee contact info).

A simple way to accomplish both of these is to put view/edit permissions on tabs. I could combine that with linked records and lookups to accomplish everything I need, with much less complexity than view/column permissions. Tabs could inherit permissions from the base, or have their own.

[Tom_Lowe]

Adding my voice to requests for table-level permissions:

We have two categories of data that we use - call them “programming” and “operational”.

Programming data needs to be edited by lots of people and inaccuracy is not too bad of a problem. Operational data only needs to be edited by two people who know what they’re doing. Inaccuracy here is a business-breaking problem, so we can’t currently keep it under the same permissions as the Programming data.

Unfortunately the operational data contains some core entities that are relevant to almost everything in Programming world. This means that we need to maintain a second version of the operational data in the programming base - with all the attendant problems that brings.

If we were able to use airtable as the source of truth for our operational data, we would potentially never consider moving to a “Real” database. However this bifurcation means that we can only ever see airtable as a flexible interim solution until we can move to a classic relational database.

[Gil_Nimmegeers]

'+ 1 for this feature.
Role management (permission management) on tab/view level would help a lot!
You could use airtable for that :winking_face: #airtableception