Luma Event Creation x Build & Brew

Launch a campus Build & Brew event with Luma registration and club promotion.

Introduction

30 Second Summary

Campus events get confusing when details change across posts. One clear source keeps everyone on the same page.

In this project, you will launch a real Build & Brew event with Luma as the single registration destination. You will promote the same event through LinkedIn, eligible Meetup, Slack, and Discord.

What You'll Build

Open your finished event as an attendee to see the session details and register through one reliable Luma link.

By the end of this project, you'll have:

A live registration page where attendees can understand the Build & Brew session before securing a place.
A registration flow with a campus capacity and waitlist. NextWork appears as a host only through approved attribution.
A consistent event message across public listings and campus channels. Every call to action leads back to the same Luma page.
Secret Mission: Clone the finished Luma event into the next Build & Brew session without copying registrations.

Are there any prerequisites?

Bring a confirmed Build & Brew topic with a tentative schedule and venue or remote meeting details. You need LinkedIn and Meetup accounts with posting access to your club's Slack and Discord channels. Use an approved program contact only if NextWork should appear as a host.

Before We Start

This is your moment to commit to one real Build & Brew session before the hands-on work begins. Your launch commitment connects the topic, intended attendees, chosen format, and reason for running the session.

Set Up Your Campus Launchpad

Your launch commitment gives this Build & Brew a purpose. The next risk is letting each promotion platform carry a different date, format, or registration path.

A shared event brief protects single-source registration. In this step, you will complete that brief before reaching Luma's event form.

You will confirm approved Slack and Discord channels. You will also choose a no-cost Meetup route.

In this step, get ready to:

Complete an event brief for your selected event format.
Reach the Luma event creation form with a new account.
Confirm approved campus promotion routes across Slack, Discord, and Meetup.

Complete your event brief

The event brief becomes the reference for every listing you create later. Most of its details already come from your launch commitment and confirmed logistics.

Transfer your confirmed project topic into the brief: your project topic.
Transfer your visible outcome into the brief: your visible outcome.
Record your planned date: your event date.
Record your start and end time: your start and end time.
Record the time zone for that schedule: your time zone.
Record the confirmed venue or online details: your venue or online details.

Match Your Format to Your Logistics

Your launch commitment already names the event format. In-Person needs confirmed campus venue details. Online needs meeting details.

Hybrid needs both sets of joining details. A mismatch means the logistics need attention before you create the event.

Transfer your selected event format into the brief: In-Person, Online, or Hybrid.
Record what attendees need to bring: what attendees should bring.
Set a capacity supported by your venue or session plan: your attendee capacity.
Record the participating club name: your club name.
Record the Campus Ambassador name: your ambassador name.

Good work. Your event decisions now have one source that you can check before publishing anything.

Create your Luma account

The Luma create page prompts you to set up or access an account before the event form appears. Reaching that form confirms your account is ready for the next step.

Open the Luma event creation page in your browser.
Follow the account prompt to create your Luma account.
Complete the sign-in flow.

Your Luma launchpad is ready. You should see the event creation form instead of another account prompt.

Event Form Not Loading?

If the account prompt reappears, complete any pending account verification. Return to the create page in the same browser.

If the page remains unavailable, help me troubleshoot why the Luma event creation form is not loading.

Confirm your campus promotion routes

Your campus channels need a clear posting path before the event exists. Confirming their rules now prevents a finished announcement from landing in the wrong place.

Use your club's Slack workspace to locate the approved announcement channel.
Read that Slack channel's posting rules.
Record the Slack channel in your brief: your approved Slack channel.
Record the Slack posting rules in your brief: your Slack posting rules.
Use your club's Discord server to locate the approved announcement channel.
Read that Discord channel's posting rules.
Record the Discord channel in your brief: your approved Discord channel.
Record the Discord posting rules in your brief: your Discord posting rules.

Keep Meetup Optional

Meetup is conditional in this project. A paid upgrade prompt means you choose Skip Meetup.

