Claude for Education (Anthropic) FAQ

1. You are not in the correct group. Please submit a service ticket to request access.
2. If you believe that you are in the correct group or have confirmation that you are in the correct group by IT, please go to logout.dartmouth.edu, close your browser, and try again.

1. The Dartmouth Enterprise license does not currently offer licensing for Claude Code. However, we have heard from many users that this upgrade is desired, and we are working quickly to identify how to provide this tool. 

1. Try to use Google Chrome or Microsoft Edge as your browser. Issues have been reported using Firefox and Safari
2. You may need to go to logout.dartmouth.edu then try again. Sometimes closing your browser completely after going to logout.dartmouth.edu before trying again is required. 

1. Absolutely! The sign-in process will work the same as described in first-time log in as described in the related article on the right of this page.
2. Windows Note: If you encounter any errors installing the desktop app during the initial Claude welcome screen and setup, please visit this link for the direct download. 

1. Currently Connectors are being evaluated by the Information Security team and more information will be available soon. 

1. Log in using the normal email sign-in, and not the single sign-on at Claude.
2. You can then toggle between the accounts if logged into both with the toggle in the bottom-left corner

Let's start off with good news. Your tokens will refresh every 5 hours. 
Individuals use tokens in various ways since Claude doesn't count messages, it counts tokens (roughly 3/4 of a word), and every interaction uses a different amount. A quick one-line question barely dents your limit, while uploading a large document, running a complex task, or carrying on a long conversation can burn through tokens rapidly. This is because Claude re-reads your entire chat history with every new message, and agentic tasks (where Claude takes multi-step actions on your behalf) can use 10-100x more tokens than a simple chat. Because of this variability, there's no single honest answer to "how many messages do I get?"
More information Usage limit best practices | Claude Help Center

1. Visit their status page at Claude Status

Below are a few resources from Anthropic’s website. As the pilot rollout moves forward, we will compile additional  Dartmouth resources to complement those listed below.

1. Claude 101
2. https://claude.com/resources/tutorials
3. Claude's Status Page
4. Claude's Usage Best Practices
5. Claude's FAQ
6. https://claude.com/resources/tutorials/getting-started-with-claude-in-excel

The Reality of AI Tools Today There is no single AI tool that does everything best. Claude, Copilot, ChatGPT, Gemini and others each have their own strengths, and honestly the landscape is shifting fast enough that today's answer might look different in six months.

It Comes Down to Use Case Some tools integrate more naturally into certain workflows. If you live in Microsoft 365 all day, Copilot may feel more seamless. If you are doing long-form document analysis or research synthesis, Claude's context window tends to shine. If your team is already deep in Google Workspace, Gemini makes sense to explore. The best tool is often just the one that fits how you actually work.

Institutional vs. Personal Use Where it gets more nuanced at Dartmouth is the distinction between what is sanctioned for institutional use and what individuals choose to use on their own. From ITC's perspective, our role is to make sure that when institutional data is involved, the tool in use has gone through the appropriate review. Outside of that, individuals are free to make their own choices about what works best for them.

Our Recommendation Try them. See what resonates. If you find yourself wanting to use a particular tool with Dartmouth data or in a Dartmouth workflow, that is when you loop us in so we can make sure it is set up safely.

Here are is a general Dartmouth AI page with resources 

You can find more information at this Article - AI Data Sensitivity Guide page.

Status: Claude Websearch is now enabled. 

Recommendations: Best practices include:

• Don't enter data you wouldn't put in an email to an external party
• Avoid student PII, medical information, or confidential research data
• The "Incognito" mode in Claude doesn't save conversations if you want an extra layer of privacy

Status: Claude Cowork is not currently available.

Reason: Currently under security review. 

 

Status: Claude Connectors are available upon request. 

