|
See slack thread for customer issue and employee testing done, linked intercom chat above.
- Note the linked chat and thread is related to customer use case where they wish to:
- connect to their cluster using a configured Atlas built-in role Read DB user scoped to specific db and associated collection(s)
- view documents in collection using Compass
- Currently the customer_cannot see any collection(s_) in Compass sidebar (showing as 0) and also on the main navigation they see the DB namespace but no collections
-
- As a temporary workaround, customer was directed to use mongo shell, but customer wishes to use Compass to see data in graphical user interface (not the built-in MongoSH component)
- Internal testing done shows that the same behavior surfacing when using any of the Compass stable and beta version
- Inquiring as to whether this is due to command listCollections (see listed permissions for read DB user) being unavailable for the DB user 'read' privileges which in turn is affecting the collection view access in Compass ?
|