Skipping Meetup keeps your launch free. Do not purchase a plan for this project.

Your event format and organizer history determine the correct Meetup route.

Choose the tab that matches your Meetup account and event logistics.

Existing Organizer Access

This route fits when you already have an approved Meetup group with Organizer access.

Go to Meetup's website in your browser.
Sign in with your existing account.
Open your existing approved Meetup group.
Confirm your account has Organizer access for that group.
Record the approved group in your brief as the Meetup route: your Meetup route.

Meetup Starter Eligible

Meetup Starter is for eligible first-time organizers. It supports 1 group with up to 2 in-person events per calendar month.

Each event supports up to 10 attendees per event. This route applies only to an In-Person Build & Brew.

Go to Meetup's website in your browser.
Sign in with your existing account.
Confirm Meetup Starter is available to your account.
Confirm your event uses the In-Person format.
Confirm your event capacity is 10 attendees or fewer.
Confirm this is your single Starter group.
Confirm you will run no more than 2 Starter events this calendar month.
Record Meetup Starter in your brief as the Meetup route: your Meetup route.

Skip Meetup

This route fits when Meetup Starter is unavailable. It also fits an Online or Hybrid event. A paid upgrade request leads to the same route.

Go to Meetup's website in your browser.
Sign in with your existing account.
Confirm the condition that makes Meetup unavailable for this event.
Leave the Meetup flow before making a payment.
Record Skip Meetup with the exact reason in your brief: your Meetup route.

Your campus promotion routes are now decided. Each route has a clear channel or a documented no-cost skip reason.

Before the final check, do you expect the Luma create page to open directly to the event form?

Return to the Luma event creation page.

You should see the event creation form. This confirms your Luma account is signed in and ready.

Compare your event brief with the final checklist below.

What Should Your Brief Contain?

Event content includes the project topic, visible outcome, what to bring, club name, and ambassador name.
Schedule details include the date, start and end time, time zone, venue or online details, capacity, and selected event format.
Promotion routes include the approved Slack channel, Slack posting rules, approved Discord channel, Discord posting rules, and Meetup route.

You should now have every event brief field completed. You should also have a documented Meetup route that requires no new payment.

Your campus launchpad is set. Next, you will turn the event brief into your first live Luma page.

Publish Your Luma Event Page

Your event brief now holds one consistent set of decisions for the session. That planning keeps the live page aligned with every promotion you create later.

In this step, you'll turn the brief into a live Luma registration page. This first version focuses on the details attendees need before registering.

In this step, get ready to:

Add the event details from your completed brief.
Shape an attendee-facing page with clear information.
Publish the event for a private visitor check.

Add the core event details

The event's core details tell attendees when the session happens. They also tell attendees how to join.

In the Luma event creation form from earlier, enter Build & Brew: [PROJECT TOPIC] as the event title.
Choose [DATE] as the event date.
Set the event time to [START-END].
Set the time zone to [TIME ZONE].

You should now see the Build & Brew title paired with the schedule from your brief.

Select In-Person, Online, or Hybrid based on the format recorded in your brief.
Add [VENUE OR ONLINE DETAILS] in the location area.
Compare the completed event details with your event brief.

The selected format should now show the matching venue or meeting information.

Shape the attendee page

People use the event description to decide whether the session fits them. A useful description answers their practical questions before they register.

What makes the description useful?

The opening tells attendees what they will build.
The audience line makes clear who should attend.
The outcome names [VISIBLE OUTCOME].
The preparation line states [WHAT TO BRING].
The agenda shows the session flow.
The access section gives approved entry or joining instructions.

Write a description that covers every item in the checklist above.
Review the description against your event brief.

Your description should now give an attendee enough information to decide whether to register.

Choose a cover image that represents the Build & Brew topic.
Choose a theme that keeps the event details easy to read.

You should now see your chosen cover image applied in the event creator. The selected theme should style the page around it.

Visibility determines how people discover your event. A Private event stays unlisted while people with the link can still register.

