Base Permission - Possible not to have collaborators copy a base?

[Kim_Trager1]

Im making a airtable system, for a friend of mine.
It deals with quite sensitive data…
Is there a way to make sure an editor can’t just duplicate a whole his base including all records into their own workspace, but still be able to edit records?

[Jack_Butcher]

Did you ever get a response to this issue? We’re facing the same dilemma

[Kim_Trager1]

Unfortunately not.

We’re sofar working under the pretence that no-one would ever think of it being an option… And sofar it haven’t been a problem.
But guess it’s like an insurance; you never need it until it’s too late…

[Andrew_Piotukh]

That’s crazy. It’s a huge security issue. That way the sensitive info of clients can be easily duplicated multiple times by multiple (nested) invites. I cannot understand why Airtable does nothing about it. No need to be genius to steal the whole CRM

[Mike_McLaughlin]

your question is sub-feature of a major long running feature request Advanced User Permissions

[Andrew_Piotukh]

thank you Michael. Do you know if it is possible to see whether the base has been copied? Some kind of history

[Mike_McLaughlin]

I’m pretty sure no, but I’d suggest you try to copy a base with multiple users on it and see if anyone gets a notification that they are part of a ‘new base’

[Dagoberto_Salle]

It is a big problem for us, I can’t understand why we don’t have a way to block “duplicate base” feature.

[Luke_Jasudavici]

Is this still an issues in 2021?

If so, this needs to be addressed. This is kind of a deal breaker.

[Kim_Trager1]

I’m actually not sure, I’ve just continued on the assumption that no-one would do such a thing… :grimacing: