This article gives a department a structure to start from when moving shared files off the Microwave (J:) drive into a Microsoft Team. It includes two worked examples, the naming and nesting rules that keep the result usable, and guidance on what belongs in OneDrive instead.
This article explains how a Team owner adds channels to a Microsoft Team that is already in use, moves files between channels without losing version history, and removes channels the department no longer needs. It also explains which channel changes cannot be undone.
Instructions for archiving a Microsoft Team so its conversations and files become read-only, restoring an archived Team, and making specific SharePoint folders read-only when a whole Team cannot be archived. Also explains what happens to files in an archived Team and the Microsoft 365 Team expiration policy. Applies to Bowdoin Team owners and members.
Whether to add a shortcut or sync when you want Microsoft Teams channel files and shared folders to appear in File Explorer or Finder. Compares the two options, explains which one follows you between computers and which is tied to a single machine, and covers switching from one to the other.
This article explains what deleting a Microsoft Team removes, including the Team's SharePoint site and every channel's files. It also explains the 30 day window for recovering a deleted Team and why archiving is usually the better choice for a Team whose work is finished.
This article explains that a file attached to a Microsoft Teams chat is stored in the sender's own OneDrive and shared only with the people in that conversation, while a file posted in a channel is stored in the team's SharePoint library and is available to everyone with access to the channel. It covers how to tell the two apart, where meeting recordings are saved, and how to move a chat file into a channel.
This article explains how to search for a file in Microsoft Teams, SharePoint, and OneDrive, and what each search box actually covers. It also lists the common reasons a file that exists does not appear in your search results, and what to do next when no search turns the file up.
This article explains where a department's shared files live after they move from the Microwave department drive (J:) to Microsoft Teams. It covers how to open those files, how to reach them from File Explorer or Finder, and what changes compared with working on the J: drive.
This article explains why desktop shortcuts, recent file lists, spreadsheet links, browser bookmarks, and email signatures stop working after a department's files move from the Microwave (J:) drive into Microsoft Teams. It describes how to repoint each kind of link at its new location and why repairing links as they fail beats auditing every file at once.
This article explains what happens to a Bowdoin colleague's files after that person leaves the College. It describes which files stay available, which files disappear with the departed account, how a department requests recovery of files held in a departed colleague's OneDrive, and how to keep the same loss from happening again.
Step-by-step instructions for recovering a deleted document from the Recycle Bin in OneDrive, Microsoft Teams, or SharePoint, including how to check the second-stage Recycle Bin. Notes the 93-day total retention period after which items are permanently deleted.
This article explains how an owner of a Microsoft Team at Bowdoin can choose between sending an external sharing link, using a shared channel, and adding a guest to the Team. It describes what a guest can see once added, the 180-day expiry on external access, and how to remove a guest when the work ends.
Instructions for team and channel owners on adding, removing, and changing the roles of members in Microsoft Teams. Covers managing members of a team, a private channel, and a shared channel, explains owner, member, and guest roles, and lists reasons membership may not be editable. Applies to Bowdoin team and channel owners.
This article explains how to open Word, Excel, and PowerPoint files stored in Microsoft Teams using the installed desktop apps instead of Teams or a browser. It covers setting the desktop app as the default, opening a single file in the desktop app, and what to check when a file opens as read-only or when Office is not signed in with a Bowdoin account.
This article explains how a Team owner checks everyone who can reach the files in a Microsoft Team, including members, guests, people added directly in SharePoint, and anyone holding a sharing link. It also describes a short review a Team owner can repeat each quarter.
This article explains how version history works for files stored in Microsoft Teams, SharePoint, and OneDrive, where to find it, and how to put an earlier version of a file back. It also explains why restoring an older version does not erase newer ones.
This article explains how to give a Microsoft Teams channel its own email address, so that messages, scans, and automated reports arrive where the team already works instead of in one person's mailbox. It covers getting the address, limiting who may send to it, removing it, and when a different approach fits better.
This article explains how to give another person access to a file or folder stored in Microsoft Teams, SharePoint, or OneDrive with a Bowdoin account. It covers the link types available, the difference between edit access and view access, and when adding a person to the Team is a better choice than sending a link.
An explanation of how Microsoft Teams organizes work into channels, how permissions work across teams and channels, and where files are stored in the linked SharePoint site. Covers standard, private, and shared channels, owner and member roles, the folder structure behind Teams, managing channel settings, and best practices. Applies to Bowdoin students, faculty, and staff.
This article gathers everything a Bowdoin Microsoft Team owner is responsible for into one page. It covers the controls only owners have, why every Team needs at least two owners, membership and guest reviews, expiration notices, deletion risk, restricted data, and a recurring checklist, with each procedure named in the Related Articles section.
This article explains which kinds of files stop working, or lose data, when they are placed in a Microsoft Teams channel. It lists the file types a department should leave out of a migration from the Microwave (J:) drive and names where each type belongs instead.
This article explains why a Word, Excel, or PowerPoint file stored in Microsoft Teams, SharePoint, or OneDrive is sometimes locked, even though two people can normally edit the same file at the same time. It describes how to tell who is holding a file open, what checking a file out does, and how to keep working while a lock clears.
This article explains how to keep Microsoft Teams, SharePoint, and OneDrive files available on a computer when there is no internet connection. It covers marking files and folders to keep on a device, freeing that disk space again afterward, and what happens to edits made offline once the computer reconnects.
This article explains the email Microsoft sends to Team owners before an inactive Microsoft Team expires. It covers what the warning means, what counts as activity, how an owner renews a Team in one step, what is deleted if nobody acts, and what to do with a Team the department has finished using.