I plan to invite collaborators to edit a grid via an interface. Must they have editor rights on the admin portal, or can they remain viewers to reduce costs?
Based on my experience managing similar setups in Airtable Enterprise, it’s preferable to assign editor rights to collaborators who require direct input into the grid. While viewers can access data, any editing or modifications would necessitate editor privileges. In our deployment, we balanced functionality and cost by giving limited editor access only to those who actively update records. It might be useful to explore using dashboards or forms for some interactions; however, these workarounds do not wholly replace the need for editor rights if the intention is for direct editing.
In my experience working with Airtable Enterprise, when collaborators need to actively engage with the grid by updating data, it is more practical to grant editor access rather than limiting them to viewer permissions. Although viewer rights might seem like a cost-effective solution for non-editing tasks, they can impede agility and lead to delays if changes are required quickly. I encountered scenarios where teams wasted time requesting modifications through the admin, which disrupted workflow. A balanced approach, favoring editor access for key contributors, has consistently proven more efficient despite the additional cost.
i think if your collabs are actually updating stuff, they gotta be editor even if cost is a bit higher. viewers just cant make changes on the grid. maybe try forms for some data entry, but full edits need proper rights, so keep that in mind.