From aa1a96edc26e068823e5ebac349036743a8fd0bb Mon Sep 17 00:00:00 2001 From: anoadragon453 Date: Tue, 16 Aug 2022 16:38:40 +0000 Subject: deploy: 06a27338813371bd17a76947f82b3167c484f2ac --- latest/usage/administration/admin_api/index.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'latest/usage/administration/admin_api/index.html') diff --git a/latest/usage/administration/admin_api/index.html b/latest/usage/administration/admin_api/index.html index 3522a67a49..411e10114c 100644 --- a/latest/usage/administration/admin_api/index.html +++ b/latest/usage/administration/admin_api/index.html @@ -150,7 +150,8 @@

Authenticate as a server admin

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 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.

UPDATE users SET admin = 1 WHERE name = '@foo:bar.com';
 

A new server admin user can also be created using the register_new_matrix_user -- cgit 1.5.1