Working channels
Create Teams channels for topics that a team needs to follow over time, with publishing rules and owners able to update or close each space as the project or department changes.
Microsoft Teams
Microsoft Teams, conversations your team can follow.
Microsoft Teams for your SME: organise teams, meetings and files, prepare external access and choose licences that fit the way your business works together.
SMEsat the heart of what we do
A dedicated contactwho knows your business
A local teamin French-speaking Switzerland
Suitable tools. Local support. A team close to you.
Geneva
Lausanne
Fribourg
Neuchâtel
Valais
Give each conversation a clear home.
Teams can bring together business conversations, meetings and shared workspaces. Its usefulness depends on understandable rules: where to ask a question, record a decision and keep the authoritative document.
For an SME working across several sites in French-speaking Switzerland, we recommend starting with a small number of useful teams. A workspace for a project or department can work well when its owners and intended lifespan are clear. Creating a new team for every conversation soon makes information harder to find and leaves staff unsure where a decision was recorded.
Online meetings
Prepare Teams meetings with organisers and external participants, test audio equipment and screen sharing, then decide how recording or transcription should be used according to available licences and your internal rules.
Focused conversations
Define when a Teams chat suits a specific question and when to publish in a channel, so that decisions and useful information remain easy to find for the people who need them later.
Channel files
Clarify how Teams channel files relate to SharePoint, then identify their owners and permissions so a project can be handed over with a clear understanding of where its reference documents belong.
Guest access
Prepare invitations to Teams spaces by confirming the business need, assigning access suited to the project and reviewing external members when their assignment ends or the collaboration no longer requires their participation.
Teams Phone calling
Assess Teams Phone against telephone numbers, equipment and reception requirements, distinguishing calls between users from public telephone services and checking the licences and operator connection needed for the proposed calling setup.
How we support you.
From initial scoping to ongoing support, the agreed work and each party’s responsibilities are defined with you before implementation.
Migration and transition
Prepare data, accounts and cutover stages, with testing and a rollback plan.
Configuration and deployment
Configure tools and integrate them into your environment within the agreed scope.
Security and access
Define permissions, available protections and useful checks.
Governance and organisation
Clarify workspaces, responsibilities, sharing rules and team practices.
Backup and continuity
Check data protection needs and prepare recovery procedures.
User support
Support adoption and agree ongoing assistance suited to your employees.
Solutions suited to your sector.
We start with your teams’ needs, business applications and organisational constraints.
Professional services
Share client files between colleagues, with appropriate access and documents that are easy to find.
Healthcare & medical
Protect patient records and maintain the tools needed for consultations.
Property & construction
Find plans and files on site while keeping control of access for everyone involved.
Local authorities & associations
Organise access for employees, elected representatives and volunteers, and make handovers easier when teams change.
A well-managed environment.
Tools alone are not enough. Ongoing management, access and documentation need to remain clear over time.
Access and security
Roles, permissions and protections suited to the agreed scope.
Continuity
Identified dependencies, with backup and recovery arrangements to prepare.
User management
Documented joiners, leavers and changes in responsibility.
Monitoring and records
Accessible configuration, licence and upcoming renewal records.
Understand your options before deciding.
Uses, limitations and frequently asked questions: the points to clarify when preparing your project.
Understand where files are stored.
Teams is not an independent document store. Microsoft's architecture overview explains its connections with other Microsoft 365 services. Channel files use SharePoint; files shared in a chat can come from OneDrive.
This matters when an employee leaves or a project changes hands. We can review SharePoint and OneDrive usage to decide where long-lived documents belong. The shortcut visible in Teams does not, on its own, explain who owns a file or who can access it.
Prepare meetings, guests and mobile working.
A useful rollout includes tests with meeting organisers, external participants and people working away from the office. Check audio equipment, connectivity, invitations and screen-sharing rules.
Guest access needs an approval process and a review when assignments end. Recording and transcription settings should reflect your use cases, licences and internal rules. Short training sessions built around real situations are more useful than a tour of every button. Test the experience from an external account as well, because an organiser's view does not show every difficulty a guest may encounter.
Agree the scope of support.
An engagement can cover team structure, collaboration settings, a pilot and practical usage guidance. Administration responsibilities, request handling and workspace reviews need to be agreed separately.
IT governance helps define who may create teams, invite guests, archive spaces or delete them. We also recommend documenting apps added to teams: a third-party tool may request permissions over business information. Approving an integration should therefore depend on its usefulness and the access it actually needs. Keep a named owner for each approved integration so that it can be reviewed later.
Does Teams replace our telephone system?
Not automatically. Calls between users and calls to the public telephone network have different requirements. Teams Phone and carrier connectivity need a review of licences, numbers, equipment and reception workflows. The add-on licensing documentation explains these distinctions. You should also plan how calls will be handled if normal connectivity is unavailable.
Is a private channel enough for sensitive files?
A private channel does not remove the need to check its members, sharing links and file locations. Test access using the relevant user profiles and document exceptions. For particularly sensitive material, agree document ownership and permissions before conversations begin. Decide who reviews membership when a project changes or an external participant's work finishes.
What happens to a team when a project ends?
It needs someone responsible for closure. That person decides which documents remain useful, who takes ownership and which external permissions to remove. Archiving, retention and deletion serve different purposes. A written rule helps avoid both abandoned workspaces kept indefinitely and premature deletion of information that the business still needs to consult.
Microsoft sources
Why work with Sunitech on your Microsoft Teams project?
Advice and solution selection
Review of your needs, comparison of options and clearly explained priorities.
Deployment and integration
Preparation, configuration, testing and coordination with the relevant providers.
Support and development
Agreed support scope, documentation, licences and next steps.
A project? A question?
Let’s discuss your needs.
An initial conversation to understand your situation and decide on the next steps together.
Contact us
- Review of your environment
- Understanding your business challenges
- Guidance and recommendations
- No obligation