Is it possible to automate the status of read-only interface collaborators? For example, when the status of a collaborator changes to 'inactive' in my base, I'd like to remove them as collaborators on all interfaces. When their status changes to 'active', I'd like to remove their access to Interface B but preserve their read-only access to Interface A.
Solved
Auto script to manage interface collaborators
Best answer by kuovonne
Those endpoints for adding or deleting collaborators are only available to people on Enterprise plans. They also are part of the web API, not part of scripting. Although it is technically possible to access the web API with scripting, it is not secure.
Thus, it is not realistic to use scripting to control access.
However, you can set up your fields and interfaces to only show records to active users. Have a table of users where you store the status of each user. Link users to their records in other tables. Use conditional lookup fields to include only users who are active. Then in the interface, filter the records to only include records where the current user is in the conditional lookup.
Inactive users would still have access to the interface, but would not be able to see any records.
+18There appear to be an API endpoints for this, so it should be possible, yeah:
https://airtable.com/developers/web/api/add-interface-collaborator
https://airtable.com/developers/web/api/delete-interface-collaborator
TheTimeSavingCo wrote:
There appear to be an API endpoints for this, so it should be possible, yeah:
https://airtable.com/developers/web/api/add-interface-collaborator
https://airtable.com/developers/web/api/delete-interface-collaborator
I did see this, but it is not clear to me how to integrate these into a script. Could you provide an example of what it would look like in the script?
+17Those endpoints for adding or deleting collaborators are only available to people on Enterprise plans. They also are part of the web API, not part of scripting. Although it is technically possible to access the web API with scripting, it is not secure.
Thus, it is not realistic to use scripting to control access.
However, you can set up your fields and interfaces to only show records to active users. Have a table of users where you store the status of each user. Link users to their records in other tables. Use conditional lookup fields to include only users who are active. Then in the interface, filter the records to only include records where the current user is in the conditional lookup.
Inactive users would still have access to the interface, but would not be able to see any records.
kuovonne wrote:
Those endpoints for adding or deleting collaborators are only available to people on Enterprise plans. They also are part of the web API, not part of scripting. Although it is technically possible to access the web API with scripting, it is not secure.
Thus, it is not realistic to use scripting to control access.
However, you can set up your fields and interfaces to only show records to active users. Have a table of users where you store the status of each user. Link users to their records in other tables. Use conditional lookup fields to include only users who are active. Then in the interface, filter the records to only include records where the current user is in the conditional lookup.
Inactive users would still have access to the interface, but would not be able to see any records.
Thank you! That is essentially what I have done, was just hoping for a more complete removal of access without having to manually remove.
Reply
Most helpful members this week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.