Configure

The order to configure Sponsorships in — from the starter records Rhythm creates when you turn it on, through the setup checklist, to your first sale.

Create, change, clone, and delete the add-on products optional sponsorship benefits are billed through, and why an add-on product has no price of its own.

Place the My Sponsorships list and the sponsorship detail element on your Portal, and set the page the list links to.

Create, order, and manage the application processes that define how sponsors apply — which form they fill in, whether they confirm their details first, and whether checkout uses your account's defaults or its own.

Define the reasons staff can give when they change an opportunity's review status on a sponsorship application, and why a reason still in use cannot be deleted.

Set the business unit, accounts, payment methods, and invoice and fee rules every sponsorship purchase uses unless an application process overrides them.

Add the benefits every buyer of an opportunity receives, offer groups of optional benefits to choose from, set expiry and capacity, and charge extra through an add-on product.

Put an opportunity on sale online, set its selling window, require staff approval before a purchase becomes a sponsorship, and write the confirmation and activation emails sponsors receive.

Offer Purchase Sponsorships and sponsorship management in your Portal, place their page-designer blocks, and understand where each one sends members by default.

Allow or refuse Portal viewing and purchasing of sponsorships for each contact role, or for every contact at once, and why a contact role in use cannot be deleted.

Send a test copy of an opportunity's confirmation or activation email, filled in with a real sponsorship's details, to any address you choose, before a sponsor ever sees it.

Define what you are selling to sponsors — name, category, type, event, price, capacity, and selling window — and learn why Rhythm sometimes refuses to save or delete one.

Your account keeps one Sponsorship settings record covering checkout defaults and Portal contact-role permissions, created the first time you save and replaced on every later save.

Assign a Read Only, Day-to-Day User, or Administrator policy to control what a staff member can do in Sponsorships, including who can open Setup and change settings.