# Users: Matomo Matomo Users Manager Users ## Documentation Every Matomo account able to sign in or hold API/UI permissions on this instance. - Catalog: `Matomo` - Schema: `UsersManager` - Primary Keys: `login` - Label: Matomo Users Manager Users Can retrieve data and change data using insert, update and delete. ## Table Columns The columns of the table `Users` are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `date_registered` | `varchar2` | | ☑ | Date and time the account was created, as returned by Matomo. Matomo does not document which time zone this is expressed in. | | `email` | `varchar2` | | ☑ | Account e-mail address. Required on insert; changing it on update triggers the passwordConfirmation requirement documented below. | | `initial_id_site` | `int32` | | ☐ | Site to grant initial 'view' access to. Required on insert for a non-superuser caller; addUser has no corresponding read-back and updateUser takes no such argument, so this column is insert-only in practice. | | `invite_accept_at` | `varchar2` | | ☐ | Date and time the invitation was accepted, or null while it is still pending or for an account never invited. | | `invite_expired_at` | `varchar2` | | ☐ | Date and time the pending invitation expires, or null once the account is active or for an account never invited. | | `invite_status` | `varchar2` | | ☑ | Account status, for instance 'active' or 'pending'. | | `invited_by` | `varchar2` | | ☐ | Login of the account which invited this user, or null for an account created directly through addUser rather than inviteUser. | | `last_seen_ago` | `varchar2` | | ☐ | How long ago the account last signed in, in Matomo's own human-readable text - absent under the same condition as last_seen. | | `last_seen` | `varchar2` | | ☐ | Date and time the account last signed in, or absent for an account which never has - measured 2026-08-28 on Matomo's own 'anonymous' pseudo-account. | | `login` | `varchar2` | | ☑ | Account login: primary key. Matomo's own getUsers() answers it as 'login'; addUser/updateUser/deleteUser all take it as 'userLogin' instead, hence the explicit updatePath. Assigned by the caller on insert, never renamed afterwards - Matomo has no rename-user method. | | `password_confirmation` | `varchar2` | | ☐ | The connected account's own current password - required by Matomo whenever an update changes email or password, ignored otherwise. Never answered on read. | | `password` | `varchar2` | | ☐ | Account password. Required on insert; optional on update, where an empty value leaves the current password unchanged. Never answered on read. | | `superuser_access` | `int32` | | ☑ | 1 if the account has superuser access, 0 otherwise. Read-only on this table: Matomo grants or revokes it through the separate setSuperUserAccess() call, which this driver does not yet wire up (design chapter 7b, deferred). | | `uses_2fa` | `char` | | ☑ | Whether two-factor authentication is enabled for the account. |