Communication

The Communication module keeps your teams and crew informed. It has three tools, each suited to a different kind of message:

Communication is always enabled on every event (like Accreditation).

Not here: automated emails (approvals, invites, tickets) live under System Emails, and portal page copy lives under Pages — both in the Settings area. See the Settings guide.

Bulk Emails

Communication → Bulk Emails sends one-off emails to accreditation audiences.

Creating and sending

1. Press New Email, enter the Email Subject, and pick the Recipients:
   • All Crewmembers
   • All Team Contacts (HODs)
   • All People Who Have Collected Pass
   • Selected Groups — tick the groups you want.
2. The draft opens for editing: write your Message (personalise with First Name, Last Name, and Team Name merge tags) and optionally attach one file (PDF, Word, or image) included with every send.
3. Use Send test email to check it in your own inbox, then Save and Send (you’ll be asked to confirm).

Emails move through Draft → Queued → Sent. Sent emails can’t be edited, but Duplicate as new draft gives you a fresh copy to reuse — handy for recurring updates.

News Feed

Communication → News Feed publishes updates to the team portal’s news timeline.

Creating a post

New Post opens the post form:

• Title — shown at the top of the post in the portal feed.
• Content — rich text for the update itself.
• Pin to top — keep important posts above the rest.
• Audience — All groups, or switch on specific groups only.

Save as a Draft to keep working, or Publish to make it live. Published posts can be updated, Unpublished (back to draft), or deleted.

Where teams see it

Teams see a News Feed section in their portal as soon as at least one published post is visible to their group, with pinned updates shown first. News also appears on the crew induction hub, so people completing inductions see your latest updates too.

Knowledge Base

Communication → Knowledge Base builds a wiki of reference pages for the team portal — think site handbook, local information, or frequently asked questions.

Building pages

• New root page creates a top-level page; Add child page nests pages underneath, so you can organise content as a tree (e.g. Site Info → Parking, Site Info → Deliveries).
• Each page has a Title, Parent page, Audience (All groups or specific groups), and rich-text Content.
• Reorder pages with the up/down controls.
• Save Draft keeps a page hidden; Publish page makes it live.

Deleting a page also deletes all of its child pages — you’ll be warned first.

Where teams read it

Published pages appear as a navigable tree in the team portal sidebar (and on the induction hub), filtered by each team’s group. Teams outside a page’s audience never see it.

Choosing the right tool

• Time-sensitive and must reach inboxes? Bulk Email.
• An update people should see next time they open the portal? News Feed (pin it if it’s important).
• Information people will need again later? Knowledge Base.

A common pattern: publish the detail as a knowledge base page, post a short news item pointing to it, and send a bulk email only when it’s urgent.