-
-
Notifications
You must be signed in to change notification settings - Fork 38
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Initial docs for dashboard permissions, refs #27
- Loading branch information
Showing
2 changed files
with
19 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# Saved dashboards | ||
|
||
A set of SQL queries can be used to create a saved dashboard. Saved dashboards have URLs and support permissions, so you can specify which users are allowed to see which dashboard. | ||
|
||
Saved dashboards currently need to be created using the Django Admin interface. | ||
|
||
Available view permissions are as follows: | ||
|
||
- `private`: Only the user who created (owns) the dashboard can view | ||
- `public`: Any user can view | ||
- `unlisted`: Any user can view, but they need to know the URL (this feature is not complete) | ||
- `loggedin`: Any logged-in user can view | ||
- `group`: Any user who is a member of the `view_group` attached to the dashboard can view | ||
- `staff`: Any user who is staff can view | ||
- `superuser`: Any user who is a superuser can view | ||
|
||
Edit permissions exist in the admin interface but do not yet do anything. Follow [#27](https://github.com/simonw/django-sql-dashboard/issues/27) for progress on this. |