🧭✨Future Teams (NEW)
✨ NEW TABLE - November 2025
🛠️ Partner API Alignment Migration
🧭 This table represents the post-migration state for
teams.1️⃣ Migrate to this table by April 2026
2️⃣ Between April 2026 and July 2026, remove FUTURE__ prefix
Contains detailed team and operator information with associated location and contact details. Filters and organizes team data based on operator relationships and includes key business identifiers. Enriches base team data with operator matching flags for relationship tracking.
SQL: FUTURE__teams
Schema
| Column Name | Data Type | Description |
|---|---|---|
| Primary ID | ||
| id | INTEGER | Primary key |
| Other IDs | ||
| operator_id | INTEGER | References the primary operator associated with this team |
| parent_operator_id | INTEGER | References the parent operator if this team belongs to a hierarchical structure |
| owner_user_id | INTEGER | Identifies the user who owns or manages this team |
| partner_external_id | VARCHAR | External identifier used by the partner system to reference this team |
| Timestamps | ||
| created_at | TIMESTAMP_NTZ | Timestamp when the team record was first created |
| updated_at | TIMESTAMP_NTZ | Timestamp when the team record was last modified |
| deleted_at | TIMESTAMP_NTZ | Timestamp when the team record was marked as deleted, null if active |
| Filters | ||
| is_main_operator_match | BOOLEAN | Indicates if this team is directly linked to the main operator (true) or not (false) |
| is_parent_operator_match | BOOLEAN | Indicates if this team is linked to the operator through a parent relationship (true) or not (false) |
| is_deleted_pii | BOOLEAN | Indicates if a row has PII that have been nullified |
| Attributes | ||
| name | VARCHAR | Display name of the team |
| operator_name | VARCHAR | Name of the associated operator |
| partner_name | VARCHAR | Name of the partner organization |
| country | VARCHAR | Full name of the country where the team is located |
| country_code | VARCHAR | Two-letter ISO country code for the team's location |
| address1 | VARCHAR | Primary street address of the team |
| city | VARCHAR | City where the team is located |
| zip | VARCHAR | Postal code for the team's address |
| VARCHAR | Primary contact email address for the team | |
| company_name | VARCHAR | Legal company name associated with the team |
| vat_number | VARCHAR | VAT registration number for the team's company |
| type | VARCHAR | 'personal', 'professional', 'operator' |
Changes from Last Version
Renamed columns
- team_id → id
- team_name → name
Added columns
- operator matching filter flags:
is_main_operator_match,is_parent_operator_match updated_at
Inclusion Criteria
- the
operator_idorparent_operator_idmust match the partner's operator ID
Data flow
| Upstream tables | Downstream tables |
|---|---|
| none | FUTURE__charges |
FUTURE__charge_points |
Alignment
Partner API
- Aligns with Partner API get/teams endpoint
- the API param
includeDeletedmust be set to true
The teams table
teams table- exclude deleted rows to match the old table
where deleted_at is nullUpdated 1 day ago