Choose Public for open promotion or Private for link-only registration.

The form now contains the content and presentation choices for your attendee-facing page.

Publish and inspect the first version

Publishing turns the form into the registration destination you can share. A private browser window shows how the page looks without your signed-in session.

Compare the completed form with your event brief one final time.
Select Create Event.

Your event is live immediately after this action. That is your first visible win: attendees now have one page they can open to understand the session.

Record the event URL from your browser address bar here: [LUMA EVENT URL].
Open a private browsing window in your browser.

Before you load the link, do you expect the private window to show every event detail without relying on your signed-in session?

Load [LUMA EVENT URL] in the private window.

What should I see?

The title reads Build & Brew: [PROJECT TOPIC].
The date matches [DATE].
The time range matches [START-END].
The time zone matches [TIME ZONE].
The event type matches your selected format.
The location area shows [VENUE OR ONLINE DETAILS].
The description contains every item from the checklist above.
The page uses your chosen cover image.
The page uses your chosen theme.

Switch back to the signed-in event manage page in Luma.

Before you inspect registration, do you think this first page already protects a campus room with limited seats?

Select the Registration tab.

You'll see that Set Capacity has not been configured. You'll also see that Enable Waitlist has not been configured.

This intended shortfall proves that a polished event page does not automatically protect a limited campus room.

Page details not matching?

Compare each mismatched detail with the value in your event brief.
Check that the private window loaded the complete URL you recorded.
Return to the signed-in event manage page to correct any attendee-facing detail.

Help me compare my Luma event page with my event brief.

Your Build & Brew now has a live registration home. Next, you'll make that registration flow fit a limited campus venue.

Make Registration Campus-Ready

The live Luma page now gives attendees a clear place to understand your Build & Brew session. Its registration flow now needs to fit your campus requirements.

The current registration flow still lacks the campus capacity control from your brief. Approved program ownership also needs a safe path before promotion.

In this step, get ready to:

Protect registration with campus-ready controls.
Apply only approved NextWork host attribution.
Audit every launch detail against the event brief.

Protect campus registration

The event brief already records the attendance limit for this session. A waitlist gives additional interest a controlled path after the event reaches capacity.

Switch back to the Luma event manage page from earlier.
Select the Registration tab.
Enter the attendance limit from your event brief under Set Capacity.
Turn on Enable Waitlist.
Check whether any access rule requires manual review.
Turn on Require Approval when manual review is required.
Leave Require Approval off when manual review is unnecessary.
Review the Registration tab for the configured controls.

You should see the attendance limit from your event brief. The waitlist should be enabled.

The Require Approval setting should match your venue or campus access rules.

Good progress. Your event now protects the available places while preserving a path for additional interest.

Controls not appearing?

Confirm that the event title matches the live Build & Brew event from earlier.
Refresh the manage page before checking the Registration tab again.

Help me check why my Luma registration controls are missing.

Handle approved host attribution

Host attribution tells attendees which people or organizations officially stand behind the event. An unapproved NextWork identity would imply ownership that the program has not granted.

Choose the tab that matches your current approval status.

✔️ I have an approved host

This route applies when the Campus Ambassador Program supplied an approved NextWork contact or Calendar.

Locate the Hosts area on the event manage page.
Select Add Host.
Choose the approved NextWork contact or Calendar supplied by the Campus Ambassador Program.

The supplied identity should now appear in the host setup panel.

Turn on Show on Event Page.
Select Non-Manager unless the program explicitly authorized Manager access.

The host is now configured for public display with the approved access level.

Select Invite Host to complete the host setup.

You should see the supplied identity in the Hosts area.

Create an Ambassador Launch Checklist beside your event brief in the same document tool.
Record the approved NextWork host attribution in the checklist.

ⓧ Host approval is pending

A pending host request does not block the event launch. The event can continue under the confirmed ambassador or club identity.

