Custom Claude Project: Your Personal IT Environment Assistant

What This Builds

A Claude Project pre-loaded with your organization's IT environment documentation, common ticket types, KB articles, and approved tools list. Every conversation you open starts with AI that already knows your infrastructure — no re-explaining that you use ServiceNow, that your VPN is GlobalProtect, or that your AD domain is corp.yourcompany.com. The assistant becomes genuinely useful for your specific environment rather than giving generic answers.

Prerequisites

• Claude Pro account ($20/month) — required for Projects feature
• Comfortable using Claude for troubleshooting and documentation tasks (Level 3)
• An hour to gather and write up your environment documentation
• Access to your org's IT documentation (even partial)

The Concept

A Claude Project is a permanent workspace where you can upload documents that Claude references in every conversation. Unlike starting a new chat each time — where you have to re-explain your environment — the Project maintains context across all conversations.

Think of it like this: right now, when you ask Google "how do I configure VPN on Windows 11," it gives you generic answers. But if your coworker who knows your network setup answered the same question, they'd say "oh, for our GlobalProtect setup, you need to do X first because our gateway requires certificate auth." That context makes the answer immediately actionable instead of generically correct. This Project creates that coworker.

Build It Step by Step

Part 1: Create the Project

1. Sign in to claude.ai with your Pro account
2. Click "Projects" in the left sidebar
3. Click "+ New Project"
4. Name it: "IT Environment Assistant" or "[Company] IT Support"
5. Click Create

What you should see: A project workspace with a "Project knowledge" section for documents and a "Project instructions" section for configuration.

Part 2: Create Your Environment Documentation Document

This is the most important step. Create a new document (Word or text file) called "environment-overview.txt" with these sections:

## IT Environment Overview

**Company:** [Company name - optional]
**OS Standard:** Windows 11 22H2 / Windows 10 22H2 (mixed)
**Active Directory:** On-premises AD, domain: [corp.domain.com]
**Azure/M365:** Hybrid joined, M365 E3 licenses
**VPN:** [Product name + version]
**Email:** Exchange Online (M365)
**Ticketing System:** [ServiceNow / Jira / Zendesk + version]
**Remote Support:** [TeamViewer / AnyDesk]
**Endpoint Management:** [Intune / SCCM + version]
**Antivirus:** [Product]
**Backup:** [Product/service]
**MFA:** [Azure AD MFA / Duo / other]
**Key Servers:** [List major servers by function — don't include IPs or hostnames unless comfortable]
**Key Applications:** [List business applications you support]
**Known Ongoing Issues:** [Any persistent issues you deal with regularly]

Fill this in to your comfort level. Even partial information helps significantly.

Part 3: Upload Your Top KB Articles

Take your 10 most commonly referenced KB articles and copy their text into a single document called "kb-articles.txt". Include article titles as headers.

These are the articles that contain:

• Your VPN setup procedure
• Password reset steps (with your specific AD setup)
• Most common printer setup procedure
• Email setup for mobile devices
• Most common application troubleshooting steps

Claude will reference these as authoritative for your environment.

Part 4: Upload Both Documents

In your Claude Project's "Project knowledge" section, click the "+" or "Upload" button. Upload:

• environment-overview.txt
• kb-articles.txt

Wait for both to process (a few seconds each).

Part 5: Write Your Project Instructions

Click "Project instructions" or "Set project instructions." Paste and customize:

You are an IT support assistant for a help desk analyst. You have been loaded with the specific details of our IT environment in the uploaded documents.

WHEN ANSWERING TROUBLESHOOTING QUESTIONS:
- Reference our specific environment (OS versions, VPN product, AD setup) from the uploaded documents
- Prioritize solutions that work with our specific tools and infrastructure
- Provide specific commands, registry paths, and navigation steps — not generic advice
- When our KB articles cover the issue, reference them explicitly

WHEN GENERATING SCRIPTS:
- Use our environment specifics from the uploaded document
- Default to PowerShell 5.1 unless otherwise specified
- Include error handling and -WhatIf mode by default on modification scripts

WHEN WRITING DOCUMENTATION:
- Follow the KB article format established in the uploaded articles
- Use our terminology for systems and tools

ALWAYS:
- Tell me if my question requires information I haven't provided in the documents
- Flag if a solution might not apply to our specific setup

Click Save.

Part 6: Test With a Real Scenario

Open a new conversation in your Project. Test with a real current issue:

A user can't connect to VPN this morning. They're on their home network. Error message: [paste exact error]. Their setup should be our standard - what are the first 3 things I should check?

What you should see: A response that references your specific VPN product, gives troubleshooting steps appropriate to your environment, and possibly references your VPN KB article if you uploaded one.

Compare this to a generic ChatGPT answer. The difference should be meaningful.

Part 7: Maintain and Improve Over Time

The project gets more valuable as you add more environment documentation:

• After resolving a complex unique issue: add a note to kb-articles.txt
• When major changes happen (OS upgrade, VPN product change): update environment-overview.txt
• Add your org's escalation contacts and their areas if useful

Real Example: Typical Session After Setup

You open the project and ask: "New hire onboarding for a Marketing Coordinator. Walk me through what I need to set up."

What the assistant says: Instead of generic "create AD account, assign email" advice, it references your specific environment: "Based on your environment setup: Create their account in AD on [your domain]. Assign M365 E3 license in the admin portal. Add them to the Marketing distribution group. Set up [your VPN product] on their device using the procedure from the KB. Standard Intune enrollment should push [your antivirus] automatically. For the specific Salesforce access Marketing uses, they'll need a ticket to the Salesforce admin team."

What that saves: The cognitive overhead of context-switching between your documentation, your memory of the procedure, and generic advice. Everything is in one place.

What to Do When It Breaks

• Assistant gives generic advice instead of environment-specific → Ask "please reference our environment documentation when answering" — or update your instructions to emphasize this more strongly
• KB article information is outdated → Update the document in Project knowledge; Claude will use the updated version
• Project fills up (context window limit) → Claude Pro handles more context than free, but for very large environments, prioritize the most frequently referenced documentation
• Answer contradicts your actual setup → Your environment doc may be incomplete — add the specific detail Claude missed

Variations

• Simpler version: Just use the Project instructions (no document uploads) to configure Claude with your most common environment details — type them directly in the instructions field
• Extended version: Add a "scripts library" document with your most useful approved PowerShell scripts; Claude can reference and adapt them rather than generating from scratch each time

What to Do Next

• This week: Set up the project with at minimum the environment overview document; test it on your 3 most common ticket types
• This month: Add KB articles for your top 10 most common issues; refine the instructions based on where the output falls short
• Advanced: Create a second project specifically for change management documentation — upload your change management templates and procedures for consistent, policy-compliant CR drafting

Advanced guide for IT support technician / help desk analyst professionals. These techniques use more sophisticated AI features that may require paid subscriptions.