Collections and admin_channels/access api

I’m pretty sure I’m correct but just checking that channels are unique to collections so two collections if the user is assigned a channel of a given name say member_123 to each collection it will be treated as two separate channels which happen to have the same name.

e.g. access to mydb.myscope.collection1 and mydb.myscope.collection2

would require the /mydb/_user/:name to have PUT

...
"collection_access": {
    "myscope": {
      "collection1": {
        "admin_channels": [
          "!",
          "member_123"
        ]
      },
      "collection2": {
        "admin_channels": [
          "!",
          "member_123"
        ]
      }
}
...

E.g. You can’t cascade or wildard access either from the default collection or within a scope.

So if a new collection3 is added there is no default channels added ecxept “!” without explicitly setting them. Correct?

Not a big deal just interested.

3 posts - 2 participants

Read full topic