Skip to content

feat(admin): console user management with user types #60

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

Closed
jogunjobi wants to merge 1 commit into from
Closed

feat(admin): console user management with user types #60

Show file tree
Hide file tree
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: 8 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,14 @@ record. Entries are grouped by the release that first shipped them.

### Added

- Console users can be managed from the console and the API. Administrators
open **Console Users** to add a user as Administrator, Read-write, Read-only
or Custom (chosen roles), edit their type, reset their password, disable,
enable and delete them. A new user, and a reset, gets a generated temporary
password shown once that must be changed at first sign-in. An administrator
cannot lock themselves out, the last enabled administrator cannot be removed,
and only a disabled user can be deleted. Every change is audited. Before,
adding a console user after deployment needed SQL.
- A read-only console role, `viewer`: it opens every console page and read
API and can change nothing, including dry-runs and connection tests.
- When the console refuses an action, for example a read-only account clicking
Expand Down
Loading
Loading