> ## 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.
# Every automation that runs out of the box
> A full inventory of what Introw automates without a workflow: partner detection, property and tier sync, segments, portal access, records, learning, incentives, messaging, and AI.
Most of the automation a partner program needs is already in Introw, and most of it starts working the moment your CRM is connected. This inventory lists it area by area: what each automation does, whether it is on by default or something you switch on, and where it is configured. Read it before you build anything on the [Workflows](/features/automation/workflows) canvas, because the list of rules you actually have to build yourself is shorter than it looks.
## What you'll achieve
A complete, checkable picture of Introw's out-of-the-box automation, so you can switch on the pieces your program needs, stop enforcing them by hand, and reduce your workflow backlog to the rules that are genuinely specific to how you run partnerships.
## Before you start
Most of this list is a consequence of the CRM connection. See [CRM integrations](/features/integrations/crm).
**Always on** needs no switch, only configuration. **Switch on** is off until you enable it, because it changes what partners receive or what happens to your data. **Build it** means there is no built-in automation and a workflow is the answer.
## Partners and their people
Everything here follows from partner detection, and it is the layer worth getting right first: it decides who your partners are and what data the rest of the program automates against.
| Automation | What it does | State | Where |
| ---------------------- | ------------------------------------------------------------------------------------------------------------ | --------- | ----------------------------------------------------------------------------------------------------------- |
| Partner detection | A CRM object plus filters decide which records are partners; only matching records become partners in Introw | Always on | [Detect partners from your CRM](/features/partners/partner-management/guides/detect-partners-from-your-crm) |
| Automatic partner sync | New CRM records matching your filters become partners on their own, with no import to re-run | Switch on | CRM settings |
| Contact import | The contacts on a detected partner's company arrive under the partner's **People**, ready for portal access | Always on | [Provisioning](/features/access/provisioning) |
| Owner suggestion | The partner's CRM account owner is suggested as a team member to accept and set as their manager | Always on | [Wire partner ownership](/features/partners/team/guides/wire-partner-ownership) |
| Attributed records | Deals, tickets, and custom objects linked to a partner appear on their record and in their portal | Always on | [Configure deal attribution](/features/co-selling/shared-pipelines/guides/configure-deal-attribution) |
| Two-way property sync | Mapped partner properties travel between Introw and the CRM in the direction you set | Always on | [CRM integrations](/features/integrations/crm) |
| Tier sync | A tier assigned in Introw is written to a CRM property, and a tier already set in the CRM flows in | Switch on | [Build a tier program](/features/partners/tiers/guides/build-a-tier-program) |
| Partner-edited fields | Fields you make editable are written straight back to the CRM when a partner changes them | Switch on | [Set up a shared pipeline](/features/co-selling/shared-pipelines/guides/set-up-a-shared-pipeline) |
## Audiences
| Automation | What it does | State | Where |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------ | --------- | ------------------------------------------------------------------------------------------------ |
| Dynamic segments | Conditions over live partner, contact, and CRM data are re-evaluated on a schedule, so membership follows the data | Always on | [Create a dynamic segment](/features/partners/segments/guides/create-a-dynamic-segment) |
| Segment-driven notifications | Recipients for every notification event are decided by the organisation default and per-segment overrides | Always on | [Control who gets notified](/features/engagement/notifications/guides/control-who-gets-notified) |
| Segment-driven access | Portal tabs, content, and assets appear only for the segments you scope them to | Switch on | [Restrict a tab to segments](/features/portal/portal-access/guides/restrict-a-tab-to-segments) |
| Segment-driven pricing | Tier and segment discounts apply themselves to the right partners' quotes | Switch on | [Set tier-based discounts](/features/cpq/discounts/guides/set-tier-based-discounts) |
Segments are the single highest-leverage automation in Introw, because so much keys off them. A dynamic segment is also the way to trigger on things no event names directly: "quiet for 30 days", "crossed a revenue threshold", "certified but not transacting". Define the segment, then point a workflow's **Segment membership** trigger at it.
## Portal access
| Automation | What it does | State | Where |
| -------------------------- | ------------------------------------------------------------------------------------------ | --------- | --------------------------------------------------------------------------------------------------- |
| Access from a CRM property | A CRM contact property decides which contacts get portal access, so access follows the CRM | Switch on | [Map contact portal access](/features/integrations/crm/guides/map-contact-portal-access) |
| Domain-based access | Anyone on the partner's verified domain can reach the portal without an individual invite | Switch on | [Set up portal access](/features/portal/portal-access/guides/set-up-portal-access) |
| Portal SSO provisioning | A partner signing in through SSO is provisioned into the right portal on first login | Switch on | [Set up portal SSO](/features/access/sso/guides/set-up-portal-sso) |
| Team SCIM provisioning | Your own team members are created, updated, and deactivated from your identity provider | Switch on | [Provision your team with SCIM](/features/access/provisioning/guides/provision-your-team-with-scim) |
## Records and submissions
| Automation | What it does | State | Where |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------- |
| Form to CRM | A submission creates or updates the CRM objects behind it, from the field mapping you set | Switch on | [Connect a form to your CRM](/features/forms/crm-automations/guides/connect-a-form-to-your-crm) |
| Record matching | Submissions are matched against existing CRM records and update them instead of creating duplicates | Switch on | [CRM automations](/features/forms/crm-automations) |
| Partner attribution | Everything a submission creates is attributed to the partner who sent it | Always on | [CRM automations](/features/forms/crm-automations) |
| Fill if empty | Enrichment fields only write where the CRM has no value, so partner input never overwrites your data | Switch on | [CRM automations](/features/forms/crm-automations) |
| Approval routing | A submission is routed to reviewers, and accepted, declined, or returned before anything lands | Switch on | [Run a submission approval workflow](/features/forms/submissions-approvals/guides/run-a-submission-approval-workflow) |
| Conflict detection | A registration overlapping a deal already in your CRM is flagged with an assessment and a recommendation | Switch on | [Catch and resolve channel conflict](/features/ai/channel-conflict/guides/catch-and-resolve-channel-conflict) |
| Watched-property updates | You choose which properties count as a change, so partners are told when something meaningful moves, not on every sync | Switch on | Pipeline section, **Notifications** |
## Journeys and tasks
| Automation | What it does | State | Where |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------ | --------- | ----------------------------------------------------------------------------------------------------------------------- |
| Journey on experience | A journey attached to an experience is applied as partners get that experience, so onboarding starts on its own | Switch on | [Auto-apply a journey from the experience](/features/partners/journeys/guides/auto-apply-a-journey-from-the-experience) |
| Task due dates | A journey's tasks get their due dates from days-after-assigned, so every partner's dates are right for when they started | Always on | [Build a journey from scratch](/features/partners/journeys/guides/build-a-journey-from-scratch) |
| Task reminders | Partners are reminded about assigned tasks that are coming due | Switch on | [Notifications](/features/engagement/notifications) |
| Progressive unlocking | Completing onboarding moves a partner into the segment that unlocks the next set of content and tabs | Switch on | [Build a progressive onboarding path](/features/partners/onboarding/guides/build-a-progressive-onboarding-path) |
## Learning
| Automation | What it does | State | Where |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------- | --------- | --------------------------------------------------------------------------------------------- |
| Auto-enrollment | Every partner in the segments you attach is enrolled in the course, including partners who join the segment later | Switch on | [Configure enrollment rules](/features/courses/enrollments/guides/configure-enrollment-rules) |
| Auto-issued certificates | A certificate attached to a course is awarded on completion, gated on the passing score where the course sets one | Switch on | [Create a certificate](/features/courses/certificates/guides/create-a-certificate) |
| Progress sync | Course progress and certificates are written back to the CRM | Always on | [Progress tracking](/features/courses/progress-tracking) |
| Incomplete-learner nudges | Learners who started but did not finish are reminded | Switch on | [Nudge incomplete learners](/features/courses/enrollments/guides/nudge-incomplete-learners) |
| Certificate expiry | A certificate with a validity period expires on its own, so recertification is visible rather than assumed | Always on | [Certificates](/features/courses/certificates) |
## Incentives and money
| Automation | What it does | State | Where |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------- |
| Earned commission lines | Plans generate lines from CRM and billing data as deals close and invoices are paid, against your eligibility rules and rates | Switch on | [Build and launch a commission plan](/features/commissions/commission-plans/guides/build-and-launch-a-commission-plan) |
| Recalculation on change | A change to the CRM or billing record behind a line re-evaluates that line rather than leaving a stale amount | Always on | [Review and adjust commission lines](/features/commissions/commission-lines/guides/review-and-adjust-commission-lines) |
| Automatic payout runs | Payout batches advance on the schedule you set instead of someone starting each one | Switch on | [Configure commission payout settings](/features/commissions/settings/guides/configure-commission-payout-settings) |
| Payout status sync | Payment and transfer events from your billing provider move the payout's status on their own | Always on | [Connect Stripe](/features/integrations/billing/guides/connect-stripe) |
| Affiliate attribution | Link clicks and conversions are attributed to the right partner and campaign, with fraud checks | Switch on | [Set up affiliate conversion tracking](/features/affiliate/conversion-tracking/guides/set-up-affiliate-conversion-tracking) |
| MDF lifecycle | Requests, approvals, claims, and remaining budget move through the fund without a spreadsheet | Switch on | [Funds and allocation](/features/mdf/funds-allocation) |
## Messaging
| Automation | What it does | State | Where |
| ----------------------- | -------------------------------------------------------------------------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------- |
| Lifecycle notifications | Deal, task, submission, learning, and commission events reach the audiences you scoped | Switch on | [Every notification Introw sends](/features/engagement/notifications/guides/every-notification-introw-sends) |
| Sleeping-deal nudges | A deal sitting in a stage past your inactivity window prompts the responsible partner | Switch on | [Nudge stalled deals](/features/engagement/notifications/guides/nudge-stalled-deals) |
| Off-portal delivery | Notifications reach partners by email and in each partner's mapped Slack or Teams channel | Switch on | [Channels](/features/engagement/channels) |
| Reply-by-email | A partner replying to a notification has their reply tracked back onto the record for every collaborator | Switch on | [Configure partner notifications by email](/features/engagement/channels/guides/configure-partner-notifications-by-email) |
| Referrer updates | The partner who referred a deal is kept up to date as it moves, with no manual status email | Switch on | [Keep referrers updated](/features/referrals/deal-updates/guides/keep-referrers-updated) |
## AI
| Automation | What it does | State | Where |
| ------------------------ | ------------------------------------------------------------------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------ |
| Partner support agent | Partner questions are answered from your own content, wherever the partner asks | Switch on | [Launch the partner support agent](/features/ai/partner-support/guides/launch-the-partner-support-agent) |
| Deal coaching | A deal notification carries a specific next step, not just the fact that something changed | Switch on | [Set up an AI deal coach](/features/ai/deal-coaching/guides/set-up-an-ai-deal-coach) |
| Announcement suggestions | Your partner-relevant LinkedIn posts arrive weekly as announcement drafts, rewritten for partners | Switch on | [Publish AI-suggested announcements](/features/engagement/announcements/guides/publish-ai-suggested-announcements) |
| Knowledge crawling | Your public content is crawled and kept in the agent's knowledge base so answers stay current | Switch on | [Fill the knowledge base](/features/ai/knowledge-base/guides/fill-the-knowledge-base) |
## What is left to build
After all of the above, the rules that still need a [workflow](/features/automation/workflows) are the ones tied to your own program design rather than to the mechanics of running a partner program:
* **Promotion on achievement.** Tier a partner up, add them to a segment, and log it in the CRM when they certify or finish onboarding. See [Reward a finished journey](/features/automation/workflows/guides/reward-a-finished-journey).
* **Deadline chases with escalation.** Remind the partner before a task is due, again after it slips, and hand it to the partner manager. See [Chase a task to its due date](/features/automation/workflows/guides/chase-a-task-to-its-due-date).
* **Fixed rewards.** A flat bonus for an action, rather than a percentage of a deal. See [Reward a finished journey](/features/automation/workflows/guides/reward-a-finished-journey).
* **Reacting to your own CRM fields.** A partner's segment, region, or program field changing in the CRM moving them onto a different experience. See [React to a CRM change on a partner](/features/automation/workflows/guides/react-to-a-crm-change-on-a-partner).
* **Multi-step re-engagement.** A sequence that nudges, waits, checks whether it worked, and only then involves a human. See [Re-engage quiet partners](/features/automation/workflows/guides/re-engage-quiet-partners).
## Verify it worked
Walk the list against your own program and you should be able to point at each row and say "on, off on purpose, or not for us". The test that the built-in layer is doing its job: new partners appear without anyone importing them, your partner list and the CRM agree, segment membership is current, submissions arrive as CRM records rather than as messages someone retypes, and the reminders your partners get are ones nobody sent.
## Related
Build the rules the built-in layer does not cover.
The full catalog of automatic messages, with triggers and recipients.
Set up the detection and sync layer everything else follows from.
Build the audiences the rest of the program keys off.