Email & Collaboration Setup in Rwanda

Exchange Online, Teams and SharePoint set up so email and collaboration actually work together.

Email and collaboration setup configures Exchange Online, Teams, SharePoint and OneDrive to work as one way of working: email for outside communication, Teams for team conversation and meetings, and shared files edited in place instead of passed around as attachments. Any organisation already on Microsoft 365 but still working mainly through email attachments needs it. This page covers organising and adopting these tools. Moving onto Microsoft 365 in the first place, including mailbox migration, is covered by Microsoft 365 deployment.

What is email and collaboration setup, and who needs it

It’s the design of how your organisation uses Microsoft 365’s communication and file tools: a team structure that mirrors how you work, file locations with sensible permissions, shared mailboxes for common addresses, guest access rules, and short training so habits change. It suits organisations with files scattered across inboxes, laptops and USB drives, and those where Teams grew without any structure.

The problem it solves

When files travel as attachments, versions multiply, edits get lost and nobody knows which copy is final. When Teams grows without a plan, there are dozens of teams with similar names, files stored in random chats and guests nobody remembers inviting. Both waste time and leak data. A deliberate setup gives every file one home and every team a purpose, with access controlled in one place.

Where things should live

Email is for people outside your organisation and formal communication. Shared mailboxes, such as info@ or accounts@, let several people manage one address without sharing a password.

Teams is for conversation within teams and projects, meetings and quick questions, organised by department or project, with channels for distinct topics.

SharePoint holds files the team or organisation owns. Each team has a site; organisation-wide content, such as policies and templates, sits on a central site.

OneDrive holds each person’s own working files and drafts.

Designing teams and permissions

  • Start from how you work: departments, cross-department projects and committees.
  • Keep teams few and purposeful, with at least two owners each, so none are orphaned when someone leaves.
  • Control who can create teams, or use naming rules, to avoid duplicates.
  • Set permissions at team or site level, not file by file, so access is easy to review.
  • Decide sharing rules: who can share outside the organisation, and whether anyone-with-the-link sharing is allowed.
  • Plan guest access with expiry and periodic review.

This structure also makes Microsoft 365 security optimisation easier, because sharing and access follow clear rules.

What the work involves

  1. Understand how you work: teams, projects, shared addresses and external partners.
  2. Design the team structure, file locations, permissions and sharing rules.
  3. Build teams, sites, shared mailboxes and guest settings.
  4. Move files from file servers, laptops and inboxes into the right locations.
  5. Train staff and team owners in short sessions.
  6. Review after a month and adjust.

What’s included and what’s not

Included: team and site structure design, file migration into the new structure, shared mailboxes, guest access configuration, and staff training.

Not included unless bundled: moving mailboxes from another system (see Microsoft 365 deployment), device management (see Microsoft Intune) and email on a non-Microsoft platform (see business email setup under Web, Hosting & Digital).

Typical timelines and what drives cost

Setup for a single organisation typically takes three to five days, plus training. Cost is driven by the number of teams and sites, the volume of files to move and how much they need reorganising, the number of external partners, and how many training sessions are needed.

Equipment typically used

Microsoft Teams, SharePoint, OneDrive and Exchange Online from your existing licences, the SharePoint Migration Tool or similar for moving files, and the Teams and SharePoint admin centres for sharing and guest settings. Desktop and mobile Teams and OneDrive apps on staff devices.

Common mistakes we see

Files still sent as attachments after Teams is rolled out. One giant team for everyone. Teams with a single owner who then leaves. Departmental files kept in one person’s OneDrive. Anyone-with-the-link sharing on by default. Guests from old projects still holding access. And a shared mailbox password passed around instead of proper shared mailbox access.

Hand holding a glowing network sphere of technology icons above the earth at night

Frequently asked questions

Isn't Teams just for chat and video calls?

No. Each team in Teams is backed by a SharePoint site where its files live, so a team becomes a shared workspace: conversations, documents edited together, meeting notes and project tasks in one place. Used only for chat and calls, it's a small part of what most Microsoft 365 licences already include.

How is SharePoint different from just saving files to email attachments?

An attachment creates a new copy every time it's sent, so nobody knows which is current. A file in SharePoint has one copy that people open and edit together, with version history to roll back mistakes and permissions that decide who can see it. Sharing a link instead of an attachment also lets you withdraw access later.

Can external partners or clients be added to a Teams channel?

Yes, as guests or through shared channels, with limits you set. Guests can join a team or channel and see only what's shared there, not the rest of your organisation. We set guest access per team, require guests to verify their identity, and review guest accounts periodically so partners from finished projects don't keep access indefinitely.

Do we need training for staff to actually use these tools well?

A little, and it pays back quickly. Short sessions on sharing links instead of attachments, finding files in Teams, co-editing documents and running a good Teams meeting change habits more than any technical setting. Team owners get a little more on managing members and channels. We provide short written guides for later reference.

Should we use OneDrive or SharePoint for our files?

Both, for different things. OneDrive is each person's own working space, for drafts and files that are theirs alone. SharePoint, through Teams or team sites, is for anything a team shares or that the organisation must keep when someone leaves. A common mistake is keeping shared departmental files in one person's OneDrive, which causes problems when they leave.

Getting full value from Microsoft 365?

Tell us your licence tier and what your staff struggle with. We’ll review the setup and quote what changes.

Welcome to GENIUS Advanced Technologies, your partner for IT infrastructure, security and software in Rwanda.

Bienvenue chez GENIUS Advanced Technologies, votre partenaire pour l’infrastructure, la sécurité et les logiciels au Rwanda.

Key services

  • IT Infrastructure & Networking
  • Cybersecurity
  • CCTV & Surveillance Security
  • Microsoft & Cloud
  • Software Development
  • IT Support & Managed Services

Choose your language

Choisissez votre langue

You can switch language at any time from the site menu. Vous pouvez changer de langue à tout moment depuis le menu.