# Overview

In our example, the user "Oliver Adams":

  • Has the user UUID "3d0f1348-612a-4804-b632-24c4b871e76e". It was generated by the system upon creation of the user.
  • Has the role with the role UUID "9891264d-4a77-4fa2-ae7f-84c9af14ae3b" assigned.
  • Was created in the account with the account UUID "9891264d-4a77-4fa2-ae7f-84c9af14ae3b".
  • Has a "description" field with user-defined attributes of the user in form of key-value pairs:
    - key: It must match the regular expression(opens new window) ^[a-z_][0-9a-z_]{0,63}$.
    - value: JSON compliant value.
  • Has a "activity" field with the name of the Timeseries table ("user_activity_log") where the User Activity Log of this user is to be stored.
Attribute Type Description
uuid string User UUID.
name string Name of the user. It must match the regular expression(opens new window) ^[0-9A-Za-z][0-9A-Za-z_ \-]{0,30}[0-9A-Za-z]$. It does not need to be unique in the context of the account.
account string Account UUID.
role string Role UUID.
description dictionary Attributes of the user in form of key-value pairs:
- key: It must match the regular expression(opens new window) ^[a-z_][0-9a-z_]{0,63}$.
- value: JSON compliant value.
For more details consult the description field section.
created_ts timestamp Time at which the user was created. Measured in seconds (to three decimal places) that have elapsed since the Unix epoch(opens new window).
updated_ts timestamp Time at which the user was last updated. Measured in seconds (to three decimal places) that have elapsed since the Unix epoch(opens new window).

Was this article helpful?