Leave the Hosts area unchanged.
Create an Ambassador Launch Checklist beside your event brief in the same document tool.
Record that NextWork host approval is pending in the checklist.
Confirm that the Hosts area contains no unapproved NextWork identity.

Why use Non-Manager access?

Non-Manager access shows the approved host on the event page without providing backend access. Manager access provides full control over the event.

Use Manager access only when the Campus Ambassador Program explicitly authorizes it.

Audit the launch details

A final audit catches details that drifted while the event page was taking shape. The event brief gives every promotion one verified source.

Place your event brief beside the Luma event manage page.
Compare the live event title with the event brief.
Compare the live event date with the event brief.
Compare the live event time zone with the event brief.

Use the brief as your source

The event brief is the approved source for your launch details. Every public listing in the next step can copy from one verified record.

Compare the live event format with the event brief.
Compare the live location or meeting details with the event brief.
Compare the configured capacity with the event brief.
Compare the copied Luma registration URL with the live event URL.
Correct each mismatch in Luma before continuing.
Mark the audit as complete in the Ambassador Launch Checklist.

Before you make the final check, do you expect the manage page to match your launch checklist completely?

Select the Registration tab on the Luma event manage page.
Confirm that the capacity matches the event brief.
Confirm that Enable Waitlist is on.
Confirm that Require Approval matches the access rules.
Review the Hosts area.
Compare the displayed host state with the Ambassador Launch Checklist.

You should see the attendance limit from the event brief. The waitlist should be enabled.

The Require Approval setting should match your access rules.

The Hosts area should show the approved supplied identity when one exists. Otherwise it should show no unapproved NextWork identity.

Your Ambassador Launch Checklist should record the matching approved or pending status.

That is the governance work done. The event can now be promoted with a registration flow that fits your campus rules.

Your Luma event is now ready for campus registration. Next up, you will create public discovery paths that lead everyone back to this single registration destination.

Build Public Discovery Paths

Your campus-ready Luma event now has its registration controls in place. Its host status is also ready for launch.

A correct Luma page is still hard to discover when only direct-link holders can find it. Public listings on LinkedIn plus eligible Meetup routes preserve single-source registration by pointing back to Luma.

In this step, get ready to:

Publish a LinkedIn Event that sends visitors to Luma.
Complete the confirmed no-cost Meetup route.
Test every available public listing as a visitor.

Publish the LinkedIn Event

A LinkedIn Event gives your Build & Brew a persistent public listing. Its external link leads visitors into the registration controls already configured on Luma.

Open LinkedIn in a desktop browser.
Sign in to your existing LinkedIn account.
Select Home.
Select Events.
Select Create an Event.

You should see the LinkedIn Event form. This is where you mirror the details already audited on Luma.

Review the Locked Fields

After posting, LinkedIn locks Organizer. It also locks Event type.

The Event format is locked too. A mismatch in any locked field forces you to recreate the listing.

Select the organizer shown on your Luma event page in the Organizer field.
Select the matching option in Event type.

You should now see the same organizer shown on Luma. The event type should also match.

Select the matching option in Event format.
Enter the exact Luma title in the event name field.

Your LinkedIn Event should now carry the same title as the live Luma page. Its format should describe the same attendee experience.

Set the time zone to match the audited Luma time zone.
Set the date plus start time to match the Luma schedule.

The schedule shown in the LinkedIn form should now match the schedule in your event brief.

Paste the Luma event description into the LinkedIn description field.
Select External event link.

You should now see the field for an event hosted outside LinkedIn.

Paste your audited Luma event URL into the external location field.

Why Keep Registration on Luma?

LinkedIn provides discovery. Luma owns attendee registration.

One registration destination keeps the room capacity accurate. It also keeps the waitlist reliable.

Compare every completed LinkedIn field with the live Luma page.
Select Next.
Write a short share post that introduces the Build & Brew session.
Select Post.

That is your first public discovery path live. Visitors can now reach the controlled Luma registration flow from LinkedIn.

LinkedIn Event Details Look Wrong?

