Skip to content

Commit 17f2045

Browse files
authored
Merge pull request parse-community#428 from Pikorua/master
Changed explanation for "Separating App Access Based on User Identity…
2 parents 53729c4 + 1bbf8e5 commit 17f2045

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -211,20 +211,20 @@ To do so, update your `parse-dashboard-config.json` configuration file to match
211211
{
212212
"user":"user1",
213213
"pass":"pass1",
214-
"apps": [{"appId1": "myAppId1"}, {"appId2": "myAppId2"}]
214+
"apps": [{"appId": "myAppId1"}, {"appId": "myAppId2"}]
215215
},
216216
{
217217
"user":"user2",
218218
"pass":"pass2",
219-
"apps": [{"appId1": "myAppId1"}]
219+
"apps": [{"appId": "myAppId1"}]
220220
} ]
221221
}
222222
```
223223
The effect of such a configuration is as follows:
224224

225-
When `user1` logs in, he/she will be able to manage `appId1` and `appId2` from the dashboard.
225+
When `user1` logs in, he/she will be able to manage `myAppId1` and `myAppId2` from the dashboard.
226226

227-
When *`user2`* logs in, he/she will only be able to manage *`appId1`* from the dashboard.
227+
When *`user2`* logs in, he/she will only be able to manage *`myAppId1`* from the dashboard.
228228

229229

230230
## Run with Docker

0 commit comments

Comments
 (0)