:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Account detail sidebar properties
Each user can pin up to 50 account custom properties, relationships, and account fields in their project.
You can pin any account field that the Accounts list offers as a column, such as the Stripe customer ID or the external ID.
Account fields show the account's value read-only. Use the account editor to change them.
When customer-analytics-account-scene is enabled, the Accounts list also shows these pins in expanded rows.
The left arrow expands or collapses the row. The account name opens account details.
Expanded pins use the same Properties section and editable fields as the account sidebar.
They follow the saved order and wrap horizontally within the table container.
Each property uses its content width, up to 16rem, with a 1rem gap between properties. An open editor uses the full 16rem width.
Field headers reserve equal height with or without an edit button, so read-only and editable values align.
Fixed-layout tables reserve 3rem for the expansion button so the icon does not get clipped.
If no properties are pinned, the Pin properties button opens the selector in place.
Only expanded accounts load property values. The list does not load the legacy detail tabs while this flag is enabled.
With the flag disabled, the existing row expansion and account-name behavior remain unchanged.
The Pin properties button and the Properties gear open the same ordered selector in both views. In expanded rows, the gear sits beside the Properties label. In the sidebar, it stays right-aligned. Only the panel that opened the selector renders it. Saving pins updates every mounted panel in the project. Dragging entries changes their saved display order. The sidebar scrolls independently of the main account content on wide account scenes.
At the top of the sidebar, the left action opens a modal where you add the account to your event stream. If your stream isn't set up or is turned off, the modal links to the event stream settings. The back arrow on the settings page returns to the account. The right action edits the account. The account editor includes the name, website domain, billing ID, Slack channel ID, Salesforce ID, email domains, and known emails. It also includes the Stripe ID when the account already has one. The external ID remains read-only. The external ID shows under the account name on every account page, with a copy button. Saving refreshes the account title and breadcrumb. A failed save keeps the editor open for retry.
Pinned rows load current values for the selected account. Missing custom values display "Not set" and relationships without current assignees display "Unassigned". Loading and failed requests have separate states, with retry available after a failure. The empty configuration does not request account values or relationships, so account-data failures cannot block the Pin properties action. Saving the first pin starts loading values. Refresh failures retain the last loaded rows and any open editor, with a non-blocking retry warning. Only a failed initial load replaces the rows with a blocking error.
Account editors can edit manual and workflow-backed properties inline. Workflow-backed rows warn that a workflow may overwrite a manual change. Warehouse-backed and canonical properties are read-only. Date and datetime pickers provide their own apply and cancel controls; other editors use Clear value, Cancel, and Save.
Clearing a custom value requires confirmation and posts a null value to
POST /api/projects/:project_id/accounts/:account_id/custom_property_values/.
The endpoint returns 204, soft-deletes the current value, and preserves its history.
Warehouse-backed and canonical values reject both manual sets and clears.
A warehouse sync clears a saved custom property when the source row contains an explicit null for that property. The sidebar then displays "Not set". The clear preserves history and emits a property-change event. Repeated nulls do not emit another change event. Missing source rows or columns leave saved values unchanged.
Sets and clears for the same account and custom property share a PostgreSQL transaction lock, including when no active value exists. Sync checks for unchanged values use the same lock. The lock lasts until the outer transaction commits or rolls back. Different account/property keys remain independent. Bulk syncs commit each property separately. This prevents write collisions, but does not coalesce sync jobs or order source snapshots by freshness.
Relationship editors support single and multiple holders. Removing a holder ends the assignment without deleting its history. Multi-holder changes retain unchanged holders. Relationship saves apply the edits relative to the assignments shown when editing began. Concurrent additions and removals are preserved. A retry tracks assignments created by its own partial save, so those can still be removed if the draft changes before retrying. Clearing every holder requires confirmation. Failed saves keep the editor open; after a partial relationship failure, the sidebar reloads current assignments so a retry uses the latest state.
AccountPinnedPropertiesPanel connects both views to the same configuration, loading states, and editors.
AccountPropertyField renders each label, source icon, value, and editor.
Pin preferences belong to accountSidebarConfigLogic, keyed by project.
accountPropertyDataLogic holds live values, keyed by project and account.
accountSidebarPropertiesLogic owns editing state for each property panel.
The Relationships tab and account list refresh after assignment changes.
Successful writes emit the existing custom-property and role-assignment events.
The source is account_sidebar for sidebar edits and list_expansion for expanded-list edits.
Custom-property events exclude property names and values;
role-assignment events retain the existing role metadata and internal-user identifiers.
Properties in account views
With customer-analytics-account-views enabled, the view component picker offers Properties.
Each tile stores its own ordered selection in the view document under config.properties.
The tile's Edit action changes its selection and title through the existing view save flow.
Adding a tile starts with an empty selection.
These selections do not change sidebar pins or project defaults.
Properties tiles show a vertical list of custom properties, relationships, and supported account properties. Tiles use the sidebar's horizontal padding, and editable rows place the pencil beside the property name in both surfaces. A tile shows the first ten visible properties before scrolling vertically to the remaining rows. The scrollbar sits at the card's right edge while property rows keep their horizontal padding. The viewport adjusts to wrapped values, open editors, and width changes. Account properties are website domain, billing ID, Slack channel ID, Salesforce ID, Stripe ID, email domains, and known emails. Stripe ID appears only when the current account already has one. Account name and arbitrary account property keys are not supported. Custom properties and relationships use the same editors and access rules as sidebar rows. Only project admins with account editor access can edit email domains and known emails.
Account property saves use the account editor's fresh-read merge and list normalization. Local account editor and widget saves run in sequence to keep edits to different fields. Saved values refresh visible properties tiles and the sidebar without replacing other editors' drafts. Account reads do not broadcast changes to other editors. A read started before a save cannot replace that saved value. Relationship saves refresh every mounted Relationships tile and refresh the shared property data once. Custom-property saves do not reload Relationships tiles. Each tile keeps separate editor state for the current account. A failed save keeps the input for retry. Loading failures and refresh failures show retry actions, separate from missing values. Deleted property definitions stay in saved selections and show a warning until removed through the tile's Edit action.
Widget edit events record the source and property type, never property names, values, or account identifiers.
Widget values and property selections opt out of autocapture.
The edit source is account_view.
customer analytics account properties widget configured records only the selected property count.