How do Connectors get approved? The ITC Third-Party Application Review process evaluates for security risk and alignment with Dartmouth's policies. Once an app is approved, other users can find and install it without needing subsequent reviews, unless the app's scope changes. Here is the link to request a Third-Party Application Review. Please see this link for allowed Claude Connectors.

Reason: Many connectors provide various access and permissions such as:

Each Connector is Essentially a New Data Pipeline - When you add a connector in Claude, you are authorizing Claude to read from and potentially write to that external service. Every connector is a new data flow that needs to be evaluated on its own merits. Google Drive, Slack, GitHub, Salesforce, they each carry different data types, different sensitivity levels, and different risk profiles.

Scope of Access is Broad by Design - Connectors are not read-only in many cases. Claude can take actions on your behalf through those connections. That means a compromised session, a misconfigured permission, or an unvetted connector could result in data being moved, modified, or exfiltrated without the user fully realizing it.

FERPA, HIPAA, and Research Data Exposure - At Dartmouth specifically, any connector touching systems that could surface student records, health data, or sensitive research outputs triggers compliance obligations. Information Security needs to verify that the connector vendor has appropriate data handling agreements and that the data flowing through Claude is not being retained or used downstream.

Chain of Custody Problem - Once data passes through Claude and into a connector, you now have a multi-party data chain. Anthropic, the connector vendor, and the destination service all become relevant parties. Without a review, Dartmouth has no visibility into that chain.

Insider Threat and Credential Risk - Connectors authenticate using credentials or OAuth tokens. If those are not properly scoped and managed, a bad actor with access to the Claude instance could potentially leverage those connections in ways the user never intended.

The ITC Third-Party Application Review process requires administrator approval before any third-party app from platforms like Microsoft, Slack, or Zoom can be made available in the Dartmouth tenant, ensuring each app is evaluated for security risk and alignment with Dartmouth's policies. Once an app is approved, other users can find and install it without needing subsequent reviews, unless the app's scope changes. Here is the link to request a Third-Party Application Review. Below are approved connectors with their recommended and safe uses.

Timeline: The approval process can up to two weeks, if approved. Please use the Third-Party Application Review to submit a new request for any connector you would like to be reviewed. 

Status: Claude Ask Dartmouth is not currently available in the production tenant.

Status: Claude in Chrome is not currently available.

Reason: This is still in Anthropic preview mode and more testing is needed. 

​​​​​Full Browser Visibility - Claude in Chrome can see what is on your screen as you browse. In a university environment, that means it could be observing anything from student-facing portals, Banner or PeopleSoft sessions, research databases, email, financial systems, basically anything a student, staff or faculty member has open in their browser.

Session and Credential Exposure - If Claude in Chrome is active during an authenticated session, it has visibility into that session context. That is a significant concern for any system that handles privileged access, including systems administrators who might have elevated permissions open in the same browser.

FERPA and Sensitive Data Capture - An individual using Claude in Chrome while reviewing grades, advising notes, or financial aid information could inadvertently expose FERPA-protected data to the extension and by extension to Anthropic's infrastructure, without any formal data handling agreement covering that scenario.

No Granular Control Today - Unlike a managed enterprise deployment, there is currently no easy way for Dartmouth IT to scope what Claude in Chrome can and cannot see at the browser level. It is largely all or nothing from a visibility standpoint.

Audit and Logging Gaps - Dartmouth would have no visibility into what data Claude in Chrome is capturing or transmitting during a session, which creates a real gap in the audit trail that compliance teams would flag immediately.

Use Behavior is Unpredictable - The extension does not require the user to deliberately share something, it is ambient by design.

Timeline: Months out, if approved. ITC is currently investigating a safe roll out of Claude in Chrome and what required training may look like due to the access it permissions it receives. 

Status: Claude Code is not currently available.

Reason: Dartmouth will continue to work with Anthropic on how Claude Code/Premium Seats can be purchased. 

Timeline: Getting closer. Anthropic has a plan in place but are figuring out on how to apply to the Dartmouth environment.