> For the complete documentation index, see [llms.txt](https://docs.sumble.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sumble.com/system-setup-and-configuration/data-destinations/users-table.md).

# Users table (account owners and managers)

If your accounts come from Snowflake, BigQuery, Google Cloud Storage, or S3 rather than a CRM, you can send Sumble a users table so it knows your reps and their managers.

This lets you see account status and filter accounts by CRM data for each rep in the web app. Managers can see their direct reports' accounts, and Sumble can attribute each account to its owner.

## Columns

Include one row per user. You can use any column names; Sumble maps them during setup.

| Column        | Required | Notes                                                           |
| ------------- | -------- | --------------------------------------------------------------- |
| User ID       | Yes      | Must match the identifier in the accounts table's owner column. |
| Name          | Yes      |                                                                 |
| Email         | Yes      | Use the address the rep uses to sign in to Sumble.              |
| Title         | Yes      | A row's title can be blank.                                     |
| Manager ID    | No       | Must match another row's user ID.                               |
| Manager name  | No       |                                                                 |
| Manager email | No       |                                                                 |
| Manager title | No       |                                                                 |

Each successful run reads the full table. Users no longer present are removed from the active user list. If a pull returns no rows while users are already present, Sumble skips removal to protect against an empty result caused by a broken source.