DoltLab customer has a use-case where different teams/permission levels of people collaborate across various databases, however, only a small number of teams/people are permitted to make schema changes to these databases.
In DoltLab/DoltHub's current permissions model, there is no way to prevent users from making/proposing changes to schema, while allowing changes to the data.
Additionally, the teams/people who review and approve pull requests that should only be adding data, may also not be authorized to changed the schema.
Existing branch permissions do not help with this use-case either.
Attenuated permissions should ideally be handled at the SQL-server level, and as of now, we don't have a dedicated UX for such functionality. We might not be able to implement this now.
DoltLab customer has a use-case where different teams/permission levels of people collaborate across various databases, however, only a small number of teams/people are permitted to make schema changes to these databases.
In DoltLab/DoltHub's current permissions model, there is no way to prevent users from making/proposing changes to schema, while allowing changes to the data.
Additionally, the teams/people who review and approve pull requests that should only be adding data, may also not be authorized to changed the schema.
Existing branch permissions do not help with this use-case either.