This documentation page tells you how to create user accounts on your Matrix server.
Table of contents:
Notes:
USERNAME_HERE and PASSWORD_HEREUSERNAME_HERE, use a plain username like alice, not a full ID (@alice:example.com)admin=yes or admin=no depending on whether you wish to make the user an administrator of the Matrix serverAfter registering a user (using one of the methods below), you can log in with that user via the Element Web service that this playbook has installed for you at a URL like this: https://element.example.com/.
It’s best to register users via the Ansible playbook, because it works regardless of homeserver implementation (Synapse, Dendrite, etc) or usage of Matrix Authentication Service (MAS).
To register a user via this Ansible playbook:
just register-user USERNAME_HERE PASSWORD_HERE <admin access: yes or no>
# Example: `just register-user alice secret-password yes`
or by invoking ansible-playbook manually:
ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=USERNAME_HERE password=PASSWORD_HERE admin=<yes|no>' --tags=register-user
# Example: ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=alice password=secret-password admin=yes' --tags=register-user
Feel free to register as many users (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your user account only (with admin=yes), and others should be created with admin=no.
[!WARNING] If you’re registering users against Matrix Authentication Service, do note that it still insists on having a verified email address for each user. Upon a user’s first login, they will be asked to confirm their email address. This requires that email sending is configured. You can also consult the Working around email deliverability issues section for more information.
If you’re using the Synapse homeserver implementation (which is the default), you can register users via the command-line after SSH-ing to your server (requires that all services have been started):
/matrix/synapse/bin/register-user USERNAME_HERE PASSWORD_HERE <admin access: 0 or 1>
# Example: `/matrix/synapse/bin/register-user alice secret-password 1`
If you’re using the Dendrite homeserver implementation, you can register users via the command-line after SSH-ing to your server (requires that all services have been started):
/matrix/dendrite/bin/create-account USERNAME_HERE PASSWORD_HERE <admin access: 0 or 1>
# Example: `/matrix/dendrite/bin/create-account alice secret-password 1`
If you’re using the Matrix Authentication Service and your existing homeserver (most likely Synapse) is delegating authentication to it, you can register users via the command-line after SSH-ing to your server (requires that all services have been started):
/matrix/matrix-authentication-service/bin/register-user USERNAME_HERE PASSWORD_HERE <admin access: 0 or 1>
# Example: `/matrix/matrix-authentication-service/bin/register-user alice secret-password 1`
This register-user script actually invokes the mas-cli manage register-user command under the hood. If you’d like more control over the registration process, consider invoking the mas-cli command directly:
/matrix/matrix-authentication-service/bin/mas-cli manage register-user --help
[!WARNING] Matrix Authentication Service still insists on having a verified email address for each user. Upon a user’s first login, they will be asked to confirm their email address. This requires that email sending is configured. You can also consult the Working around email deliverability issues section for more information.
To manage users more easily (via a web user-interace), you can install Synapse Admin.
[!WARNING] If you’re using Matrix Authentication Service, note that user management via synapse-admin is not fully working yet. See the Expectations section for more information.
If you’d rather keep your server private (public registration closed, as is the default), and let certain people create accounts by themselves (instead of creating user accounts manually like this), consider installing and making use of matrix-registration.
To open up user registration publicly (usually not recommended), add the following configuration to your inventory/host_vars/matrix.example.com/vars.yml file:
For Synapse:
matrix_synapse_enable_registration: true
For Dendrite:
matrix_dendrite_client_api_registration_disabled: false
After configuring the playbook, run it with playbook tags as below:
ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
Notes:
The shortcut commands with the just program are also available: just install-all or just setup-all
just install-all is useful for maintaining your setup quickly (2x-5x faster than just setup-all) when its components remain unchanged. If you adjust your vars.yml to remove other components, you’d need to run just setup-all, or these components will still remain installed. Note these shortcuts run the ensure-matrix-users-created tag too.
If you’re opening up registrations publicly like this, you might also wish to configure CAPTCHA protection.
To change the admin privileges for a user in Synapse’s local database, you need to run an SQL query like this against the synapse database:
UPDATE users SET admin=ADMIN_VALUE WHERE name = '@alice:example.com';
where:
ADMIN_VALUE being either 0 (regular user) or 1 (admin)USER and example.com pointing to a valid user on your serverIf you’re using the integrated Postgres server and not an external Postgres server, you can launch a Postgres into the synapse database by:
/matrix/postgres/bin/cli — to launch psql\c synapse — to change to the synapse databaseYou can then proceed to run the query above.
Note: directly modifying the raw data of Synapse (or any other software) could cause the software to break. You’ve been warned!
Promoting/demoting a user in Matrix Authentication Service can be done using the mas-cli management tool’s manage promote-admin and manage demote-admin commands. For example: /matrix/matrix-authentication-service/bin/mas-cli manage promote-admin some.username.
You can also do it via the MAS Admin API‘s POST /api/admin/v1/users/{id}/set-admin endpoint.