Recreate the LinkedIn Event when a locked organizer field is incorrect.
Copy the audited Luma URL again when the external link opens the wrong page.

Ask for help with the exact field that does not match. Help me compare my LinkedIn Event with my Luma event.

Follow your no-cost Meetup route

Meetup remains conditional because Organizer eligibility varies by account. Your route from the event brief determines whether you publish an event, submit a group for review, or document a skip.

Keep Meetup No-Cost

Meetup is optional in this launch. A paid upgrade request means the no-cost route is unavailable.

Stop before purchasing a Meetup plan.

Which Meetup route did you document in your event brief?

Existing Approved Group

This route uses a group where your account already has Organizer access. The Meetup listing mirrors Luma without creating another registration system.

Open the homepage for your approved Meetup group.
Select Create event.
Select Create a new event.

You should see the Meetup event scheduler for the approved group.

Enter the exact Luma event title.
Set the schedule to match Luma.

The Meetup title should now match the Luma title. Its schedule should show the same date plus time.

Enter the same campus venue shown on Luma.
Paste the Luma description into the Meetup description field.

The listing should now describe the same Build & Brew session. Its venue should also match.

Add the plain Luma URL to the Meetup description as the only registration call to action.
Select Publish.

Your Meetup event is now a discovery path to Luma. Attendees still register through the same controlled page.

Eligible Meetup Starter

Meetup Starter works only for eligible first-time organizers. This project uses it only for a qualifying in-person event.

Check the Starter Limits

Meetup Starter supports one group.
It supports up to two in-person events per calendar month.
Each event supports up to ten attendees.

Confirm that your Meetup account still shows the free Meetup Starter route.
Confirm that your Build & Brew format is in-person.
Confirm that the event capacity is ten attendees or fewer.
Complete the free group submission shown in your Meetup account.

Meetup can keep a new group under review after submission. A pending review is a valid result for this project.

What state do you see after submitting the group?

✔️ My Group Is Approved

Open the approved group homepage.
Select Create event.
Select Create a new event.

You should see the Meetup event scheduler for your approved group.

Enter the exact Luma title.
Set the schedule to match Luma.

The Meetup title should now match the Luma title. Its schedule should show the same date plus time.

Enter the same campus venue shown on Luma.
Paste the Luma description into the Meetup description field.

The listing should now show the same venue. Its description should match the Luma event.

Add the plain Luma URL to the description as the only registration call to action.
Select Publish.

Your eligible Meetup event is now published. Its registration path still leads to Luma.

ⓧ My Group Is Awaiting Review

Add a note named Meetup Promotion below your event brief.
Record that the new Meetup group is awaiting review.
Stop Meetup work for this project while the review remains pending.

Your pending group submission satisfies the Meetup route for this launch. The LinkedIn Event remains your available public listing.

Skip Meetup

Skipping Meetup is the correct route when the event does not qualify for a no-cost listing. Valid reasons include an online format, a hybrid format, unavailable Starter access, missing Organizer access, or a paid upgrade request.

Add a note named Meetup Promotion below your event brief.
Record the exact reason that Meetup was skipped.
Confirm that no paid Meetup plan was purchased.

Your no-cost Meetup route is now documented. LinkedIn remains the public discovery path for this event.

Test every public path

A listing only helps when its call to action reaches the correct event. Testing as a visitor catches private-session assumptions before attendees find them.

Before you test the routes, where do you think each available call to action should land?

Open a private browser window.
Visit your published LinkedIn Event.
Select its Luma event link.

You should land on the same Luma event page audited in the previous step. The title should match your Build & Brew event.

Return to the LinkedIn Event with your browser's back button.
Visit the published Meetup event in the same private window if you created one.
Select its plain Luma URL.

You should reach the same Luma event from Meetup. The schedule plus format should match the LinkedIn route.

Compare the Luma URL reached from each listing with the audited URL in your event brief.
Confirm the documented Meetup reason when your route is pending or skipped.

