As of April 12th, you must go to Progress SupportLink to create new support cases or to access existing cases. Please, bookmark the SupportLink URL and use the new portal to contact the support team.
Either use the master secret (not recommended in client-side apps), or apply [read-write permissions](http://devcenter.kinvey.com/html5/guides/security#Entitylevelpermissions) to the users you want to update. Then, you should be update to update other users than the user you’re currently logged in as.
a
agpoweredmg
said
about 9 years ago
Thanks Mark, after posing the question I read about the acl modifications in the security guide and figured that would probably be the suggested route to take. I appreciate the confirmation.
a
agpoweredmg
said
about 9 years ago
A second question. Could you explain what I need to do with the entity variable that is shown in the code samples. I'm not a 100% sure what the 'prop: 'value' is referring to/needs to reference.
M
Mark
said
about 9 years ago
The `{ prop: 'value' }` is just an example of an entity. For example, if you were to have an app showing books, your entity most likely looks similar to:
```
var bookEntity = {
title: 'Book Title',
author: 'Book Author'
};
var acl = new Kinvey.Acl(bookEntity);
```
Basically, to obtain the ACL of an entity, you call `new Kinvey.Acl` and pass in the entity.
a
agpoweredmg
said
about 9 years ago
So in order to give one specific user from the 'users' collection full read/write access to the collection. Would I have to run a loop to update the acl specifically on each entity or is there a way to pass the collection its self as an entity?
M
Mark
said
about 9 years ago
Right now, yes, the ACL has to be applied to each entity. Improving support for collection-wide ACL is however on our list of things to do.
agpoweredmg