phil-w

> The audience is the database id or database url. Maybe you have two different databases - one for prod and one for test? You need to send it to...

Got it - thanks, and I was kind of hoping the checks there were done server side ;-) That's an example I was working through, but the link there gets...

1. I have the /public and /my API things working, but of course they don't need auth beyond the user token. 2. I created some roles using the CLI with...

> Roles can be assigned by realm owners or members that have the permission to {manage: "members"} or specifically to {update: {members: ["roles"]}}. ... >> You may also edit a...

I got through some of this, but I still can't find the key bit of documentation. I tend to end up using google etc to find stuff here. Perhaps separating...

> Roles are set per member, not per user. Unlike users that are server-only - and handled outside the client-server replication, members are replicated and can be update client-side as...

## 1 users I have a single realm, rlm-public. Users can create themselves, and my "super user" can list, edit and delete them using the Dexie Cloud API, through my...

Thanks! That's a different path (from that in the docs which was `/public/roles`), but it doesn't error out, so some progress! An example path is: `/all/roles/%5B%22roles%22%2C%22readonly%22%5D` That returns as JSON...

Thanks for the doc fix, which allowed me to test first the fail case (always the right way!) and then fix & test the other path. That now works. I...

@Wolfhergang, thanks! I'll re-read multiple times that when I get to that point! Perhaps this should be a discussion? - I want my user's data to be shared between sign-ins...