For nonprofits and universities with many voices
Admissions, research, alumni, fundraising, every programme and chapter — they all have something to post, and the comms team is answerable for all of it. Let each group draft in its own workspace, and let comms approve before anything goes out.
The old way, crossed out.
- Departments running their own accounts with nobody reviewing what goes outComms reviews every department’s posts
- Posts sent to comms as attachments, with no idea which version is finalThe final version, reviewed on the post
- Accounts set up by staff and students who have since leftAccounts that stay when people leave
A workspace for each department or programme
Give each department, faculty, programme or chapter its own workspace, with its own calendar, accounts and history. The people who know the news write it; the central comms team sees everything that is waiting for a decision.
Membership is per workspace, so a department’s writers see only their own workspace, while the comms team can be approvers across all of them.
Comms approves, departments write
- Department staff write and schedule posts as editors — they can’t approve their own
- The comms team reviews each post as it will appear, and approves, requests changes or rejects it
- Changes arrive as notes on the post, so a busy department knows exactly what to fix
- Approvers are free, so any number of comms reviewers and senior sign-offs cost nothing
Set an approval window per workspace, so a post nobody reviewed in time expires rather than going out anyway.
One standard across many accounts
A central team can’t write every post, but it can hold every post to the same standard. Every post is checked against each network’s limits as it is written, and comms sees each one in its final form before it goes out — so the tone, the facts and the photos are right on the smallest programme account as on the main one.
Keep the style guide’s key rules in the team notes, where department editors see them while writing, rather than in a PDF nobody opens.
Accounts that outlast the people who made them
Department accounts are often set up by someone who has since moved on, and the password went with them. Connecting each account to its workspace through the network’s own sign-in keeps it with the department. When a student ambassador or staff member leaves, the account stays where it is.
Planning for the year’s big moments
Open days, results days, graduation, appeal deadlines, awareness weeks: the calendar is built around months, so each department plans its month around the dates that matter to it, and comms sees them coming in the review queue instead of on the day. The monthly calendar guide covers planning around fixed dates.
Department editors take a team seat; approvers never do. Pro covers five workspaces and five seats; larger institutions and networks of chapters usually need the Agency plan, which is unlimited.
The features that matter most here.
Client approvals
Approve, request changes or reject — on the post, in one click.
Content calendar
Day view for writing, month grid for reviewing — one screen, one switch.
Collaboration
A conversation thread on every post, shared with the client.
Publishing
Each client connects their own accounts — no shared logins.
Nonprofits & universities, answered
Can the central comms team approve posts from every department?
Yes. Add the comms team as approvers in each department’s workspace. Approvers are free, and every decision is recorded.
Can departments only see their own posts?
Yes. Each department works in its own workspace, and membership is per workspace.
Which plan suits a university or a large nonprofit?
Pro covers five workspaces and five team seats. Institutions with more departments or more writers usually need Agency, which is unlimited. Approvers are free on every plan.
Get next month approved before it starts.
Start free with one client. No card needed — upgrade when the client list grows.