> ## Documentation Index > Fetch the complete documentation index at: https://docs.introw.io/llms.txt > Use this file to discover all available pages before exploring further. # June 2026 > June 2026 release: segments replace per-contact roles as the audience model, partner teams go multi-person, the first public API ships, and commissions bill. > The most significant release of the half. Segments became the one way to target audiences across Introw, replacing per-contact roles, partner teams went multi-person, and the first public API went live. The through-line was scale and openness: a targeting model that grows with the program instead of fighting it, team structures that match how real partner accounts work, and an API that lets customers build on top of Introw. ### Segments become the audience model Segments are now the single way to control who sees what, gating announcements, asset access, course enrollments, portal tabs, and more, with static segments for hand-picked groups. This is the release where per-contact portal roles became segments. A role was one static label set by hand; a segment is a reusable, CRM-driven audience that maintains itself and is used across the whole product. That is what lets a program scale to thousands of partners without anyone keeping lists current, and it is our [CRM-native](/why/crm-native) and [low-TCO](/why/low-tco) bets in one change. For the full reasoning and what to check, see [Roles are now segments](/release-notes/roles-are-now-segments) and [Segments](/features/partners/segments). ### Multi-person, multi-role partner teams You can now put several people on a partner with different roles, and use them dynamically across experience variables, deal owners on form submissions, the team section in the partner experience, announcement authors, and certificate issuers. Real partner accounts have more than one stakeholder, and modeling that faithfully, straight from your CRM, is part of being [enterprise-grade](/why/enterprise-grade). Roles can map to a CRM property, so who owns a partner stays in the system of record. See [Wire partner ownership](/features/partners/team/guides/wire-partner-ownership). ### The first public API Version one of the Introw API is live, with documentation at [developers.introw.io](https://developers.introw.io). Enterprise buyers rarely want an island, so an API that lets them manage partners and wire Introw into their own stack is a requirement for moving upmarket, and a core piece of being [enterprise-grade](/why/enterprise-grade). Version one covers partners, commission lines, and payouts, with keys scoped to only the resources they need and revocable instantly. See [Create and manage API keys](/features/developer/api/guides/create-and-manage-api-keys). ### Commissions tied to your billing Stripe and Chargebee now work as data sources for commission plans, so commissions couple directly to paid invoices in your billing platform. Paying partners off real, paid revenue removes a manual reconciliation step and the disputes that come with it, and keeps the numbers trustworthy end to end. It is the [CRM as the system of record](/why/crm-native) extended down to the invoice: paid revenue in, correct commissions out. Introw imports customers, subscriptions, and invoices from the billing platform as a commission data source, on a schedule or on demand. See [Connect billing data](/features/integrations/billing/guides/connect-billing-data) and [Commission plans](/features/commissions/commission-plans). ### More control over how you reach partners Email and Slack configurations are aligned so you can enable or disable updates per object, and custom email domain (in early access) lets you send partner email from your own domain. Both give [enterprise-grade](/why/enterprise-grade) programs the control and the branding they expect over outbound communication. See [Control who gets notified](/features/engagement/notifications/guides/control-who-gets-notified) and [Send notifications from your own domain](/features/portal/email-domain/guides/send-notifications-from-your-own-domain). ### WhatsApp as a partner channel Partners can now work with you over WhatsApp, chatting and taking action through an in-channel `@Introw` agent ("share this \$20k deal for me") on the app they already keep open, with no portal setup on their side. For many partners, especially outside North America, WhatsApp is the channel they actually check, so meeting them there is often the difference between a deal move happening now or next week. Reaching partners on their own channel rather than pulling them onto one of ours is the [work-where-you-are](/why/work-where-you-are) bet in its purest form. See [Communication tools](/features/partner-connect/communication-tools). ### Also new * Partner Connect now shows which partners have connected their CRM and lets you nudge the rest, so more partners [work in the tools they already use](/why/work-where-you-are). See [Partner CRM](/features/partner-connect/partner-crm). * Generate document translations with AI, and AI Agents now work natively on PPTX, DOCX, and XLSX files, viewable in the browser and used as context. This is the [AI-native](/why/ai-native) bet reaching the file formats partners actually send. See [Translate a document](/features/content/asset-library/guides/translate-a-document). * Archive items you are done with, and reopen them when you need them again. * Your CRM integration now only fails when nothing works at all, and highlights each individual mapping that stops working, so one changed field no longer stalls the whole sync. See [Troubleshoot a CRM connection](/features/integrations/crm/guides/troubleshoot-a-crm-connection).