Guide Library

Agent Workshop

Agent Workshop - Connect Your Agent to Your Information Inside Claude

Week 3Agent Workshop

  • 20–30 minGuided walkthrough

Use a desktop browser for this workshop. You'll add your Safety & Security Rules to My Agent, your Claude Project, and number their versions. Then you'll learn what a connector can reach, what Claude lets you limit and who decides, and hand your agent a meeting transcript.

Watch the video walkthrough in StormWind Campus (sign in with your bootcamp login).

What You Need for This Guide

  • A desktop browser and your approved Claude work account, with Project and file-upload access if you have it.
  • My Agent, with your and Communication Style Guide in it.
  • Your saved Safety & Security Rules from this week's session.

Give Your Agent Your Voice Inside Claude

Build Your Safety & Security Rules

Choose the tool you’re allowed to use

Your approved tool

The tool your company approved.

Pick your approved tool above to see the steps and screenshots for it.

Start guide
6 steps · At your own pace
About saved progress

No account needed. Checkmarks save on this browser and device when browser storage is available. If storage is blocked or full, new checkmarks last until you reload or close this page. Progress doesn’t sync to other browsers or devices. Clearing this site’s browser data removes it, and private browsing may not keep it after you close the window.

Standard Data rules for AI at work

Data Rules

Data rules for AI at work

Check with your IT Team before you paste any work data into an AI tool. Avoid names, account numbers, customer data, or anything sensitive without explicit permission from IT. If you aren't sure, redact anything sensitive and replace it with generic information. AI makes mistakes, make sure to fact check your agents outputs even if they sound right.

Before you start

  • Check with your IT teamAsk what your company allows before you put anything from work into an AI tool. Your company policy is the one that counts, and it is the one this library cannot see.
  • Use the tool your company approvedChatGPT, Claude, Microsoft 365 Copilot Chat and Gemini are all covered here. Use the one your company approved, not the one you like best.
  • Sign in with your work accountA work account keeps your chats inside the agreement your company signed. A personal account in the same product sits outside it.
  • Connected appsAn email or file connection your IT team approved can read the names and addresses in what it opens. Everything else under “Never put this into an AI tool” still applies.
  • No approved account yetFollow the steps with made-up example text, or on paper, until IT gives you one.

Never put this into an AI tool

  • Customer or personal detailsNo names, email addresses, phone numbers, home addresses or account numbers. That covers colleagues as well as customers.
  • Regulated recordsHealth, financial, HR and legal records stay in the systems built to hold them, unless IT has told you in writing that this tool may see them.
  • Passwords, keys and access codesNo credentials of any kind, yours or anyone else’s, and nothing that grants access to a system.
  • Anything under an NDA or not yet publicUnreleased plans, contracts, pricing and source code need clearance before they go near a chat window.
  • Anything your company policy prohibitsYour company’s rules win over anything in this library. If policy keeps something out of AI tools, it stays out, whatever a guide suggests.

Do this instead

  • Swap real details for placeholdersWrite “Customer A”, “[client name]”, “$X”. You get the same quality of answer, and you put the real details back yourself.
  • Describe the situation rather than pasting the documentMost of what an agent needs is the shape of the problem, not the file it arrived in.
  • Trim a file before you upload or paste itTake out the identifying columns and pages first, or work from a short extract.

Check the answer before you use it

  • Read it as if a colleague had drafted itAn agent states wrong things with complete confidence. Your name goes on the work, so the check is yours.
  • Say where the agent helpedFollow your company rule on disclosing AI assistance, especially in client-facing or formal work.

When you are not sure

  • Ask before you paste or upload, not afterA question to your IT team takes a minute. Cleaning up after a data incident takes a great deal longer.
  • When in doubt, leave it outIf you would not put it in an email to someone outside the company, keep it out of the chat.
Open the full page
Download Guide

Step

Add your rules to My Agent

