Slack & Discord integrations
Settings → Integrations connects GreekManage to your organization’s Slack workspace or Discord server and posts activity there automatically: new events, reminders, announcements, election deadlines, and counts-only alerts for officers and national staff. You decide which channels exist, who can read each one, and which activity goes where.
How it fits together
- Connect a Slack workspace or Discord server.
- Add channels from that app and give each one an audience label — who can read it.
- Create posting rules: when this happens (a trigger), post to these channels, at this time, with this message.
- Watch the post log to see what was sent and whether it arrived.
GreekManage only ever posts something to a channel whose audience is allowed to see it. That check runs on every single post — a rule cannot override it.
Connect Slack or Discord
Open Settings → Integrations. There is one card per app.
Slack
- Click Connect Slack. Slack asks you to sign in and choose a workspace.
- Review the permissions and click Allow. GreekManage asks only to post messages, post to public channels it has not joined, and list your public and private channels.
- You return to Settings → Integrations, and the card shows your workspace as Connected.
Private channels: the GreekManage app can only post in a private channel it has been invited to. In Slack, open the channel’s settings, add the GreekManage app under Integrations, then add the channel in GreekManage.
Discord
- Click Connect Discord. Discord asks which server to add the GreekManage bot to — you need the Manage Server permission on that server.
- Keep the requested permissions (view channels, send messages, embed links, read message history) and click Authorize.
- You return to Settings → Integrations with the server listed as Connected.
The bot can post in text and announcement channels it can see. If a channel restricts who can view it, give the GreekManage bot’s role access to that channel.
Disconnecting
Click the unplug icon next to a connected workspace or server and confirm. Its channels are removed, any rule left without a channel is turned off, and nothing more is posted there. Messages already posted stay in Slack or Discord.
Channels and audience labels
Under Channels, click Add channel, pick the app and one of its channels, then choose:
Audience — your promise about who can read the channel:
| Label | Means | What can post there |
|---|---|---|
| Everyone | Any member can read it | Only activity every member can already see in GreekManage |
| Officers | Only officers can read it | Everything above, plus officer alerts |
| National staff | Only national staff can read it | Any trigger, including staff alerts |
Scope — which part of the organization the channel is for:
- Organization — receives organization-wide posts.
- Region — receives posts for that region and for chapters in it.
- Chapter — receives posts for that chapter only.
An item that belongs to one chapter (for example, a chapter-only event) is only posted to channels scoped to that chapter, never to an organization-wide Everyone channel. A National staff channel receives everything.
To pause a channel without removing it, edit it and turn Posting on off. If GreekManage loses access to a channel (the app was removed, or the channel was archived or deleted), the channel shows Error and the problem is reported (see Failure alerts).
Posting rules
Under Posting rules, click New rule. The editor has a live preview of the message, in both Slack and Discord style, on the right.
Trigger
Pick what the rule reacts to. Triggers are grouped by category, and the list only shows triggers for modules your organization has. Examples by category:
| Category | Examples |
|---|---|
| Events | New event (edits and cancellations update the original post), event reminder, event is full, weekly events roundup |
| Announcements & forums | Bulletin published (from national, a regional admin or a chapter’s officers), new forum post, pinned post, poll created or closing soon |
| Elections, surveys, photos, alumni | Election published, voting open or closing soon, results published, survey launched, new album, new career posting |
| Learning & members | Course published or assigned to a group, a chapter completed a required course, new member class crossed, birthdays (off unless you turn it on) |
| Recruitment, dues, compliance, service hours, documents | Recruitment opened or closing, dues due soon (no amounts), compliance requirement created or due soon, service-hour goal progress, document published |
| Foundation & national staff | Campaign launched, milestone reached, campaign ending; chapter at risk, ticket escalated, approvals waiting, weekly compliance summary, thresholds |
| System | Integration failure |
The old Announcement published trigger belonged to the Feed, which has been removed. Rules that used it now run on Bulletin published. If one of them shared a channel with a bulletin rule you already had, it was switched off so bulletins don’t post to that channel twice, and its name ends in “(paused: shares a channel with a bulletin rule)”. Delete it or point it at another channel.
Under the trigger you can see its minimum audience. Channels whose label is too low for the trigger are greyed out, with the reason.
Channels
Click the channel chips to choose where the rule posts. You can pick more than one.
Filters
Some triggers have filters — for example, an event trigger can be limited to one hosting chapter, one calendar, one category, or required events only. Leave a filter empty to include everything.
When
The timing choices depend on the trigger:
- Immediately — as soon as it happens.
- After a delay — a set number of minutes later.
- Before — a set time before something starts or closes, such as 24 hours before start time for an event reminder.
- Roundup — a daily or weekly summary at a set time (for example, Sundays at 6:00 PM).
- Threshold — checked daily or weekly; posts only when a number crosses the value you set.
Pick the time zone for roundups and quiet hours. Turn on Quiet hours to hold posts that would arrive overnight; they go out when quiet hours end.
Message
Leave the message empty to use the trigger’s default, or write your own. The first line becomes the message title. Click a placeholder chip to insert a value such as {title} or {when}. Only the placeholders shown for that trigger are filled in — anything else in braces is rejected when you save. Turn off Include link buttons to drop the “Open in GreekManage” button.
Messages never ping anyone: @here, @everyone, @channel and user mentions are switched off.
Send test and save
Click Create rule. Once a rule is saved, open it again and click Send test to post a test message, marked as a test, to each of its channels.
Each rule in the table shows when it last posted and any error, with a switch to turn it off without deleting it.
Starter rules
Add starter rules creates a sensible set in one step. You choose an Everyone, an Officers and a National staff channel, and GreekManage adds rules such as: new events to Everyone, a reminder 24 hours before required events, a Sunday-evening events roundup, bulletins, election closing reminders, a daily approvals-waiting count to Officers, and chapter-at-risk and integration-failure alerts to National staff. Pressing it again does not create duplicates. Starter rules are ordinary rules — edit or delete them freely.
The “Also post to” box
When a national admin, regional admin or officer creates an event or a bulletin, the create form shows an Also post to box listing the channels the item could go to:
- Channels covered by a posting rule are ticked already. Untick one to skip it for this item only.
- National admins also see other channels the item could go to, unticked, to post this one item there once.
- Channels the item’s audience does not allow never appear. For example, an Officers & educators only event never lists an Everyone channel.
If no channel could receive the item, the box does not appear and your posting rules decide as usual. Reminders and roundups always follow the rules in Settings.
The post log
Post log lists what was sent, newest first: the message title, the rule (or One-off for an Also post to post with no rule), the channel, when, and the status.
| Status | Meaning |
|---|---|
| Pending | Waiting to send — delayed, held by quiet hours, or retrying |
| Delivered | Posted |
| Edited | The original post was updated, for example after an event changed |
| Deleted | The post was removed because the item can no longer be posted there |
| Failed | Could not be posted — the error is shown, with a Retry button |
| Skipped | Not sent, for example because a rule hit the hourly limit |
Filter the log by status with the selector at the top. A rule posts at most 30 messages an hour, to protect your channels from floods.
Failure alerts
When a channel stops accepting posts, or a connection is revoked, GreekManage marks it with an error in Settings → Integrations and posts an Integration failure alert to your National staff channels (if a rule for it exists — the starter rules include one). Fix the problem in Slack or Discord — re-invite the app, or reconnect — then Retry the failed posts.
Never posted
Some information never leaves GreekManage through an integration, whatever a rule, filter or message says. The list is locked for every organization and is shown at the bottom of Settings → Integrations:
- Individual invoices, payments, balances, discounts, payment plans or credits
- Individual donations, donor names, pledges or receipts
- Membership status changes, disaffiliation or chapter suspension
- PNM and applicant details, reference letters or demographics
- Grades, quiz scores, individual course progress or certificates
- Individual RSVPs, check-ins or service-hour entries
- Votes, or who voted
- Direct messages and group chats
- Support ticket contents
- Mentor matches
- Photo tags
- Chapter notes and internal chapter tasks
Officer and national-staff alerts carry counts and a link — never names or amounts. Events with Include in calendar feeds and exports turned off are never posted.
Related
Last verified against v0.88.3 (2026-10-06).