How to choose the right message setup for your organisation
Different non-profits need different levels of control, storage and admin support. A small outreach team in Observatory may only need a few shared mailboxes and a simple calendar, while a provincial office in Johannesburg or Durban may need more structured access, team folders and clearer handover steps for staff changes.
Start by looking at how your people actually work. If trustees, field staff and finance all share documents, then your setup should cover mail, calendars and file access in one place. If your team is mobile, check that the service works properly on phones and tablets, especially when load-shedding interrupts office work.
- Count active users, not just total staff.
- List who needs shared calendars and who only needs message.
- Check if you need mobile access, admin controls or document sharing.
- Think about growth over the next 12 months, not only today.
What to expect during a mail migration
Moving from an old mailbox system can be straightforward when it is planned properly. The main work is usually linking the domain, creating new mailboxes, copying old messages and making sure contacts and calendars come across correctly. For organisations with donors, volunteers or project teams, it helps to do this in stages rather than all at once.
A good migration plan should include a timeline, a go live window and a clear list of who will test each account. There should also be a handover step so your internal admin knows how to reset passwords, add users and manage groups after the move. That way your team is not left waiting for outside help every time a small change is needed.
- Confirm the number of mailboxes and aliases before migration.
- Back up contacts and shared calendar entries first.
- Test mobile devices after the transfer, not only benchtop access.
- Allow time for DNS changes to settle, since mail delivery can take a bit of time to update.
Using shared calendars to keep programmes on track
Shared calendars help teams avoid double bookings and missed meetings. They are useful for training sessions, board meetings, site visits and grant deadlines, especially when staff work across Cape Town, Pretoria, Bloemfontein and other branches. A well-managed calendar setup gives each person the visibility they need without exposing private information to everyone.
For non-profits, the practical value is simple: less confusion and fewer last-minute calls. You can create separate calendars for management, fundraising, outreach or room bookings, then decide who can view or edit each one. If your office is in a busy shared space or your team travels often, this can save a lot of time.
- Set clear rules for who can edit, not just who can view.
- Use separate calendars for events, leave and board meetings.
- Keep naming simple so new staff can understand it quickly.
Document sharing for reports, policies and day-to-day work
Document sharing is most useful when files are easy to find and properly organised. Non-profits often keep policy documents, funding reports, attendance registers and programme notes in many different places, which leads to version mix-ups. A shared document area gives your team one place to store files and work on them together.
Set folder names that match your real work, not technical terms. For example, use programme names, years and document types so staff can see what belongs where. This is especially helpful when teams change or when a support person in Bellville or Stellenbosch needs to step in and find a file quickly.
- Keep one master folder structure for all teams.
- Limit editing rights for sensitive documents.
- Use clear file names with dates and versions.
- Review old folders every few months so clutter does not build up.
Security and access controls for non-profit mail systems
Message security matters because non-profits often handle personal details, donor records and internal plans. A proper setup should include strong passwords, two-step protection where needed and a review of who has access to each mailbox. If a staff member leaves, access should be changed quickly to protect the organisation.
Security does not need to be complicated. It needs to be consistent. A short review can show whether old accounts are still active, whether mobile devices are protected and whether shared mailboxes are being used correctly. This is especially important for organisations with part-time staff or volunteers who may not be on site every day.
- Remove access as soon as roles change.
- Check which devices are signed in to organisation accounts.
- Use separate admin access for day-to-day support work.
- Review security after staff changes and before new projects start.
When to ask for help with setup, training or support
Some teams only need a basic mail setup. Others need help with migration, training, mobile configuration and admin handover all at once. If your staff are new to hosted message, or if you are moving from a mix of personal accounts and old inboxes, guided support can save time and avoid mistakes.
Training is often most useful right after go live, when people are already working in the new system. That is the best time to cover calendar sharing, contact imports, mailbox rules and how to get help if something stops working. For non-profits, this keeps operations steady without adding extra pressure on a small admin team.
If you are choosing a service for offices in Cape Town, Johannesburg, Durban, Pretoria or Bloemfontein, these guides can help you compare what you need before you commit. They are written to keep the process practical, so your organisation can make a clear choice and move forward with less stress.