Start With The Role, Not The Person
Before you create a mailbox, decide what the role actually needs to do. A volunteer who only confirms attendance for a one day event does not need the same access as a temporary fundraising coordinator who will manage donor replies for three months. If you assign mailboxes too quickly, you end up with old accounts, missed messages and confusion when people leave.
A practical rule is to link the mailbox to the function, not the individual. Use role based addresses for ongoing tasks such as volunteers, events, outreach or shelter admin. For short term help, a shared mailbox or controlled forwarding setup may be enough. That keeps your records cleaner and reduces the number of accounts you need to manage later on.
- Give a full mailbox only when the person must send and receive messages in their own name for more than a few weeks.
- Use a shared mailbox for team based tasks that need visibility by more than one person.
- Keep personal message accounts separate from organisation records and volunteer admin.
When A Volunteer Needs An Org Message Address
There are times when a proper organisation email address is the sensible choice. If a volunteer is dealing with beneficiaries, suppliers, schools, municipal offices or media queries, the communication should come from the organisation and not from a private Gmail or Yahoo account. That looks more professional and it also makes it easier to keep a record of what was agreed.
For non-profits in South Africa, this matters even more when the work involves grants, venue bookings or transport arrangements. In Cape Town, for example, a volunteer coordinating a food drive may need to share dates with community halls, the local ward office and donors all in the same week. A proper mailbox makes those conversations easier to trace and hand over if the volunteer suddenly becomes unavailable.
- Use an organisation mailbox when the volunteer represents the non-profit externally.
- Use it when the role handles private or sensitive information.
- Use it when the role will continue after a specific event or campaign.
How To Keep Access Tight Without Slowing The Team
Giving volunteers access does not mean giving them free rein. A mailbox should have clear limits, especially if the volunteer is only around for a season or during a campaign. Set up access in line with the work they need to do, then remove it as soon as the assignment ends. This is basic administration, but it saves a lot of trouble later.
Good access control also helps when load-shedding, travel or staff shortages interrupt the normal routine. If one person knows everything and nobody else can log in, the inbox can stall for hours. A better setup is to let one manager or coordinator retain oversight while the volunteer handles day to day replies. That way the organisation stays in control even when the timetable changes.
- Use strong passwords and change them when the role changes or ends.
- Limit which folders, calendars or document spaces a volunteer can edit.
- Record who approved the mailbox and what the person is allowed to do.
Shared Mailboxes, Personal Mailboxes Or Forwarding
Not every volunteer role needs the same setup. Shared mailboxes are useful where several people answer the same inbox, such as event enquiries or volunteer sign ups. Personal mailboxes suit one person who has individual responsibility, such as a temporary project coordinator. Forwarding can work for very light duties, but it is easy for messages to get lost if the person forgets to check their private inbox.
Think about how often the inbox will be used and who needs to see the replies. If the work is sensitive or time bound, a shared mailbox with clear rules is usually safer than forwarding to a personal address. If the volunteer is producing reports, sending invitations and keeping a full paper trail, a named mailbox may be the better choice. The right answer depends on the load of the role, not on what is easiest on day one.
- Shared mailbox: best for teams answering the same enquiries.
- Personal mailbox: best for one person with ongoing responsibility.
- Forwarding: best for low volume communication, but use carefully.
Make Handover Part Of The Setup
Many non-profits only think about access when a person joins. The bigger issue is what happens when they leave. A proper handover should be planned from the start, especially for volunteers who work on campaigns, holiday programmes or temporary admin cover. Without a handover, messages stay in the old inbox and other people have to chase loose ends.
A simple handover process should cover passwords, active contacts, calendar events, shared documents and any open tasks. It should also say who owns the mailbox after the person exits. In smaller organisations, this step is often skipped because everyone is busy, but it is worth the extra 20 minutes. One clean handover can save days of backtracking later.
- Confirm the exit date and the last day of mailbox access.
- Move any important messages into the organisation's shared records.
- Update calendar events and document permissions before the person leaves.
A Local Example From A Busy Volunteer Team
Consider a community food programme in Observatory that runs deliveries across Cape Town, with extra help from volunteers in Bellville and Stellenbosch. One volunteer handles donor thank you notes, another manages collection times, and a temporary coordinator deals with roster changes for six weeks. If all three use personal email addresses, messages quickly get mixed up and nobody knows which reply is current.
A better setup is to give the coordinator a named mailbox, give the delivery team a shared inbox for route changes, and keep donor communication under one controlled account. Shared calendars can show drop off times, school visits and stock counts, while document folders hold driver notes and consent forms. This keeps the admin neat even when people are working from home, travelling between towns or dealing with patchy connectivity. It also helps when a volunteer steps away with little notice and the next person needs to carry on without confusion.
For organisations working across Johannesburg, Durban, Pretoria or Bloemfontein, the same approach applies. Local conditions change, but the principle stays the same: give access only where it is needed and keep ownership with the non-profit.
Set Expectations Before The First Login
Once the mailbox is created, the volunteer should know how it will be used. Explain what they may send, what they may not change, who checks the inbox after hours and when they should escalate issues. This avoids the common problem where someone replies too quickly or stores sensitive information in the wrong place.
A short induction is often enough, but it should be specific. Volunteers do not need a long technical session. They need clear instructions on who to copy, how to name files, what to do during outages and where to ask for help if the mailbox stops syncing on a mobile phone. If you get this right from the start, the system remains simple and the organisation keeps control.
- Tell volunteers which messages are urgent and which can wait.
- Show them how to use shared calendars and document folders properly.
- Make sure they know the exit process before they start work.
