--- title: "Device Owners" slug: "device-owners-1" updated: 2026-10-22T15:24:50Z published: 2026-10-22T15:24:50Z canonical: "docs.databee.buzz/device-owners-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.databee.buzz/llms.txt > Use this file to discover all available pages before exploring further. # Device Owners ## Purpose The Device Owners CDP is a mapping table and should be used to join users to devices. Users can have different relationships to a device from business owner, IT owner, asset owner, finance owner, etc. The CDP is ideal for answering questions of who the point of contact is for a device depending on the use case. ## Understanding the Table The table is structured with `device_id` as the main row identifier, the `key` representing the relationship type (BU, IT, ORG_Owner), and the `value` being the `user_id` that correlates with the relationship type. A new row will be created for each unique set of `device_id`, `key`, and `value` Check if `end_time is null` to determine if a user is still responsible for a given device. ## Joining to CDPs and OCSF `Device_id` and `value` should be used to join against other CDPs. ## [Schema](/user-manual/docs/device-owners) ## Example Queries Find all records for a given user or device id ```pgsql SELECT * FROM device_owner where end_date is null and value = {id} ``` ```pgsql SELECT * FROM device_owner where end_date is null and device_id = {id} ``` ## CDP Data Dictionary | **Caption** | **Name** | **Requirement** | **Type** | **Description** | | --- | --- | --- | --- | --- | | Device ID | device_id | required | integer_t | Device.id: The unique identifier used by DataBee for a specific device. This will be logged as `device_id` in activity tables to link to a particular device in this table. This field should not be mapped manually as the DataBee product populates this field itself. | | End Time | end_time | optional | timestamp_t | Device.end_time: The end time of when a particular state of the user was valid. Using the `start_time` and `end_time` together bound the time when a particular user state was valid. If there is no `end_time` it tells the analyst that this is the current state of the user as DataBee understands it. There will ever only be a single user for which the `end_time` is `null`. | | ID | id | required | integer_t | Device.id: The unique identifier used by DataBee for a specific device. This will be logged as `device_id` in activity tables to link to a particular device in this table. This field should not be mapped manually as the DataBee product populates this field itself. Device.owner: The primary owner of a device. Device.additional_owners: Other possible owners of a device. This is added to allow an array of owners, but when there is only one owner, the `owner` field should be populated. | | Owner Label | key | optional | string_t | Device.owner: The primary owner of a device. Device.additional_owners: Other possible owners of a device. This is added to allow an array of owners, but when there is only one owner, the `owner` field should be populated. | | Record Created At | record_created_at | required | timestamp_t | CDPs generated timestamp when record was created. | | Record Updated At | record_updated_at | required | timestamp_t | CDPs generated timestamp when record was last updated. | | Data Sources | sources | optional | string_t Array | Device.owner: The primary owner of a device. Device.additional_owners: Other possible owners of a device. This is added to allow an array of owners, but when there is only one owner, the `owner` field should be populated. | | Start Time | start_time | optional | timestamp_t | Device.start_time: The start time when a particular state of the user became valid. | | Owner User ID | value | required | integer_t | Device.owner: The primary owner of a device. Device.additional_owners: Other possible owners of a device. This is added to allow an array of owners, but when there is only one owner, the `owner` field should be populated. |