> ## 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.

# September 2026

> September 2026 releases: Introw Pay settles a whole payout batch from one invoice, per-property visibility on shared pipelines, a rebuilt form Automation tab with three approval modes, the Introw bot in Microsoft Teams, and agents that update deals through your own action buttons.

> September is the month money started moving. Introw Pay takes a payout batch from one invoice to every partner paid, in their own currency, with verification done per partner. Around it, the rules you set for partners got stricter and easier to read: a deal property can decide when it shows, a form's automation reads top to bottom, and the agent updates deals through the same buttons a partner would.

Commissions were the last part of the program that still scaled with headcount. Introw calculated what each partner earned and grouped it into a batch, and then finance spent the week paying it out one transfer at a time. That week is what Introw Pay removes, which is the [low total cost of ownership](/why/low-tco) bet applied to the money itself. The rest of the month tightened the same idea elsewhere: the person who owns the program should be able to say what a partner sees, how much an agent decides, and where a conversation happens, without a dev ticket in between.

### Pay every partner from one invoice with Introw Pay

Commission plans already worked out what each partner earned, and a payout batch already grouped it per partner with a statement behind it. What came next was still finance's week: one transfer per partner, a spreadsheet handed over each cycle, and bank details chased by email. **Introw Pay** takes that over. On a batch, choose **Pay now** and Introw issues one consolidated invoice to your company, one line per partner. You pay it by bank transfer, once. Introw Pay then sends each partner their share in their own currency, moves every payout from **Pending payment** through **Scheduled** to **Paid**, regenerates the statement in the partner's currency, and emails them when the money is on its way.

Partners set themselves up once per vendor, from the **Commissions** section of your portal. The first payable payout shows them the amount waiting and a **Link a bank account** button. Introw Pay verifies who they are and confirms the bank account the money should land in, so your team never collects or stores any of it. On your side each payout carries a **Payment details** row reading **Not connected**, **Incomplete**, **Verified**, **Restricted** or **Deauthorized**, the batch filters on **KYC ready**, and **Remind to set up payouts** nudges the partner champion, at most once per payout per day. Partners who are not ready are left out of this invoice and stay in the batch for the next run.

Every movement of money, your invoice in and each partner payment out, is a row on the new **Payments** tab with a status from **Open** to **Completed**, **Failed** or **Reversed**. Finance pays one supplier invoice a cycle instead of running hundreds of transfers, which is the [low total cost of ownership](/why/low-tco) bet applied to the one part of commissions that still grew with your partner count. Verification per partner, inside the payment engine rather than in your inbox, is what makes it hold at five hundred partners, which is the [enterprise-grade](/why/enterprise-grade) bet in the same place.

You switch it on in **Payout Settings**, where **Introw Pay** is one of the two options under **How will payments be sent to partner?**. It needs your company currency in EUR or USD and complete billing info. **Manual invoicing** stays exactly as it was for finance teams that own payments themselves. Introw Pay is included in every plan, with a percentage fee on the transactions it processes and nothing extra on your subscription. It is being switched on per organisation while we complete the rollout, so ask your Introw contact if it is still locked in Payout Settings. See [Introw Pay](/features/commissions/introw-pay/technical), [Pay a payout cycle with Introw Pay](/features/commissions/introw-pay/guides/pay-partners-with-introw-pay), and [Get partners ready to be paid](/features/commissions/introw-pay/guides/get-partners-ready-to-be-paid).

### A deal property that shows only when it matters

Each property on a shared pipeline can now carry its own visibility conditions. Open the property's menu in the pipeline configuration, choose **Configure visibility**, and set conditions on the record's other properties, next to the existing **Show on card** toggle. Conditions are evaluated per record against the CRM values, so a discount field appears only once a deal reaches negotiation, and a loss reason shows only on a deal that is Closed lost. It applies on the portal deal card and detail, in the table view, where a hidden cell reads as a dash, and on the HubSpot partner card. The properties that drive the pipeline itself, the stage, the pipeline, the primary and sorting properties and the totals, always show, and the menu says why. The Salesforce embed does not apply these conditions yet.

In August, custom action buttons learned to appear only from the stage where they make sense. Properties learning the same thing closes the loop: you can now shape both what a partner sees on a deal and what they can do to it from one screen, per record. The same caveat applies. This is a relevance control, not a permission, and what a partner is allowed to see and change is still governed by segments and permissions. Configuring it yourself, per property, is the [low total cost of ownership](/why/low-tco) bet applied to the pipeline. See [Set up a shared pipeline](/features/co-selling/shared-pipelines/guides/set-up-a-shared-pipeline) and [Pipeline rules](/release-notes/pipeline-rules).

### The form's Automation tab, rebuilt around the record it writes

A form's **Automation** tab is now organised as **Submission**, **Review**, **Notifications** and **Records written**, with each block named for what it does: **Identify submitter**, **Confirmation screen**, **Notify your team**, **Channel conflict check**, **Approval gate**, **Reply to submitter** and **Partner automation**. A CRM record automation reads top to bottom: which record it targets, with **Match or create** as the default next to match only or the submitter's own company or contact, **Match on these fields**, **Default values** to fill in if not known, **Partner links**, and then the form fields.

