We have an issue where sometime we want to only give read access to a table within a schema. I was wondering if boundary has the ability to control those sorts of access permissions.
For instance there’s a read only user that Carmen can connect to, but we only want her to be able to read part of a specific schema.
This kind of ability will come later with credential integration with Vault (and eventually others). You’ll be able to have Vault create dynamic secrets on the fly and inject them into the session.
I can’t give a timeline on this yet but it’s something we’re actively working on.