Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Improve documentation on becoming server admin #13230

Merged
merged 5 commits into from
Aug 3, 2022
Merged
Show file tree
Hide file tree
Changes from 4 commits
Commits
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
1 change: 1 addition & 0 deletions changelog.d/13230.doc
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Added steps describing how to elevate an existing user to administrator by manipulating a postgres database.
reivilibre marked this conversation as resolved.
Show resolved Hide resolved
3 changes: 2 additions & 1 deletion docs/usage/administration/admin_api/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,9 @@
Many of the API calls in the admin api will require an `access_token` for a
server admin. (Note that a server admin is distinct from a room admin.)

A user can be marked as a server admin by updating the database directly, e.g.:
An existing user can be marked as a server admin by updating the database directly.

Check your [database settings](config_documentation.md#database) in the configuration file, connect to the correct database using either `psql [database name]` (if using PostgreSQL) or `sqlite3 path/to/your/database.db` (if using SQLite) and elevate the user `@foo:bar.com` to administrator.
```sql
UPDATE users SET admin = 1 WHERE name = '@foo:bar.com';
```
Expand Down