The approval gate is now three cards instead of two nested toggles. **Manual** sends every submission to your approvers, with no AI. **AI Assisted** has the AI advise while you decide. **Autonomous AI (Agentic)** lets the AI clear the routine cases while you handle the rest. Nothing changed underneath; what changed is that how much the agent decides on a form is one visible choice rather than a combination you had to reason about, which is the [AI-native](/why/ai-native) bet with the human where you put them. A Salesforce lookup such as the primary partner contact also now fills from the contact the same submission created. See [Connect a form to your CRM](/features/forms/crm-automations/guides/connect-a-form-to-your-crm) and [Run a submission approval workflow](/features/forms/submissions-approvals/guides/run-a-submission-approval-workflow).

### Agents update deals through your own action buttons

In August the portal agent learned which action buttons your shared pipeline carries. It now uses them everywhere a partner can talk to it. When a partner asks to change a deal, from the portal, from Claude or ChatGPT through Partner Connect, or from the HubSpot partner app, the agent routes the change through the custom action button you configured, such as **Move to next stage**, and respects that button's visibility conditions. The guardrails, approvals and automations you built for the button apply to the agent as well, and it only falls back to leaving a comment when no button applies. An agent that acts within the same rules as the partner it acts for is the [AI-native](/why/ai-native) bet done properly. See [Partner support agent](/features/ai/partner-support/technical) and [Let partners update a deal with guardrails](/features/co-selling/shared-pipelines/guides/let-partners-update-a-deal-with-guardrails).

### The Introw bot answers in Microsoft Teams

In August the Introw app in Teams learned to answer **help** and **setup**. It now carries a conversation. It posts a welcome card when it is installed in a personal chat, a setup card in a chat that is not yet linked to an Introw account, and in a team or group chat it replies whenever you mention it. Ask a connected tenant for **partners** or **deals**, or to **register a deal**, and the agent takes it from there, with links that render as proper Teams links. Your Microsoft identity is linked when you connect, so a Teams sign-in that uses a different email from your Introw login still resolves to you, and partner contacts on another domain are recognised in shared channels. Shared channels now appear in the channel picker and resolve to the tenant that hosts them. Introw is still added to Teams as a custom app while the store listing is pending. Meeting your team in the chat tool it already has open is the [work where you already are](/why/work-where-you-are) bet. See [Connect Microsoft Teams](/features/integrations/chat/guides/connect-microsoft-teams) and [Configure partner notifications in Microsoft Teams](/features/engagement/channels/guides/configure-partner-notifications-in-microsoft-teams).

### Also in this release

* **The asset library filters and sorts by Included in**, so you can pull up everything a portal actually embeds, and **Date added** now sorts on the date the asset was added. See [Build the asset library](/features/content/asset-library/guides/build-the-asset-library).
* **HubSpot CRM-only users get the whole conversation.** A deal email to a CRM-only seat now opens the collaboration view inside HubSpot, and an @mention on a deal comment reaches them like any other collaborator. See [Invite a team member](/features/access/team-management/guides/invite-a-team-member).
* **English (UK) is a portal language**, distinct from **English (US)**, and existing UK records stay UK. See [Multilingual](/features/localization/multilingual/technical).
* **Only known AI clients can connect over MCP.** Claude, ChatGPT, Cursor, Windsurf, Notion AI, Lovable, Langdock, Gemini and desktop clients on a local address register on their own; an unknown hosted client is refused. See [Connect an MCP client](/features/developer/mcp/guides/connect-an-mcp-client).
* **A form's CRM record filters apply to partners too.** A form limited to one pipeline now only offers, and only accepts, records in it, in the portal and over the API. See [CRM automations](/features/forms/crm-automations/technical).
* **Salesforce dependent picklists follow the controlling field**, so a State list shows the options for the selected Country, multi-select fields honor the dependency, and two fields on one property keep their own options.
* **A quote form prefills the deal's current stage** from the CRM again.
* **The partner import reports every record** as imported or skipped with the reason, and selecting a partner you deleted earlier restores it instead of skipping it. See [Partner management](/features/partners/partner-management/technical).
* **The Intercom launcher is gone from the partner portal** and from preview, so it no longer sits over the corner of a partner's screen.
* **Refreshing a portal link keeps you signed in** on subdomains and custom domains, and a login that is not authorized no longer creates a contact in your CRM.
* **Link assets embed when the source allows it** and open in a new tab when it does not, and Loom share links play inline. See [Asset library](/features/content/asset-library/technical).
* **AI certificate backgrounds stay clean.** A generated background no longer paints text or a fake certificate of its own. See [Generate a certificate with AI](/features/courses/certificates/guides/generate-a-certificate-with-ai).
* **A custom domain stays up through a DNS provider hiccup.** Health is checked hourly and the badge reads **Certificate issue** when the certificate is the problem. See [Connect a custom domain](/features/portal/custom-domains/guides/connect-a-custom-domain).
* **Salesforce stage filters are dropdowns again** on data views, and every configured stage property shows up in the filter list.
* **Publishing an experience is fast again** for large organisations.