News

News is a small blog attached to a page. You write a post in Markdown, give it a cover image, and set it to Published. From that moment it sits in the app's Home feed. Nothing about it touches your page on the website, and nobody is told about it unless you send a push afterwards.

Which pages have News

Four page types carry the screen, and it behaves identically on all four. In each one the sidebar entry sits under the Marketing category:

Crew pages have no News screen. Posts belong to the page you wrote them on: a post on an event and a post on the promoter running it are two separate items, and neither appears under the other.

News is not sold as a plan feature. Unlike Notifications, which is replaced by an upgrade panel on the free tier, News works on every plan for anyone holding the permission described at the bottom of this page.

Open the screen

1. Open Manage pages in the admin sidebar and click the page or event you want.
2. Click News in the left sidebar, under Marketing.

The heading reads News, with Broadcast announcements to your app's Home feed. underneath. Below that sits the list of posts, a status filter on the left and a New post button on the right. A page with nothing on it yet reads No news yet. Create your first announcement.

Publish a post

1. Click New post. The list is replaced by the editor. This is the same screen rather than a dialog, so Back to list at the top left is how you leave it.
2. Click the wide empty banner at the top of the editor, marked Add a cover, and pick an image. It uploads as soon as you choose it and the banner fills. Hovering a filled banner offers Replace; the ✕ in its top-right corner clears it.
3. Type the headline over the placeholder News title. It is the only required field, and saving without one answers A title is required.
4. Write the post in the box below, placeholder Write your announcement in Markdown…. The toolbar covers bold, italic, strikethrough, inline code, three heading levels, quotes, bulleted and numbered lists, code blocks, links, a horizontal rule and an inline image. The two tabs on the right of the toolbar switch between the writing box and the rendered result; they are labelled Edit and Preview in English whatever language your admin is set to.
5. In the Publication card on the right, set Status. The hint under it reads Published posts appear in the app immediately.
6. Click Save. A Saved. confirmation appears and you land back on the list.

Cover images are capped at 10 MB. Whatever you upload is re-cut to a 16:9 frame and converted to WebP, so a tall portrait shot loses its top and bottom. Pick something wide.

What a published post reaches, and what it does not

Both lines on the screen say the same thing in different words: a published post goes to the Home feed of the app. That is the whole of its distribution.

• Nobody is notified. Publishing writes the post and stops. There is no alert, no badge and no email. Readers find it when they next open the feed.
• Pushing is a separate, deliberate step. Reopen a published post and the Publication card gains a Send a push button, which carries you to the Notifications screen with the post already selected and the form filled in from it. That form takes the title trimmed to 50 characters, the body flattened to plain text with the Markdown stripped out, and the cover image as the notification picture. Only posts published in the last three days can be picked up this way, and sending a push needs both its own permission and a paid plan.
• The button only exists on a saved post. Creating a post straight into Published and saving it returns you to the list, where no such button exists. Open the post again to get it.
• Nothing appears on the website. Your public page on sway.events has no news section. This is an in-app surface only.

Draft, Published and Archived

Every post carries exactly one of three statuses, shown as a coloured pill in the list and set from the Status dropdown in the editor.

The publication date is stamped once. The Published column is filled the first time a post reaches Published and is never rewritten. Sending a post back to Draft and publishing it again a week later keeps the original date; what moves is the Modified column. A post that has never been published shows a dash.

Both dates are printed in your own timezone, so a colleague abroad reading the same list sees the same instant written differently.

Read the list

The table holds Title, Status, Published and Modified, plus a pencil button on the right of each row. Rows are ordered by most recently modified first. There is no sort control, no search and no pagination.

The dropdown above the table filters by status, with All statuses, Draft, Published and Archived. Clicking anywhere on a row opens that post, and the pencil does the same thing.

Edit a post

1. Click the row you want, or its pencil button.
2. Change whatever you need. Every field of the creation form is here, filled in with what you saved.
3. Click Save.

Editing a published post updates it in the feed. There is no second confirmation, no draft-alongside-live copy and no version history, so an edit to a live post is live as soon as it saves.

Changing the status is how you take something down. Set a live post to Draft or Archived and save; it leaves the feed and you keep the text.

Remove a post

Deleting is a last resort. Archived already retires a post while keeping it readable to you, and it is reversible with one dropdown.

1. Open the post.
2. In the Danger zone card at the bottom right, click Delete.
3. The confirmation reads Delete this post? and This action cannot be undone. Click Delete again to go through with it.

A Deleted. confirmation appears and the list reloads without it. The Danger zone card exists only on a saved post, so there is nothing to delete while you are still creating one.

Who can use this screen

The screen is gated on a single permission, news_manage, checked both by the sidebar and again by the page itself. Page owners have it. A member who does not sees News greyed out in the sidebar, with nothing on hover to explain why, and reaching the address directly returns You don't have permission to manage news for this page.

The permissions grid has no tick box for it. news_manage belongs to none of the feature groups the Permission Management screen draws its checkboxes from, so it is not something you can hand to one teammate, or take back from them, on its own. It travels only with the two broadest role templates in that same dialog, Admin Template and Manager Template, which carry it silently along with everything else they grant. Editor Template and Viewer Template do not include it, and no checkbox can add it afterwards.

In practice that leaves two ways to run News:

• Keep it with the owner. Whoever owns the page writes the posts.
• Promote the writer. Give the person the Manager Template or Admin Template and accept that they receive a great deal more than news access along with it.

Read the rest of the model, and the difference between those templates, in Manage permissions.