Install Community Events (Bevy) in Slack, connect your Bevy community, and choose which chapters show in the App Home and in channels. This page covers admin install and chapter-to-channel setup — not member browse or RSVP.

Community Events (Bevy) is a Slack app for one Bevy community (one Bevy site, for example community.example.com). A community has chapters. Each chapter is public, private, or hidden on Bevy.

After you connect a community and map chapters, the app can show those chapters’ events in the App Home and in Slack channels, and it can post change alerts in channels you choose. Members browse, RSVP, and link their own Bevy accounts from Slack after setup — see Browse events and RSVP from Slack.

Who can install and manage

Rights come from Slack, not from Bevy roles.

• Only the connection owner can edit what a community shows. An admin cannot edit a community someone else connected. An admin can only remove it from a destination. Edits use the owner’s Bevy access; removals do not.
• The first community must come from an admin or a manager. After that, an admin can turn on Let members connect additional communities in Manage so any member can connect another community. This setting is off by default.
• Link my Bevy account is not the same as Connect. A linked account is personal. It never puts content in a channel or the App Home, even when the person who linked it organizes chapters on Bevy.

Install the app

1. In Slack, open Apps (or your workspace’s app directory) and find Community Events (Bevy).
2. Add the app to your Slack workspace. A Slack workspace admin or owner (or, on Enterprise Grid, an org admin or owner) must approve the install when your workspace requires it.
3. Open the app from the Slack sidebar so you see the App Home.

If your workspace blocks apps that are not listed in the Slack App Directory, a Workspace Owner may need to allow those apps before you can finish install.

Connect a community

1. Open the App Home. Select Connect your community.
2. In Your community URL, enter the Bevy site (for example community.yourbrand.com).
3. Optional: in Name for this community, enter a short name. The app shows this name on events when the workspace follows more than one community.
4. Select Continue to Bevy. Sign in on Bevy and approve the app.
5. Return to Slack. The App Home shows a setup card.

A connection alone shows nothing. On the setup card, choose one of these:

• Show all public chapters. Puts every public chapter on the App Home. New public chapters appear when they are created.
• Choose what to show… Opens the editor.

Edit what a destination shows

The editor sets what one destination shows. A destination is the App Home or one channel. Each destination has its own settings, so #uk-events can show UK chapters and #us-events can show US chapters of the same community.

Which events has two options:

• All public chapters (new ones too). Every public chapter shows. Use Leave out to exclude some. Chapters created later also appear.
• Only the chapters I pick. Only selected chapters show. New chapters do not appear.

Private and hidden chapters have a separate picker, Private and hidden chapters. They are never part of All public chapters.

If the community has more than 100 chapters, the public picker searches by name and shows the first 100 matches. If you cannot find a chapter, use ＋ Add a chapter by URL… in Manage.

Add a chapter by URL

1. In Manage, select ＋ Add a chapter by URL… under the community.
2. Paste the chapter’s main page URL. It must be on the same Bevy site as the connection.
3. Select Next. The editor opens with the chapter selected and no destination.
4. Pick a Channel. Optional: select Also show these in the App Home.

This screen does not put a chapter on the App Home only. Put it in a channel first, then use the App Home row on the Chapters → channels page. The App Home is the widest audience: every workspace member sees it.

Pasting a chapter URL in a normal Slack message does nothing. The app does not unfurl Bevy links.

Channel pickers show only public and private channels in this workspace — never DMs. A private channel appears only after you invite the app: type /invite @Community Events (Bevy) in the channel. If the app cannot post in a channel you saved, it tells you after save.

Show chapters in channels

In Manage, select Chapters → channels… under a community you connected. The page lists every chapter (30 rows per page) and the channels that show it. Changes save at once.

• One chapter: pick channels in that chapter’s Choose channels picker.
• Every public chapter: pick a channel at the top, then select Add to every public chapter. This skips private and hidden chapters.
• Remove a channel everywhere: pick a channel, then select Remove from every chapter (confirm). This also removes private and hidden chapters.
• App Home: use the menu on the App Home (everyone) row to edit or remove it.

If a channel shows All public chapters, removing that channel from one chapter leaves that chapter out. New chapters still appear. Adding a channel to a private or hidden chapter asks for confirmation before save.

Manage

Select Manage at the bottom of the App Home. Manage shows:

• Workspace settings (admins only): Let members connect additional communities.
• Who can manage this app (admins only, not managers): the list of managers (up to 50).
• Connected communities: every community the workspace shows, and where it shows.

For a community you connected, Manage shows one Shown in line plus Chapters → channels… and ＋ Add a chapter by URL…. For a community someone else connected, Manage shows one row per destination with the owner’s name. If you can remove it, the row menu includes Remove.

Manage shows at most 12 communities and at most 10 destinations per community. If there are more, it says so.

Private and hidden chapters

These rules protect people who cannot see those chapters on Bevy.

• Private: only chapter members can see it on Bevy.
• Hidden: Bevy does not list it. People reach it only through a direct link.
• Unconfirmed: the app could not check whether the chapter is public. The app treats an unconfirmed chapter as private.

The app reads a private chapter’s events with the connection owner’s Bevy access. When an owner puts a private chapter in a channel, everyone in that channel sees its events — including people who cannot see them on Bevy. Because of that:

• All public chapters never includes a private or hidden chapter, even when the owner is a member. Pick each private or hidden chapter in the Private and hidden chapters picker.
• When you add a private or hidden chapter, the app asks you to confirm (Are you sure?). For the App Home, it warns that everyone in this workspace will see them.
• Confirm appears only when you add a chapter, not when you re-save one you already confirmed.
• A hidden chapter shows events only if the owner organizes it.

If a public chapter later becomes private or hidden, its events can stop showing until you save again and confirm. The editor may warn: No longer public on Bevy, so this destination may not show them.

Manage, the editor, and Chapters → channels mark chapters as private, hidden, private and hidden, or unconfirmed. The line seen through your Bevy access means events come from your account.

Configure alerts

Alerts need the community’s webhook, which the app installs when an admin connects the community. If a community has no webhook, alert controls do not appear.

When a channel shows a chapter, the app can post:

• New event: a recently published chapter event (at most 5 per channel per hour).
• This event changed: a change of date, place, or status.

The first post about an event starts a thread for that event in that channel. Later changes go into that thread and also appear in the channel.

• Public events only, by default. Everyone in the channel sees the post, so the app posts only what an anonymous visitor can see on Bevy.
• Canceled public events do not get a channel post. Bevy hides canceled events from anonymous visitors. Members who follow the event still get a personal DM alert.
• Mutes. An admin can stop alerts for some chapters on Chapters → channels under Change alerts. A mute covers every channel in the workspace.

Channel alerts for private chapters (opt-in)

The owner can turn on alerts for a private or hidden chapter, one channel at a time. On Chapters → channels, each private or hidden row has a Change alerts in #channel checkbox per channel (off by default).

When on, the app posts only published and canceled events for that chapter, and only when the owner’s account can read the event. Removing the channel from the chapter removes the opt-in.

Attendee alerts

An alert card in a channel can include Attendee alerts. When on, the app posts in the event’s thread when new people RSVP (for example, 2 new attendees · 31 going).

• The app posts counts only, never names.
• Only public events can have attendee alerts.
• Only the connection owner or an admin can turn them on or off.

When something goes wrong