🧭✨Future Application Users (NEW)
✨ NEW TABLE - December 2025
🛠️ Partner API Alignment Migration
🧭 This table represents the post-migration state for
application_users.1️⃣ Migrate to this table by April 2026
2️⃣ Between April 2026 and July 2026, remove FUTURE__ prefix
Contains application user records with associated operator information. Combines user application data with operator details to provide comprehensive user context including team assignments, permissions, and deletion tracking. Includes timestamps for audit trails and marketing preferences.
SQL: FUTURE__application_users
Schema
| Column Name | Data Type | Description |
|---|---|---|
| Primary ID | ||
| id | INTEGER | Primary key |
| Other IDs | ||
| operator_id | INTEGER | Unique identifier for the operator associated with this application user |
| user_id | INTEGER | Unique identifier for the user account |
| application_id | INTEGER | Unique identifier for the application the user has access to |
| default_team_id | INTEGER | Identifier for the user's default team assignment within the application |
| deleted_by_user_id | INTEGER | Identifier of the user who performed the deletion, null if record is active |
| Timestamps | ||
| created_at | TIMESTAMP_NTZ | Timestamp when the application user record was originally created |
| updated_at | TIMESTAMP_NTZ | Timestamp when the application user record was last modified |
| deleted_at | TIMESTAMP_NTZ | Timestamp when the application user record was deleted, null if active |
| terms_read_at | TIMESTAMP_NTZ | Timestamp when the user last read or acknowledged the terms of service |
| operator_deleted_at | TIMESTAMP_NTZ | Timestamp when the associated operator was deleted, null if operator is active |
| application_marketing_emails_accepted_at | TIMESTAMP_NTZ | Timestamp when the user accepted marketing emails for this application, null if not accepted |
Changes from Last Version
Added columns (3):
- default_team_id
- deleted_by_user_id
- operator_deleted_at
Removed columns (0):
- no columns were removed
Renamed columns (0):
- no columns were renamed
Data inclusion criteria
This table works with FUTURE__operators table, requiring that operator_id is among the partner's FUTURE__operators.id records.
Data flow
| Upstream tables | Downstream tables |
|---|---|
FUTURE__operators | FUTURE__users |
Alignment
Partner API
- Aligns with Partner API get/users endpoint
application_users table
application_users tableexclude rows where deleted_at is not null
where deleted_at is nullUpdated 3 days ago