Every available public call to action should now lead to one Luma registration page. Your capacity plus waitlist remain accurate because registrations are not split across platforms.

Your public discovery paths now converge on one registration destination. Next, you'll bring the same event message into your approved campus channels.

Announce It to Campus Clubs

Your LinkedIn Event now gives the Build & Brew a public discovery path. Any available Meetup listing points to the same Luma registration page.

Public listings reach a broad audience. Slack and Discord bring the event into the trusted spaces where campus clubs already coordinate.

In this step, get ready to:

Review the posting rules for your approved Slack and Discord channels.
Customize one Build & Brew announcement using your event brief.
Post both announcements and verify their Luma links.

Review each channel's posting rules

Broad mentions can interrupt an entire club community. Each channel's rules determine whether an administrator has approved one for this announcement.

Return to the approved Slack channel named in your event brief.
Read the available posting rules for that Slack channel.
Leave @channel, @here, and @everyone out of the Slack announcement unless a club administrator has approved the mention.
Switch back to the approved Discord channel named in your event brief.
Read the available posting rules for that Discord channel.
Leave @everyone out of the Discord announcement unless a club administrator has approved the mention.

Why avoid broad mentions?

The @channel mention notifies every member of a Slack channel.
The @here mention notifies active Slack members.
Broad mentions should be reserved for announcements that a club administrator has approved.

Customize the club announcement

A single announcement template keeps the schedule consistent across both club channels. Its registration line points only to Luma, so attendees always reach the controlled registration flow.

Return to the approved Slack channel from your event brief.
Select the channel's message field.
Create the announcement draft by copying this template into the message field:

Build & Brew: [[PROJECT_TOPIC="your project topic"]]

Join [[CLUB_NAME="your club name"]] for a hands-on session where we will build [[VISIBLE_OUTCOME="your visible outcome"]].

Date: [[DATE="your event date"]]
Time: [[START_END="your start and end time"]] [[TIME_ZONE="your time zone"]]
Format: [[FORMAT_DETAILS="your matching format and location details"]]
Bring: [[WHAT_TO_BRING="what attendees should bring"]]
Capacity: [[CAPACITY="your event capacity"]]
Register: [[LUMA_EVENT_URL="your Luma event URL"]]

Hosted by [[AMBASSADOR_NAME="your ambassador name"]] with [[CLUB_NAME="your club name"]].

What does this template protect?

Every event detail comes from the event brief or the live Luma page.
The Format line mirrors your selected event format. A remote event uses ONLINE. An in-person event names the campus venue plus any approved access instructions. A hybrid event includes both sets of joining details.
The Register line contains the Luma event URL as the only registration call to action.
The Hosted line names the ambassador plus the club. NextWork appears only when your ambassador launch checklist confirms approved host attribution.

Replace every variable in the draft with the matching detail from your event brief.
Adapt the sentence beginning with Join so it sounds natural for the club.
Compare the draft's title, schedule, format, location details, capacity, and Luma URL against the live Luma page.

You should see the same event details in the draft and on Luma. The draft should contain no second registration destination.

Add NextWork to the Hosted line only when the ambassador launch checklist records approved host attribution.
Confirm that any NextWork wording matches the approved attribution.

Your completed draft now includes the approved hosts without implying unconfirmed NextWork ownership.

Missing an announcement detail?

Return to the event brief if the draft still contains a variable.
Compare the Format line with the live Luma page if the location details do not match.
Remove the NextWork reference if host approval remains pending.

Ask for help to check my campus announcement against my event brief.

Post and test both announcements

A matching draft becomes useful when club members can act on it. You will post it in each approved channel before testing the registration path yourself.

Review the Slack draft once more for any unapproved broad mention.
Press Enter to send the Slack announcement.

You should see the customized Build & Brew announcement in the approved Slack channel.

Copy the completed announcement from your posted Slack message.
Switch back to the approved Discord channel from your event brief.
Select the channel's text box.
Paste the completed announcement into the text box.
Press Enter to send the Discord announcement.

