Sorry, I should’ve mentioned that in advance:
There are several documents in testcollection, added at first through the atlas webinterface but later on also successfully with the user in question through the api. Accordingly the user does have write access to the collection and the privileges work correctly. (Also if I change the privilege to a different Collection for the user and try again through the api, I get an appropriate error from Atlas, so I’m definetely accessing via said user)
Still, I can’t see any Collection with the user in Compass, also when setting the privilege to a different non-empty Collection. Only when I grant readWrite for the whole database I can see all Collections, even empty ones, in Compass.
If it’s important: I simply copied the connection string from Cluster -> Connect -> Connect using MongoDB Compass and filled in the credentials. The end of the connection string also shows /test, so the correct database is addressed. The version of Compass is 1.21.2 and thereby above 1.12.
After adding the string to Compass, it added some things like “…Compass&retryWrites=true&ssl=true” which look to me like simply the default parameters.
I also verified multiple times that I don’t have a typo somewhere: The collection I see at Cluster -> Collections in the webinterface is definitely called test.testcollection and the MongoDB role for the user is stated to be “readWrite@test.testcollection”.