Skip to content

Changed explanation for "Separating App Access Based on User Identity… #428

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 23, 2016
Merged

Changed explanation for "Separating App Access Based on User Identity… #428

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -211,20 +211,20 @@ To do so, update your `parse-dashboard-config.json` configuration file to match
{
"user":"user1",
"pass":"pass1",
"apps": [{"appId1": "myAppId1"}, {"appId2": "myAppId2"}]
"apps": [{"appId": "myAppId1"}, {"appId": "myAppId2"}]
},
{
"user":"user2",
"pass":"pass2",
"apps": [{"appId1": "myAppId1"}]
"apps": [{"appId": "myAppId1"}]
} ]
}
```
The effect of such a configuration is as follows:

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

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


## Run with Docker
Expand Down