You should see the matching Build & Brew announcement in the approved Discord channel.

Before you test the posts, do you expect each Luma link to show the same schedule and format as its announcement?

Open the posted Slack announcement.
Select its Luma event URL.

You should reach the correct Luma event page. Its schedule plus format should match the Slack announcement.

Return to the posted Discord announcement.
Select its Luma event URL.

You should reach the same Luma event page. Its schedule plus format should match the Discord announcement.

Does a post show the wrong event?

Compare the posted URL with the URL on your live Luma event page.
Correct the announcement before sharing it further if the pasted URL points to a different event.
Ask a club administrator for the correct approved channel if Discord or Slack prevents you from posting.

Ask for help to troubleshoot my campus announcement links.

That completes your campus promotion trail. Club members can now discover the session in their usual channels and register through one reliable Luma page.

Secret mission

Clone the Next Build & Brew

Reuse your finished Luma event as the starting point for the next Build & Brew. Update every copied detail for the new session. Prove the clone has its own URL plus a fresh guest list.

Clean Up Your Resources

Choose whether to keep your event launch active, pause public promotion, or remove every artifact. This project has no required ongoing cost.

Cost warning

The Luma Free plan supports the event path used in this project. No action in this section requires payment.

Keep Luma on its free plan. Do not purchase a Meetup upgrade for this project.

Resources you used:

Original Luma event for the current Build & Brew session.
Cloned Luma event for the next Build & Brew session.
Published LinkedIn Event that directs attendees to Luma.
Optional Meetup event or submitted Meetup group when that route was available.
Build & Brew announcement in the approved Slack channel.
Build & Brew announcement in the approved Discord channel.

Keep everything running

No action is required. Choose this if registration is still open or you want to use the cloned event for the next session.

Keep the original Luma event active through its scheduled date.
Keep the cloned Luma event as the starting point for the next Build & Brew session.
Leave the LinkedIn Event published as a public discovery path.
Leave the Meetup event published if you created one.
Leave the submitted Meetup group under review if that was your route.
Keep the Slack announcement visible in the approved channel.
Keep the Discord announcement visible in the approved channel.

Pause - I'll come back to this later

Pause public promotion while preserving your event pages for later. Private visibility makes a Luma event unlisted while keeping it available to people who already have its link.

Return to the original Luma event's Manage Event page.
Open Overview.
Change the event visibility to Private.
Repeat the same visibility steps for the cloned Luma event.
Update the LinkedIn Event to state that public registration is paused.
Update the Meetup event to state that public registration is paused if you published one.
Edit the Slack announcement to state that public registration is paused.
Edit the Discord announcement to state that public registration is paused.

Delete - I don't want to use this again

Removing these events and promotions is permanent. Your pre-existing platform accounts remain intact.

Return to the original Luma event's Manage Event page.
Open More.
Scroll to the bottom of the menu.
Select Cancel Event.
Repeat the same cancellation path for the cloned Luma event.

Each cancelled Luma page is deleted.

Remove the LinkedIn Event through the event controls in the account used to publish it.
Remove the Meetup event through the approved group's Organizer controls if you published one.
Remove the submitted Meetup group through its Organizer controls if your route is still under review.
Delete the Build & Brew message from the approved Slack channel through its message controls.
Delete the Build & Brew message from the approved Discord channel through its message controls.

Nice Work!

You did it! You launched a campus-ready Build & Brew through Luma with one dependable registration destination across every promotion.

What you learned:

Built a complete Luma event page with clear session details. Protected registration with a capacity limit. Enabled a waitlist. Used only approved host attribution.
Created public discovery through LinkedIn. Used the eligible Meetup route without purchasing a plan. Kept every call to action pointed at Luma.
Published matching campus announcements in Slack. Shared the same event details in Discord. Kept one registration link across both channels.
Secret Mission: completed the optional Secret Mission to make your Build & Brew launch process reusable for a future session.

Ready to quiz yourself?