Plan the workspace
Decide whether the work needs a chat, channel, OneDrive draft, SharePoint library, list, or page. Name the owner, audience, deadline, and final location before files scatter.
Microsoft 365 end-user manual
Microsoft 365
A practical user guide for working better with Microsoft Teams, OneDrive, and SharePoint: where to store work, how to share safely, how to run cleaner meetings, and how to turn conversations into durable team knowledge.
Important: Microsoft 365 is configurable. Your organization may change app availability, external sharing, Teams creation, retention, sensitivity labels, meeting recording, Copilot, guest access, and storage rules. Use this guide as a baseline and align it with internal policy.
Start here
Quick Start: Pick the Right Tool
Many productivity problems come from using the right app at the wrong stage. Use this workflow to decide where work should begin, where it should be discussed, and where the final version should live.
Clickable Microsoft 365 Workflow
Click each step to see how a team should move work from idea to governed knowledge.
Choose a daily lens
Role-Based Daily View
Different users need different habits. Use these tabs to focus the guide on everyday actions.
Keep conversations actionable
Use Teams to reduce scattered email, but do not let decisions disappear in chat. Post decisions, files, and action items in the correct channel.
- Use channel posts for topics the team needs to see.
- Use chats for short-lived private coordination.
- Turn meetings into notes, tasks, and shared files.
Use Teams when
You need conversation, meetings, quick decisions, channel announcements, task coordination, or a place where people can ask questions around shared work.
Use OneDrive when
You are drafting, storing personal work files, sharing a file with a small audience, recovering a previous version, or syncing your own files across devices.
Use SharePoint when
The content belongs to a team, department, project, process, or audience. SharePoint is where durable files, pages, lists, and governed knowledge should live.
Access and expectations
Before You Begin
Teams, OneDrive, and SharePoint can store business records, confidential information, customer data, contracts, and internal decisions. Start by understanding access, ownership, and lifecycle expectations.
Know the data sensitivity
Do not share files broadly when they include employee, customer, financial, legal, security, or regulated information. Use your organization's labels and sharing rules.
Know the owner
Every team, file, site, library, list, and page should have an owner. If no one owns it, no one will clean it, update it, or answer access questions later.
Know the final home
Before sharing a draft, decide whether the final version belongs in OneDrive, a Teams channel file library, or a SharePoint site/library.
Minimum information before creating a workspace
- Business purpose and audience.
- Owner, backup owner, and expected contributors.
- Whether guests or external people are allowed.
- Where final documents and records should be stored.
- Whether retention, sensitivity labels, or approvals apply.
Find your way around
Microsoft 365 Navigation
Most users move between the Microsoft 365 app launcher, Teams, OneDrive, SharePoint, Outlook, and Office web apps. Search and file context are often more reliable than remembering where something was originally opened.
Use search first
Search by file name, person, team, channel, meeting title, keyword, or site name. If results look wrong, check the app, location, date, and permissions.
Watch the file location
A file opened in Teams may live in SharePoint. A file shared from OneDrive still belongs to the person who owns that OneDrive.
Favorite key places
Pin important Teams channels, follow SharePoint sites, add shortcuts to OneDrive when appropriate, and favorite frequently used files.
Teams foundation
Teams Basics
Teams is the collaboration hub for chat, channels, meetings, files, apps, and notifications. The best Teams users keep work visible without overwhelming everyone.
Screenshot hotspot
Read a Teams workspace
Use the hotspot markers to understand the parts of a Teams workspace that matter for daily productivity.
Use the left rail to move between work modes
Activity, Chat, Teams, Calendar, Calls, Files, and apps are different work surfaces. Choose the surface that matches the job instead of treating Teams as one large chat box.
Step-by-step: set up your daily Teams view
- Open Teams and review Activity for mentions, replies, reactions, and channel notifications.
- Pin or show the apps you use daily, such as Chat, Teams, Calendar, Calls, Files, Planner, or Approvals.
- Pin the channels where you have recurring work or decisions.
- Hide or mute low-value channels instead of letting every channel compete for attention.
- Use status, quiet hours, and notification settings to protect focus time.
Conversation management
Chat, Channels, and Posts
Use chats for short-term private coordination. Use channels for work the team may need to find later. The more important the decision, the more visible and structured the post should be.
1:1 chat
Use for quick questions, private coordination, or sensitive context that does not belong in a broad channel.
Best for: fast private follow-up.
Group chat
Use for temporary coordination with a small group. If the topic becomes recurring, move it to a channel.
Best for: short-lived collaboration.
Channel post
Use when the team needs visibility, searchable history, threaded replies, or file context tied to a team.
Best for: durable team discussion.
Announcement
Use for important updates with a clear audience, headline, decision, and next action.
Best for: high-signal messages.
Step-by-step: post a useful channel update
- Choose the team and channel that owns the topic.
- Start a new conversation instead of replying to an unrelated thread.
- Write a clear subject line or opening sentence.
- Attach or link the file from its correct location.
- Use @mentions sparingly: mention the team, channel, or person only when action is needed.
- End with the decision needed, due date, or next owner.
Chat etiquette that saves time
- Do not send a vague "Hi" and wait. Ask the question with enough context.
- Use reactions for acknowledgement instead of creating extra messages.
- Move long or complex topics to a meeting, channel post, Loop component, Planner task, or shared document.
- Do not use chat as the only record for approvals, policy decisions, or final instructions.
Meeting productivity
Meetings and Calls
A Teams meeting should produce decisions, notes, owners, and follow-up. If it does not, it becomes an expensive conversation with no record.
Before the meeting
Create a clear title, invite only required people, add agenda/context, attach pre-read files, and decide whether the meeting belongs in a channel.
During the meeting
Use chat for links, screen share for review, notes for decisions, captions when helpful, and recording only when policy allows and the value is clear.
After the meeting
Post recap, decisions, files, tasks, owners, and due dates in the channel or shared location where the work will continue.
Step-by-step: run a productive Teams meeting
- Schedule from Teams or Outlook with a clear outcome in the title.
- Add agenda bullets, decision points, and any pre-read links.
- Start on time, confirm the goal, and assign a note taker or use collaborative notes if available.
- Share the correct window or file, not the whole screen unless needed.
- Capture decisions and action items as they happen.
- End by confirming owners, deadlines, and where the recap will be posted.
- Post follow-up in the channel or shared workspace within the same business day.
Files inside Teams
Teams Files and Apps
Files shared in a standard Teams channel are stored in the connected SharePoint site. Files shared in a chat are typically stored in the sharer's OneDrive. That difference matters for ownership and long-term access.
Channel file path
Teams ChannelFiles tabSharePoint Library
Use this path when the file belongs to the team or project and should survive beyond one person's employment or role.
Chat file path
ChatShared fileSender's OneDrive
Use this path for short-term sharing, but move final team-owned files to SharePoint or a channel file library.
Step-by-step: manage a file shared in Teams
- Open the file from the channel or chat.
- Confirm whether it lives in SharePoint or OneDrive.
- Use version history if you need to compare or restore changes.
- Use comments and @mentions inside the file for review requests.
- Move or copy the final file to the correct team-owned location when it becomes an official record.
Personal file workspace
OneDrive Basics
OneDrive is your personal Microsoft 365 file space. It is best for drafts, personal working files, controlled sharing, sync, recovery, and files that are not yet ready for a team-owned library.
My files
Personal work files and drafts you own. Share carefully because access can depend on your account and link settings.
Shared
Files shared with you or by you. Review this area when you cannot find a file in your own folders.
Recycle bin
Use when a file or folder was deleted by mistake and still falls within your organization's recovery window.
Step-by-step: organize your OneDrive
- Create a small set of folders based on work type, not every meeting or every day.
- Use clear file names with topic, date or version cue, and audience.
- Move team-owned final documents into the right SharePoint library.
- Clean old drafts monthly so search results stay useful.
- Use shortcuts or sync for active libraries, but avoid syncing everything.
Access and links
Syncing, Sharing, and Links
Sharing is powerful and risky. The safest link is the narrowest link that lets the right people do the right work for the right amount of time.
Sharing decision helper
Pick the right sharing option
Click each permission type to understand when it fits and what to check before sending a link.
Use the narrowest audience
Specific people links are usually the safest option for sensitive or limited-audience files because the link works only for named recipients.
Step-by-step: share a OneDrive file safely
- Select the file and choose Share.
- Open link settings before copying or sending the link.
- Choose the audience: specific people, existing access, people in your organization, or external users if allowed.
- Choose view or edit access. Use view access unless collaboration requires editing.
- Add expiration or password settings when your organization provides them and the file warrants it.
- Add a short message explaining why the file is shared and what action is needed.
- Review Manage access later to remove stale permissions.
Step-by-step: sync files without clutter
- Sync only active work libraries or folders you need in File Explorer.
- Use Files On-Demand if available so cloud files do not consume local storage until opened.
- Check sync status icons before traveling or working offline.
- Resolve sync conflicts immediately and avoid renaming or moving files while sync is still processing.
- Stop syncing old libraries when the work ends.
Undo and recover
Version History and Recovery
OneDrive and SharePoint can help recover from accidental edits, overwrites, and deletions. The key habit is to check version history before recreating work manually.
Version history
Use when a file changed incorrectly, content disappeared, or you need to compare earlier versions.
Recycle bin
Use when a file or folder was deleted and you need to restore it within your organization's retention window.
Restore OneDrive
Use when many files were deleted, corrupted, or changed at once. Escalate to IT if you suspect ransomware or mass change activity.
Step-by-step: restore a previous file version
- Open OneDrive or the SharePoint library that contains the file.
- Select the file and open Version history.
- Review the modified date, editor, and version notes if available.
- Open the prior version to confirm it contains the content you need.
- Restore the version or save a copy, depending on your organization's practice.
- Tell collaborators what changed so they do not overwrite the restored version.
Team-owned workspace
SharePoint Sites
A SharePoint site is a team, department, project, or communication workspace for durable content. It can include document libraries, pages, news, lists, navigation, and permissions.
Team site
Use for collaboration by a group that creates and edits content together, often connected to a Microsoft 365 group and Teams.
Communication site
Use for broad publishing where a smaller set of owners creates content for a larger audience.
Hub site
Use when related sites need common navigation, search scope, branding, and roll-up content. Usually managed by admins or site owners.
Step-by-step: create a useful SharePoint site request
- Define the site purpose in one sentence.
- Identify owner, backup owner, members, visitors, and whether guests are needed.
- Decide if the site is for collaboration or broad publishing.
- List the first libraries, pages, lists, or links the site needs.
- Confirm retention, sensitivity, and naming requirements with your site owner or IT team.
- Request the site using your organization's approved process.
Document management
Document Libraries
A SharePoint document library is more than a folder. It can hold metadata, views, version history, approval states, alerts, flows, and permissions that help teams manage files at scale.
Folders
Use for familiar grouping when the structure is simple, but avoid deeply nested folders that hide files from search and views.
Metadata
Use columns such as department, document type, owner, status, effective date, or audience to make filtering and views more useful.
Views
Use views to show the same library by owner, status, category, recent updates, approvals, or audience without duplicating files.
Step-by-step: upload and classify a document
- Open the correct SharePoint site and document library.
- Choose Upload or drag files into the library.
- Complete required metadata columns such as owner, status, category, or effective date.
- Check version history and approval status if the library uses them.
- Share the library link or file link rather than creating duplicate email attachments.
Step-by-step: create a view
- Open the library and choose the view menu.
- Create a new view and name it for the audience or task.
- Select columns that matter for the workflow.
- Add sorting, grouping, or filters, such as Status equals Approved.
- Save the view and confirm whether it should be public or personal.
Publishing and tracking
Pages, News, and Lists
Use SharePoint pages and news for readable knowledge. Use Microsoft Lists or SharePoint lists when the team needs structured rows, columns, status tracking, ownership, and filtered views.
Page
Use for evergreen instructions, onboarding, FAQs, process overviews, and curated links.
Best for: durable knowledge.
News post
Use for timely announcements that should appear in news rollups and alerts.
Best for: timely updates.
List
Use for structured tracking such as requests, assets, issues, contacts, inventory, or approvals.
Best for: rows and statuses.
Document library
Use for files that need version history, metadata, and document-centered collaboration.
Best for: managed files.
Step-by-step: create a SharePoint page
- Open the SharePoint site where the page belongs.
- Choose New, then Page.
- Pick a template, title the page clearly, and add sections.
- Add web parts such as text, image, quick links, files, people, list, document library, or call to action.
- Preview the page, check mobile readability, and publish when ready.
- Share the page in Teams or email with a brief reason and next action.
Step-by-step: create a simple list
- Open the site and choose New, then List.
- Start from a blank list, existing list, template, or Excel file.
- Add columns for the workflow: owner, status, due date, category, priority, and notes.
- Create views such as Open items, My items, Due this week, or Completed.
- Test with a few sample rows before asking the team to use it.
Access control
Permissions and Sharing
Permissions determine who can see, edit, download, share, or manage content. End users should understand the common levels and know when to escalate to a site owner or IT.
Step-by-step: review file or folder access
- Select the file, folder, library, or site content.
- Open Manage access or the permissions panel.
- Review direct access, links, groups, and guests.
- Remove stale links or ask the owner to remove access when you do not have permission.
- Use specific people links for sensitive items instead of broad organization links.
When to ask a site owner or IT
- You need to share externally and external sharing is restricted.
- A library has broken or confusing unique permissions.
- A user can see content they should not see.
- A site has no active owner.
- Sensitive data may have been shared too broadly.
Make the tools work together
Productivity Workflows
Productivity improves when teams use the tools as a connected system: discuss in Teams, draft in OneDrive, publish in SharePoint, track structured work in Lists or Planner, and clean up access regularly.
Reduce email attachments
Share cloud links, coauthor, comment, and manage access instead of emailing new copies.
Use one working file
Keep drafts in one place and use version history rather than creating v1, v2, final, and final-final copies.
Make meetings searchable
Store recap, decisions, notes, recording links, and tasks in the channel or site that owns the work.
Clean up access
Review broad links, inactive guests, old teams, stale files, and missing owners on a recurring schedule.
Do the work
Scenario-Based Guides
Use these scenarios when teaching teams how to choose the right app and complete a common workflow from start to finish.
Scenario builder
Choose a workflow
Select a workflow to see what to set up, what to avoid, and where the final record should live.
Create one project workspace
Use Teams for discussion, a channel Files tab or SharePoint library for shared documents, Planner or Lists for task tracking, and a SharePoint page for final project knowledge.
- Create or use an approved team and channel.
- Set project owners and meeting cadence.
- Publish final documents to SharePoint.
Step-by-step: launch a project workspace
- Confirm whether an existing team or SharePoint site should be used.
- Create or request a channel for the project if the topic is ongoing.
- Add tabs for files, Planner or Tasks, important pages, and key dashboards if approved.
- Create a document library folder or view only if it improves findability.
- Post a kickoff message with goal, owner, timeline, decision log, and file location.
- Schedule recurring meetings with notes and action items tied to the workspace.
- At closeout, archive discussions, publish final files, and remove temporary access.
Step-by-step: move a final file from OneDrive to SharePoint
- Open the OneDrive file and confirm it is the current final version.
- Check version history and comments for unresolved changes.
- Move or copy the file to the correct SharePoint library.
- Complete required metadata and confirm library permissions.
- Share the SharePoint link in Teams and remove unnecessary OneDrive sharing links.
Keep it clean
Governance and Good Practice
Good Microsoft 365 habits protect productivity and information security. End users do not need to be administrators to keep workspaces clean, findable, and safe.
Least access
Give people the access they need, for the purpose they need, and remove access when the work ends.
One source of truth
Avoid duplicate final files. Publish the final record in the team-owned location.
Clear ownership
Make sure Teams, sites, files, pages, and lists have active business owners.
Monthly cleanup checklist
Fix common issues
Troubleshooting
Most Microsoft 365 issues come from permissions, sync, duplicate files, wrong location, meeting settings, or unclear ownership. Check context before recreating the work.
| Issue | Check first | Typical owner |
|---|---|---|
| Cannot find a file | Search OneDrive, Teams, SharePoint, Shared with me, Recent, and the channel Files tab. Check whether it was shared by link. | File owner or site owner. |
| Cannot open a file | Permissions, account, guest status, expired link, sensitivity label, external sharing policy, or deleted file. | File owner, site owner, or IT. |
| Sync is stuck | Network, file path length, invalid characters, open Office files, storage space, duplicate names, or sync client status. | User first, then IT. |
| Too many Teams notifications | Channel notification settings, pinned channels, @mentions, activity filters, quiet hours, and meeting chat notifications. | User or team owner. |
| Meeting recording missing | Recording permissions, organizer settings, policy, storage location, expiration, and whether recording was actually started. | Organizer or IT. |
| SharePoint page outdated | Page owner, last modified date, source documents, audience targeting, and whether the content should be archived. | Page owner or site owner. |
Reference
Glossary
Channel
A focused conversation and file area inside a Team. Standard channel files are stored in SharePoint.
Chat
A private 1:1 or group conversation. Chat-shared files usually live in the sharer's OneDrive.
Document library
A SharePoint file container with metadata, views, version history, and permissions.
Guest
An external person invited to collaborate under your organization's guest access rules.
Metadata
Columns or properties used to describe files or list items so they can be filtered, grouped, and managed.
OneDrive shortcut
A shortcut to shared content that appears in OneDrive, often used for active SharePoint libraries or folders.
Permission link
A sharing link that controls who can access content and whether they can view or edit.
Version history
A record of prior file versions that can be reviewed or restored when mistakes happen.