Search18 Results

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.

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.

This article explains what happens to a Microsoft Team when its only owner leaves Bowdoin, how to check whether a Team still has an active owner, and how to get ownership restored. It also lists the handover a departing Team owner should complete.

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.

Explains how a Team owner can limit file sharing in a Team so that only owners can create sharing links or invite others to files and folders. Because Teams files are stored in a connected SharePoint site, the change is made in the site's sharing settings. Applies to Bowdoin faculty and staff who own a Team, especially for confidential or restricted groups.

Explains how a Team owner can make a folder in a Team read-only so members can view files but cannot edit, upload, or delete them. Because a Team's files are stored in a connected SharePoint site, the permission change is made in SharePoint. Applies to Bowdoin faculty and staff who own a Team.

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 what changes and what stays the same when a Microsoft Team or one of its channels is renamed. It covers why the SharePoint web address keeps the old name, what other people notice afterward, and the order a Team owner should work in.

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 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 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 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.

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 why giving one person access to a single folder inside a standard channel usually causes more problems than it solves, and describes four better ways to reach the same result. It also covers what to record when a custom folder permission genuinely is required.

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.