Add access controls to Connections to limit who can use the Connection to create a dataset. Envision 3 options (1) Full Control which allows editing connection (2) Allow, which would allow the user to create a dataset using the connection (would likely also need Author role) and (3) Disallow, would prevent the user from creating a dataset using Connection.
Use case. Connection created to the primary database to replicate Classic DDR reports. Current functionality allows any Author to create a dataset if they know the DB table name (can be found in the SQL in the DV Developer reporting). Need to limit which DB tables Authors can use, as datasets bypass row-level security in RPD for confidential data.