Skip to content

Document Chargebee exclude-customers-by-default checkbox - #510

Merged
alvarolivie merged 2 commits into
mainfrom
docs/chargebee-exclude-by-default-checkbox
Jul 29, 2026
Merged

Document Chargebee exclude-customers-by-default checkbox#510
alvarolivie merged 2 commits into
mainfrom
docs/chargebee-exclude-by-default-checkbox

Conversation

@alvarolivie

Copy link
Copy Markdown
Contributor

Summary

  • Documents the new Exclude customers by default checkbox in the Chargebee app configuration form, which flips customer processing from import-all to exclude-all.
  • Explains how this pairs with cf_invopop_include=true to allowlist a subset of customers without back-populating the field in bulk.
  • Reframes the existing back-population guidance as the fallback for those not using the new checkbox.

Test plan

  • Preview the /guides/chargebee page and confirm the "Connect the Chargebee app" step, "Controlling which customers are processed" section, and the custom fields warning all read consistently.

Explains the new app config checkbox that flips the default customer
processing behavior to exclude-all, used alongside cf_invopop_include
to allowlist customers without back-populating the field in bulk.
@mintlify

mintlify Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
invopop 🟢 Ready View Preview Jul 29, 2026, 10:31 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Documents the new Chargebee app option to exclude customers by default, and updates the /guides/chargebee guidance so users can allowlist customers via cf_invopop_include=true without bulk back-population.

Changes:

  • Adds the Exclude customers by default checkbox to the “Connect the Chargebee app” configuration field list.
  • Updates the “Controlling which customers are processed” section to describe the new allowlist flow.
  • Revises the custom fields guidance and warning to explain when back-population is (and isn’t) required.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread guides/chargebee.mdx Outdated
@@ -525,8 +526,12 @@ Finally, you can use the following custom fields to choose which customer's invo
You would typically use either `cf_invopop_include` to allowlist the customers to be imported, or `cf_invopop_exclude` to denylist them, but not both of them. They are optional, though, and if not set, all customers' invoices will be imported.
Comment thread guides/chargebee.mdx Outdated
Clarify the Tip's import-all default now that the new checkbox can
flip it, and standardize boolean/capitalization style in the warning.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

@alvarolivie
alvarolivie merged commit 9469027 into main Jul 29, 2026
3 checks passed
@alvarolivie
alvarolivie deleted the docs/chargebee-exclude-by-default-checkbox branch July 29, 2026 10:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants