Data LakeHouse: Data Schema

Overview

This reference guide documents all data tables and fields available in the Learn Amp Data Lake. Use this information to build custom reports, dashboards, and integrations.

We're continuously adding new tables and data points—check back regularly for updates.

⚠️ Important: The Data Lake includes data linked to deactivated users and archived content/events. Remember to filter these out if appropriate for your reporting needs.

users

The users table contains details of each user within the company, including deactivated and not yet active users.

Field name	Data type	Description

Field name	Data type	Description
id	Integer	The unique user identifier
sign_in_count	Integer	Count of the total number of times the user has logged in all-time
current_sign_in_at	Timestamp	Timestamp (UTC) of the user's most recent log in
created_at	Timestamp	Timestamp (UTC) when the user was originally created
first_name	String	First name of the user (aka given name)
last_name	String	Last name of the user (aka surname)
job_title	String	Job title of the user (e.g. Marketing Assistant). Can be blank.
language	String	Primary (selected) language for the user in ISO 639-1 format
manager	Boolean	True/false flag to identify whether the user is a manager. Includes both primary team managers and override managers.
time_zone	String	Time zone string for the user's selected time zone (if any).
coach_id	Integer	User id of the user's coach (if any).
is_coach	Boolean	True/false flag to identify if the user is designated as a coach
manager_id	Integer	User id of the user's override manager, or primary team manager if user has no override manager set.
secondary_manager	Boolean	True/false flag to identify if the user is the secondary manager of any team.
hire_date	Date	Hire date of the employee. Only set if this data is available from an HR system integration or similar.
is_override_manager	Boolean	True/false flag to identify if the user is designated as the override manager of another user.
deactivated_at	Timestamp	Timestamp (UTC) for when the user was deactivated
deactivated	Boolean	True/false flag to identify whether or not the user has been deactivated.
system_role	String	System role of the user on Learn Amp.
location_id	Integer	ID for the user's primary location. See `id` in `locations` table.
tenure_in_days	Integer	Total length of the user's tenure in days (Today or Leave Date minus their Hire Date, in days). Will be null if Hire Date has not been set.
leave_date	Date	Employment termination / leave date, if available/applicable.

custom_fields

The custom_fields table contains each custom field value for each user.

Field name	Data type	Description

Field name	Data type	Description
id	Integer	Unique id of the user's custom field. Can be ignored
user_id	Integer	ID of the user that the custom field relates to
custom_field_id	Integer	ID of custom field. This value will be repeated for each occurrence of this custom field
name	String	Name of the custom field, e.g. "Employee Number"
value	String	Value of the custom field for this particular user, e.g. "ABC123"

groups

The groups table contains basic metadata of all groups. A group is a collection of users, defined by a set of filtering criteria. Users are added to groups automatically by the system, and are refreshed on a regular basis.

Field name	Data type	Description

Field name	Data type	Description
id	Integer	Unique ID of the group.
created_at	Timestamp	Timestamp (UTC) for when the group was first created.
name	String	Name of the Group

group_users

The group_users table is a link table, associating users with groups. This table defines who belongs to which groups.

Field name	Data type	Description

Field name	Data type	Description
group_id	Integer	ID of the group, see `id` in `groups` table
id	Integer	Unique ID of the group_user record.
user_id	Integer	ID of the user, see `id` in `users` table
created_at	Timestamp	Timestamp (UTC) for when the given user was added to the given group.

teams

The teams table contains basic metadata of all teams. A team may have a manager and secondary managers. Users may belong to a primary, and many secondary teams.

Field name	Data type	Description

Field name	Data type	Description
id	Integer	Unique ID of the team.
name	String	Name of the team
created_at	Timestamp	Timestamp (UTC) for when the team was first created.
manager_id	Integer	User id of the manager of the team. See `id` in `users` table
parent_team_id	Integer	ID of this team's parent team. Teams may exist within a hierarchy, and have parent and child teams.
team_users_count	Integer	Count of users belonging directly to this team. (Excludes managers)
team_user_caches_count	Integer	Count of users belonging directly to this team AND any of the child teams beneath this team in the hierarchy. (Excludes team managers).
manager_name	String	Full name of the team's manager. This will be identical to `full_name` in `users` table, for the given `manager_id`

team_users

The team_users table is a link table, associating users with teams. This table defines who belongs to which teams.

Field name	Data type	Description

Field name	Data type	Description
team_id	Integer	ID of the team, see `id` in `teams` table
id	Integer	Unique ID of the team_user record.
user_id	Integer	ID of the user, see `id` in `users` table
created_at	Timestamp	Timestamp (UTC) for when the given user was added to the given team.
primary_flag	Boolean	True/false flag to denote whether this is the user's primary team.

locations

The locations table contains basic metadata of all locations.

Field name	Data type	Description

Field name	Data type	Description
id	Integer	Unique ID of the location.
name	String	Name of the location

content

The content table contains basic metadata for all types of content referenced by activities and tasks. Content may belong directly to the company or is shared with the company from a library account.

Field name	Data type	Description

Field name	Data type	Description
created_at	Timestamp	Timestamp (UTC) when the content was first created
content_type	String	Type of the content on the Learn Amp platform. Since Items has multiple types, this field may be different from the `type` field described below. Example content types: video, article, book etc.
name	String	Name (or title) of the piece of content. If the content has a title saved in multiple languages, the name stored here will be the first available translation - beginning with English, then English-USA, and so on.
type_with_id	String	Concatenation of the content's primary `id` with its `type`, in the form: item-123
type	String	The entity type of the content on Learn Amp. Will be one of: Item, Channel, Learnlist, Event, Quiz, Survey

channels

The channels table contains basic metadata of all channels. Channels may include those belonging directly to the company, and those shared from a library account. channels is a subset of the content table, for reporting/listing only channels.

Field name	Data type	Description

Field name	Data type	Description
id	Integer	Unique ID of the channel.
created_at	Timestamp	Timestamp (UTC) for when the channel was first created.
name	String	Name of the channel

events

The events table contains basic metadata of all events. events is a subset of the content table, for reporting/listing only events.

Field name	Data type	Description

Field name	Data type	Description
id	Integer	Unique ID of the event.
created_at	Timestamp	Timestamp (UTC) for when the event was first created.
name	String	Name of the event

items

The items table contains basic metadata of all items. items is a subset of the content table, for reporting/listing only items. In Learn Amp, an item is a single learning object, such as a SCORM package, a downloadable document, a video etc.

Field name	Data type	Description

Field name	Data type	Description
id	Integer	Unique ID of the item.
guid	String	Globally unique identifier. Not used. Please ignore.
source_id	String	If the item came from an external integration or import of content from another system, the source_id may be used to store the unique identifier of the item in that system
source_type	String	If the item came from an external integration or import of content, source_type may be used to store a label/name of that system.
created_at	Timestamp	Timestamp (UTC) for when the item was first created.
name	String	Name of the item