Your agent already knows your work and how you write. Your Safety & Security Rules tell it how to handle information, and in My Agent's Files they apply to every chat in the Project. This builds on the last two workshops, which set up My Agent with your profile and style guide, and on Build Your Safety & Security Rules, where you saved your rules. Do those first if you haven't. If your account has no Projects or file uploads, keep attaching or pasting your three files into each new chat, and use that chat wherever this guide says My Agent.

  1. In My Agent Files, make a Safety Rules folder beside your other two and move your rules file into it.

  2. In Claude, open Projects, then My Agent. Beside Files, select Add, then Upload from device, and choose your rules file.

  3. Select Edit beside Instructions, replace all of last week's text with this card and select Save instructions. It's last week's card plus one line for your rules, so add back any lines of your own.

    Project instructions with your rules
    You are my work agent. You help me with my day-to-day work.

You have these reference files. Use each one for its job:
- Agent Profile: my role, priorities, the people I work with and how I like answers. Use it as background whenever it's relevant.
- Communication Style Guide: how I write, including any My Voice Dial settings. Use it whenever you draft something I'll send or share. Copy its patterns, not the particulars of its examples. If one of its sections has its own instructions, follow them.
- Safety & Security Rules: how you must handle information, uncertainty, verification and human review. Follow them in every chat.

How to work with me:
- Don't invent facts about me, my organization or my work. If a missing detail would change your answer, ask me one question first.
- Run a file's First Setup Check only when I ask for it.
- My files are the master copies. When I ask to update one, follow that file's own VERSIONS section if it has one and give me the complete next version. Remind me to save it as my master file, keep the old file, and replace that file in this Project. Don't tell me the saved setup has been updated.

Step

Number your rules and replace them in My Agent

As with your other two files, each change to your rules becomes a new numbered file you keep, so you can always tell which version your agent is using.

  1. Start a new chat in the message box at the top of the My Agent page and send the no-change card, as the video does. If you have one change, such as an organization rule you've now confirmed, send the other card instead and fill in its bracketed line.

    Set up versioning for your rules (no change)
    I want to set up versioning for my Safety & Security Rules, so I can track every change.

Change to make: None, set up versioning only

Put any change in my rules file, not your built-in memory, so my file stays my master copy. Unless a rule conflicts, do all of this in one reply:

1. If I gave a change, put it in the section it fits best, such as My Organization-Specific Rules. Use my words, and don't add rules I didn't give you. If it would weaken or contradict a rule already there, stop before writing anything: quote both and ask me which one to keep.
2. If my rules have no RULES VERSIONS section, add the one below to the end of the file, word for word. If the file has no version number in its title, version line or filename, treat the current file as Version 1. Otherwise continue from its current number. Do not restart numbering.
3. Follow RULES VERSIONS to return the entire updated file, with the new version number in both its title and its filename. Keep every other section and rule word for word, including Rule Priority and anything I've added to a rule.
4. In the What changed table, list my change, if I gave one, and say whether you added RULES VERSIONS. Do not claim a section was added if it was already there.
5. End by walking me through saving it, as RULES VERSIONS describes.

RULES VERSIONS

The rules title, the version line under it, and the filename all show the same version number. Use simple whole numbers: v1, v2, v3, and so on. The title uses readable spaces, like My Safety & Security Rules v2. The filename uses hyphens and no spaces, like My-Safety-and-Security-Rules-v2.txt.

- If I ask which version you're using, give that line's number and date.
- If I ask you to update these rules, create the next version:
  1. Raise the current version number by one. Use that new number in the title and in the version line below it, like Version 2 | Updated October 20, 2026. These are examples: use the actual next number and today's date. If you can't see today's date, write DATE NEEDED.
  2. Apart from the title, version line and version history, change only what I asked. Keep every other rule and section word for word, in the same order.
  3. Add a one-line summary to the top of VERSION HISTORY. Keep the five newest lines.
  4. Give me the entire updated rules file as one downloadable plain-text file named My-Safety-and-Security-Rules-vNUMBER.txt, replacing NUMBER with the new version number. Use only plain letters, digits, hyphens and the dot before txt. Include every section and all unchanged content. If you can't create files, put the entire file in one code block and give me the exact filename above it.
  5. Show what changed in a table: Section, What changed, Why.
  6. Walk me through saving it: save the new file in the same folder as my earlier versions, keeping every older file. Then replace the rules in your saved setup the same way I first added them, start a new chat, and ask which version you're using.
