Philleep Florence

I concur and second, @rijkvanzanten... ``` &filter[name]=ivan &filter[birthdate][gte]=1970-01-01 &filter[numbers][]=5 &filter[numbers][]=10 ``` This format is rather important! It would allow for an array of arrays (PHP) or an array of objects...

Using this will cause the first limit parameter to be dropped... `limit=200&limit[categories]=5&limit[authors]=2`. What about a separate variable to hold parameters for related collections? This way it is backward compatible.

> ?limit=500&sort=id&related[categories][sort]=5&related[categories][limit]=2 I like this option! It is keeping the same structure as the main collection parameter, so it should be easy for someone to add params for related collections...

I see your point...what about leaving filter the way it is, but also allow in the nested example? We could pose the question within **Slack** or **Github Discussion** to get...

I concur...

> If we don't care about backward compatibility, we could scope ALL query strings in an array, meaning each query string needs to have a [] after if for the...

It seems the API request may be bypassing the validation of the **user-role** interface if you set all the required permissions. Did you try clicking on the **all** button next...

@Jeremy-Gaillard in the meantime, you can prevent a non-trusted user from reading certain fields in the activity collection. They can see the activity not just all of it. See image...

@kosicielPL I was able to get the role blocked from updates by any user in a non-admin role. You can accomplish that by setting granular permissions on the user collection...

Are you trying to do this via an endpoint or you want to extend the codebase of Directus?