MicroStrategy ONE
User Hierarchy
lu_account
The lu_account table is designed to integrate Users from multiple data sources such as MicroStrategy metadata users, Usher, Physical Access Systems (PACS) into a common user identity. The Account is linked to a User based on a common email address form. If no email address is available, the account_login will be used. For example, if two metadata’s with the duplicated MicroStrategy user objects are being monitored by Platform Analytics, the accounts will be linked based on the login.
Each user from different sources will have an auto-generated account_id by the Platform Analytics ETL. Any MicroStrategy executions/manipulations or Usher transactions will be tracked at the Account level. As new data sources are added to Platform Analytics, the lu_account table will be expanded to integrate the new data sources into a single User identity.
A User is the unique identity of the person. Each User can have multiple Accounts from different data sources. For example, multiple badges from Usher and the user objects created in the metadata of the MicroStrategy Platform. The User attribute allows analysis on all of the user information across these different data sources.
Account Type will distinguish from which source the account was created. For example, MicroStrategy User or a specific network.
The Account Status will distinguish if the Account is Active, Deleted, Pending, or Inactive.
The Account Role is specific to Badge and is populated by the privileges granted through Network Manager for the specific badge. The account role indicates if the badge has Administrator or Standard access. For MicroStrategy accounts, the default value is Standard.
|
Column |
Description |
Data-type |
|---|---|---|
|
account_id |
The unique account id is the auto-generated ID for the accounts in different data sources. |
bigint(20) |
|
account_name |
The name of the specific account. A single user can have multiple accounts from different systems (Badge, MicroStrategy, Physical Access, etc). |
varchar(255) |
|
account_email |
Multiple accounts are linked to a single user based on the common email address. |
varchar(255) |
|
account_login |
The account login or domain name of the account. |
varchar(255) |
|
account_picture |
The uploaded URL of the picture of the account. A User with multiple badges can have multiple pictures. A MicroStrategy metadata account cannot have a picture. This column does not resolve the image. |
varchar(1024) |
| account_picture_large | The uploaded picture from the Account intended to be embedded in an HTML format. The picture for the account with height = 635 pixels. A user with multiple badges can have multiple pictures. | varchar(1024) |
| account_picture_small | The uploaded picture from the Account intended to be embedded in an HTML format. The picture for the account with height = 72 pixels. A user with multiple badges can have multiple pictures. | varchar(1024) |
|
creation_timestamp |
The UTC timestamp when the account was first created. For MicroStrategy metadata users, this is the timestamp when the user was created. For Badge, this is when the badge was created in Network Manager. |
datetime |
|
account_role_id |
ID of the account role. This column is specific to Badge and is populated by the badge privileges granted through Network Manager for the specific Badge account. The account role indicates if the badge has Administrator or Standard access. For MicroStrategy accounts, the default account role is MicroStrategy User. See lu_account_role for more details. |
int(11) |
|
account_status_id |
ID of the account status. This column is common for both MicroStrategy and Badge accounts. An account can be: Inactive Enabled Disabled Deleted Pending - Specific to Badge users who have been sent but not retrieved a badge. |
tinyint(4) |
|
account_type_id |
ID of the account type. The account type indicated the source of from where the account originated. For MicroStrategy accounts, the ID will be a static value and the default name is MicroStrategy User. For Badge accounts, the ID is generated through Network Manager. |
bigint(20) |
|
network_id |
ID of the network corresponding to the account. For MicroStrategy accounts, the ID will be a static value and the default name is MicroStrategy Network. For Badge accounts the Network ID is generated through Network Manager and corresponds to the badge name. |
bigint(20) |
|
user_id |
Auto-generated ID of the user that the accounts corresponds to based on the common email address. |
bigint(20) |
|
mstr_user_guid |
The GUID of the User object in MicroStrategy metadata |
varchar(32) |
|
account_title |
The title of the Badge account added through Network Manager. |
varchar(255) |
|
account_phone |
The phone number of the Badge account used for device enrollment. |
varchar(75) |
|
longitude |
The most recent longitude value of the Badge account. |
double |
|
latitude |
The most recent latitude value of the Badge account. |
double |
|
last_action_timestamp |
The most recent action timestamp of the Badge account. |
datetime |
|
last_location_timesta mp |
The most recent location timestamp of the Badge account. |
datetime |
|
modification_timesta mp |
The UTC timestamp when the account was last modified. For MicroStrategy metadata users, this is the timestamp when the user object was last modified. |
datetime |
|
account_desc |
The description of the account. |
varchar(512) |
| mstr_user_version | The version ID of the MicroStrategy user. | varchar(32) |
|
ldap_link |
The link to the account in LDAP. |
varchar(512) |
| nt_link | The link to the account in NT. | varchar(255) |
|
wh_link |
The link to the account in the WH. |
varchar(255) |
| password_expiration_frequency | How often a password wille xpire for the given account. | int(11) |
|
password_expiration_date |
The date the password for the account will expire. |
datetime |
| password_change_allowed | Whether the password for the account is allowed to be changed. | varchar(7) |
|
password_change_required |
This account is required to change its password on the next login. |
varchar(7) |
| standard_auth_allowed | This account is allowed to login via Standard Authentication. | varchar(7) |
|
trusted_auth_user_id |
The ID of the trusted authentication user. |
varchar(255) |
| metadata_id | The auto-generated ID for the metadata that this user belongs to. | bigint(20) |
lu_account_role
The Account Role indicates the level of access or privileges for the Account. This table is specific to Badge and is populated by the badge privileges granted through Network Manager for the specific badge. For more information, see Role Management. For MicroStrategy metadata accounts, the default value is MicroStrategy User.
|
Column |
Description |
Data-Type |
|---|---|---|
|
account_role_id |
ID of the account role. |
int(11) |
|
account_role_desc |
The level of privilege for the account. This column is specific to Badge and is populated by the badge privileges granted through Network Manager for the specific Badge account. An account role can be: Badge Administrator Access Badge Standard Access MicroStrategy User (the default value for MicroStrategy accounts) |
varchar(255) |
lu_account_status
The current Account Status of an Account. This column is common for both MicroStrategy and Badge accounts. The account status can change over time, for example an account can begin as active and is later updated to be deleted.
|
Column |
Description |
Data-Type |
|---|---|---|
|
account_status_id |
ID of the current account status. |
tinyint(4) |
|
account_status_desc |
The current status of the account. An account status can be: Inactive Pending- specific to Usher and indicated that an account was sent a badge via email, but it is pending badge recovery on the mobile device. Deleted Disabled Enabled |
varchar(25) |
lu_account_type
The Account Type will distinguish from which data source the Account was created. For example, a MicroStrategy user in the metadata or a specific badge name added through Network Manager (see Badge Name).
|
Column |
Description |
Data-Type |
|---|---|---|
|
account_type_id |
ID of the account type. For MicroStrategy accounts, the ID will be a static value. For Badge accounts, the ID is generated through Network Manager. |
bigint(20) |
|
account_type_desc |
The account type indicated the source of from where the account originated. MicroStrategy User - the user was created in the metadata MicroStrategy Guest User <Badge Name> - the name of the badge added in Network Manager. |
varchar(255) |
|
network_id |
ID of the network corresponding to the account type. For MicroStrategy accounts, the ID will be a static value and the default name is MicroStrategy Network. For Badge accounts the Network ID is generated through Network Manager. |
bigint(20) |
lu_user
A User is the consolidated identity of multiple Accounts. Each User can have multiple accounts from different sources. For example, multiple badges from Badge or users created in the metadata of the MicroStrategy platform. The User attribute allows analysis on all of the user information across these different data sources.
Multiple accounts are linked to a single User based on a common email address(if available) or login. For MicroStrategy metadata users, the email address is added from Developer under the User Editor > Deliveries category > Addresses section. For Badge, the email address is added through Network Manager (see Importing Users). If two or more accounts share a common email address, they will be linked to a single User. For determining the user_name, the first account processes will be used.
Each User can be enriched with an HR organization hierarchy. However, this is not essential for analysis. In case no HR organization information is added, default values will be assigned.
|
Column |
Description |
Data-Type |
|---|---|---|
|
user_id |
The auto-generated numeric ID of the user. |
bigint(20) |
|
user_name |
The first account name that was processed in the ETL. A user can have different account names for the same user, i.e. John Smith and Jonathan Smith linked to the same email address. In this case, the first account_name will be used for the user_name. |
varchar(255) |
|
user_login |
The email address is primarily used to link multiple accounts to a single user identity. If email address is not available, the user_login is used to identify a link between users. |
varchar(255) |
|
user_email |
The email address used to link multiple accounts to a single user identity. |
varchar(255) |
|
manager_id |
MicroStrategy internal use. |
bigint(20) |
|
department_id |
Auto-generated ID of the department. The department information is populated through a CSV file. |
int(4) |
|
department_owner_id |
The employee number for the department head in which the user belongs. |
bigint(20) |
|
division_id |
Auto-generated ID of the division. The division information is populated through a CSV file. |
int(4) |
|
division_owner_id |
The employee number for the division head in which the user belongs. |
bigint(20) |
|
group_id |
Auto-generated ID of the group. The group information is populated through a CSV file. |
int(4) |
|
group_owner_id |
The employee number for the group head in which the user belongs. |
bigint(20) |
|
unit_id |
Auto-generated ID of the unit. The unit information is populated through a CSV file. |
int(4) |
|
unit_owner_id |
The employee number for the unit head in which the user belongs. |
bigint(20) |
lu_network
A Network is a group of connected accounts. The Network is configured through Network Manager. For MicroStrategy metadata users, a default network called MicroStrategy Network is assigned.
Additionally resources (gateways, applications, spaces, desktops) are stored to the network level.
|
Column |
Description |
Data-Type |
|---|---|---|
|
network_id |
Auto-generated numeric ID of each Network. |
bigint(20) |
|
network_desc |
The organization name entered when creating a new network through Network Manager. |
varchar(255) |
|
network_status |
The status of the Network. A network can be active or deleted. |
varchar(25) |
|
creation_timestamp |
The timestamp for when the Network was first created. |
datetime |
|
modification_timestamp |
The latest timestamp of when the Network has been modified. Modifications can include actions such as, changing the badge properties, adding additional users or enabling Physical Access. |
datetime |
lu_validating_account
This table is a view on the lu_account table. A Validating Account is specific to Badge and represents peer-to-peer authentications. An account can be validated through scanning a QR code or entering the Badge Code of another badge. The Badge Code is unique to each user and can be configured to change routinely. For example, this code can be given over the phone to identify yourself if you are talking to someone who does not know you. By default, the Badge Code is 4 or 8 digits in length and updates every hour.
|
Column |
Description |
Data-Type |
|---|---|---|
|
validating_account_id |
The numeric ID of the account who has been validated by another user. |
BigInt(20) |
|
validating_account_name |
The name of the account who has been validated by another user. |
varchar(255) |
|
validating_account_email |
The email of the account who has been validated by another account. |
varchar(255) |
|
validating_account_picture |
The picture of the account who has been validated by another account. |
varchar(1024) |