- Never weaken, shorten or remove a rule unless I ask for that exact change. If a change would weaken or contradict a rule already here, quote both and ask me which one to keep before you write the new version.
- If I tell you something new that belongs in these rules, offer a new version. Wait for my yes.
- Never overwrite an earlier version or reuse its number.
- You can't change your own saved setup, so don't say my rules are updated until I've replaced the file.

VERSION HISTORY
- Version 1: Original rules.
    Set up versioning for your rules, with your change
    I want to set up versioning for my Safety & Security Rules, so I can track every change.

Change to make: [type one change, such as an organization field you've now confirmed, or write "None, set up versioning only"]

Put any change in my rules file, not your built-in memory, so my file stays my master copy. Unless a rule conflicts, do all of this in one reply:

1. If I gave a change, put it in the section it fits best, such as My Organization-Specific Rules. Use my words, and don't add rules I didn't give you. If it would weaken or contradict a rule already there, stop before writing anything: quote both and ask me which one to keep.
2. If my rules have no RULES VERSIONS section, add the one below to the end of the file, word for word. If the file has no version number in its title, version line or filename, treat the current file as Version 1. Otherwise continue from its current number. Do not restart numbering.
3. Follow RULES VERSIONS to return the entire updated file, with the new version number in both its title and its filename. Keep every other section and rule word for word, including Rule Priority and anything I've added to a rule.
4. In the What changed table, list my change, if I gave one, and say whether you added RULES VERSIONS. Do not claim a section was added if it was already there.
5. End by walking me through saving it, as RULES VERSIONS describes.

RULES VERSIONS

The rules title, the version line under it, and the filename all show the same version number. Use simple whole numbers: v1, v2, v3, and so on. The title uses readable spaces, like My Safety & Security Rules v2. The filename uses hyphens and no spaces, like My-Safety-and-Security-Rules-v2.txt.

- If I ask which version you're using, give that line's number and date.
- If I ask you to update these rules, create the next version:
  1. Raise the current version number by one. Use that new number in the title and in the version line below it, like Version 2 | Updated October 20, 2026. These are examples: use the actual next number and today's date. If you can't see today's date, write DATE NEEDED.
  2. Apart from the title, version line and version history, change only what I asked. Keep every other rule and section word for word, in the same order.
  3. Add a one-line summary to the top of VERSION HISTORY. Keep the five newest lines.
  4. Give me the entire updated rules file as one downloadable plain-text file named My-Safety-and-Security-Rules-vNUMBER.txt, replacing NUMBER with the new version number. Use only plain letters, digits, hyphens and the dot before txt. Include every section and all unchanged content. If you can't create files, put the entire file in one code block and give me the exact filename above it.
  5. Show what changed in a table: Section, What changed, Why.
  6. Walk me through saving it: save the new file in the same folder as my earlier versions, keeping every older file. Then replace the rules in your saved setup the same way I first added them, start a new chat, and ask which version you're using.
- Never weaken, shorten or remove a rule unless I ask for that exact change. If a change would weaken or contradict a rule already here, quote both and ask me which one to keep before you write the new version.
- If I tell you something new that belongs in these rules, offer a new version. Wait for my yes.
- Never overwrite an earlier version or reuse its number.
- You can't change your own saved setup, so don't say my rules are updated until I've replaced the file.

VERSION HISTORY
- Version 1: Original rules.

  2. Check the reply before you save. What changed should say whether RULES VERSIONS was added and list your change if you gave one. The title and version line should show the next version number: v2 if your rules had no number, or one higher than your current file's. Every other rule should be kept word for word. If not, ask in the same chat for a complete corrected file.

  3. Select Download and save the file in your Safety Rules folder under the name in the reply, such as My-Safety-and-Security-Rules-v2.txt, beside the earlier one. If Claude gives you text instead of a file, copy all of it into a new plain-text file with that exact filename.

  4. In Files, open the earlier rules file's menu and remove it, then upload the new file the same way. Start a new chat in My Agent and send this check. It should name the Safety & Security Rules version you saved.

    Check my file versions, with my rules
    Which versions of my files are you using?

Read the current Safety & Security Rules, Agent Profile and Communication Style Guide saved in this Project or Notebook, or attached to this chat. For each one, give its version number and updated date. If a number or date is missing, say so. Then quote the newest line of my rules' VERSION HISTORY. Use the files rather than an older conversation. Do not guess or change any file.

Step

Find where connectors live, and who decides

A connector lets your agent sign in to another app, such as Microsoft 365, and see what you see there, such as your email, calendar, Teams messages and files. It can make your agent far more useful, and it puts much more of your organization's data within reach.

Select Customize, then Connectors. Discover shows popular connectors, and Yours lists the ones your organization has added. One it hasn't added offers Request, which tells your organization's owners you'd like it. On Team and Enterprise plans an Owner adds each connector, and Microsoft 365 also needs your Microsoft admin's consent. A connector that's missing, or one you can only request, is your organization's answer for now.

Step

Know what a connector can do, and what you can limit

A connector's tools come in two kinds. Read-only tools search and read, and Write/delete tools send, change or delete. Writing carries the most risk, and reading still opens a door: a tool that can search your email can see all of it. Send this card in a chat in My Agent to have your agent explain the difference for your work.

Read-only vs write-back tools
Can you explain the difference between a read-only tool and a write-back tool in a connector?

These are Claude's controls:

  • Tool permissions. Open a connector you've connected in Customize, Connectors. Set each write and delete tool to Blocked, or to Needs approval for one you'll really use, and never Always allow. While it's connected, blocking a read-only tool, such as Outlook email search, is the only sure way to keep your agent out of that data. A limit your organization set can't be loosened.
  • One chat. Claude can use a connected app without being asked, so in a chat select +, then Connectors, and turn off any connector that chat doesn't need.
  • Disconnect. This button on the connector's page signs Claude out of the app.
  • Research. When you use Claude's Research feature, tools run without asking, so don't use it with a connector that can write.

Step

Learn Claude's connectors from its official page

Connectors change every few weeks, so learn them from Claude's own documentation, read through your agent so it explains what matters for your role.

  1. Open Use connectors to extend Claude's capabilities on Claude's support site.

  2. In a new chat in My Agent, paste the card. Then go back to the page, select Copy for LLM near the title, and paste the page in place of the card's bracketed line. If you can't find the button, copy the page's text yourself. Claude may show the long page as an attached file. Add a line such as “condense this to two paragraphs” if you like, then send it.

    Explain this page in a way that matters to me
    Can you explain this in a way that matters to me?

[paste the page you copied here]

  3. Check anything you'll act on against the page itself. The same method works for any Claude feature.

Step

Give your agent your meetings

A transcript keeps every word of a meeting, including the side conversation where a decision got made and then lost. Your agent can turn it into decisions and action items.

  1. Record and transcribe only where your organization's rules allow it, and tell everyone in the meeting and get their OK. Your Safety & Security Rules apply to a transcript like any other file.

  2. With an approved connector, such as Microsoft 365 for Teams meetings, your agent can pull the transcript. Without one, download it from your meeting app and attach or paste it into a chat in My Agent. Check the data rules before you do.

  3. Open Turn Your Meeting Transcripts Into Something Useful, select Download Guide, attach the file to the same chat or paste its text in, and ask your agent to walk you through it.

Agent Workshop - Connect Your Agent to Your Information Inside Claude

Confirm your result

Confirm the outcomes below to finish this guide.

Final checks

A new chat in My Agent (or a chat with your three files attached or pasted) names the current version of your Safety & Security Rules (the one the versioning card gave you) beside your profile and style guide.

You can name the connector you'd want first, whether read-only is enough for it, and what your tool lets you block or switch off, and your IT team has said yes in writing, or you know what you'll ask them.

Provide Feedback

Thanks. That went straight to the people who write these guides.