Search6 Results

This article explains how data is handled in a Bowdoin-managed Claude account, including that prompts and outputs are not used to train models by default, that Bowdoin's Primary Owner manages the account and its data, and how retention works. It directs Bowdoin-specific policy questions to Bowdoin IT.

This article explains why connected apps stop working after migration — authorizations are revoked for security — and how to reconnect them from the Bowdoin account. It also covers custom connectors, project sync re-authorization, and Bowdoin connector policy.

This article explains that custom skills have no migration path and are lost when a personal account closes, so they must be exported first. It walks through saving skills before migrating and re-adding them in the Bowdoin account, subject to College policy.

This article describes exactly what moves and what does not move when you migrate a personal Claude account into Bowdoin's managed workspace, including chats, projects, skills, and connectors. It also explains what happens to a paid Pro or Max subscription depending on how it was purchased, including the Apple App Store case.

Step-by-step instructions for setting up Okta Verify on a mobile device when activating a new Bowdoin account for the first time. Covers downloading the app, logging in with temporary credentials, completing multi-factor authentication enrollment, and adding a recovery email address. Applies to all incoming faculty, staff, and students.

Explains when Bowdoin accounts are disabled and deleted for faculty, staff, and students after they leave the college. Timelines differ by role: staff accounts are disabled immediately, faculty accounts remain active for 30 days, and student accounts are disabled on October 31 of their graduation year and deleted the following February 1. Account extensions may be available.