THE FUTURE MARKETACADEMY
Your classroomRoom 01 · AI Lab
School of AI

Claude Practitioner: design, teach and audit Claude workflows

Step 7 of 7 in AI Lab

Next in your path: 1.10.4 AI Peer Tutor: teach others to use AI well

What you'll be able to do
  • Audit a team's Claude setup (people, Projects, skills, connectors, privacy settings) and report what is safe, risky or unused.
  • Build a small set of tests for a Claude workflow, with success criteria you can check.
  • Review a workflow for risks: wrong answers, prompt injection and high-risk uses.
  • Teach others with a clear framework and a short hands-on training programme.
  • Write a one-page governance plan and a measurement plan.
  • Show your skills with a practical portfolio that another person can assess.

Before this course: Claude for Teams: shared Projects, workflows and standards (course 1.11.3), Claude Power Tools: Skills, Connectors (MCP), Claude Code and agents (course 1.12), and Claude Step by Step (course 1.11). You should already be able to set up a Team plan, share Projects and skills, add connectors and choose privacy settings. Here you move from doing it to auditing it, teaching it and leading it. The Future Market Academy is not affiliated with Anthropic. Menu names come from Anthropic's Help Center as of 2026-11-12 and some screens are being renamed, so look for the closest name. Plans, limits and prices change: check Anthropic's pricing page before you buy. This course is education, not legal advice.

Words in this course 59Open the Vocabulary Hall
01

Audit a team's Claude setup

In simple words

A good inspector walks through a house with a checklist, looks at everything, and writes down what is fine, what is broken and what is never used. You do the same for a team's Claude: look, record, and then suggest fixes.

Key facts
  • Before this course: Claude for Teams (course 1.11.3). That course built the setup; this lesson inspects it.
  • An audit compares what is written (rules, roles, standards) with what is really set up (settings, members, connectors, skills). The gaps are your findings.
  • Roles (Member, Admin, Owner, Primary Owner) were covered in course 1.11.3. In an audit, check that nobody has more power than their job needs and that the number of Owners is small.
  • Claude's Help Center describes usage analytics for Team and Enterprise plans. On Team plans, Owners and Primary Owners can view them; on Enterprise plans, Owners, Primary Owners and Admins can, but Enterprise Admins cannot see Spend. You find them by clicking your initials in the lower-left corner and choosing Analytics.
  • The analytics page has product tabs (Chat, Claude Code, Claude Design, Cowork, Surveys) and sections that include Who's using Claude? (active members and assigned seats), How are they using Claude? (adoption level, Skills, Connectors) and Results.
  • Use these views as evidence in your audit: are seats used, are skills and connectors used, are shared Projects used?
  • Audit areas to check, from course 1.11.3: members and roles; shared Projects and their permissions; skills (who can publish, who reviewed them); connectors (who added them, which tools are on Always allow, Needs approval or Blocked); memory and data settings.
  • An audit report should have: scope, date, evidence, findings with a risk level (high, medium, low), and one next action per finding with an owner.
  • An audit only reads. Do not change settings during the audit; report first and let the owner decide. This avoids breaking someone's work by accident.
Finding levelExampleWhat to do
HighA former colleague is still a memberReport at once to an Owner
MediumA connector has write tools on Always allowRecommend Needs approval
LowA shared Project has no owner name in its instructionsAdd to the next review
Step by step
  1. Write the scope: which team, which Claude plan, which date.
  2. Ask the Owner for the member list and the settings screens you are allowed to see, or ask them to share their screen.
  3. Open Organization settings > Members and check each person is still on the team and has the right role.
  4. Open the connectors page and write down each connector, who added it and its tool permissions.
  5. Open Analytics if you have access and note active members versus assigned seats, and the skills and connectors in use.
  6. Open two shared Projects and check instructions, knowledge and who can edit.
  7. Write each finding with a level (high, medium, low) and the evidence you saw.
  8. Write one recommended action per finding with a suggested owner.
  9. Check: every finding has evidence, a level and an owner, and you changed nothing.
Watch on YouTube
Building secure agents for knowledge workClaude · YouTube · youtube.com

Videos by other creators on YouTube, for reference. They are not made by or affiliated with The Future Market.

LESSON 01Audit a team's Claude setup
LESSON 01 / ANIMATED LESSON / AI VOICE00:00 / 01:00
Read the video script
[Host] "An inspector walks the house with a checklist and writes it all down. Do that with a team's Claude."
[Text on screen: Members, Projects, Skills, Connectors, Privacy] "Check five areas: people, shared Projects, skills, connectors and privacy settings."
[Screen: Analytics page] "Owners can open Analytics from their initials to see who is active and which skills and connectors are used."
[Host] "Rate each finding high, medium or low, give it an owner, and change nothing during the audit."
Try it now

Audit one real or practice setup. Produce a one-page report with at least five findings, each with a level, evidence and an owner.

ClaudeStuck? Copy a ready-made prompt for Claude

Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.

For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.

I'm learning "Claude Practitioner: design, teach and audit Claude workflows" on The Future Market. Lesson 1: "Audit a team's Claude setup".

What the lesson teaches:
- Before this course: Claude for Teams (course 1.11.3). That course built the setup; this lesson inspects it.
- An audit compares what is written (rules, roles, standards) with what is really set up (settings, members, connectors, skills). The gaps are your findings.
- Roles (Member, Admin, Owner, Primary Owner) were covered in course 1.11.3. In an audit, check that nobody has more power than their job needs and that the number of Owners is small.
- Claude's Help Center describes usage analytics for Team and Enterprise plans. On Team plans, Owners and Primary Owners can view them; on Enterprise plans, Owners, Primary Owners and Admins can, but Enterprise Admins cannot see Spend. You find them by clicking your initials in the lower-left corner and choosing Analytics.
- The analytics page has product tabs (Chat, Claude Code, Claude Design, Cowork, Surveys) and sections that include Who's using Claude? (active members and assigned seats), How are they using Claude? (adoption level, Skills, Connectors) and Results.
- Use these views as evidence in your audit: are seats used, are skills and connectors used, are shared Projects used?
- Audit areas to check, from course 1.11.3: members and roles; shared Projects and their permissions; skills (who can publish, who reviewed them); connectors (who added them, which tools are on Always allow, Needs approval or Blocked); memory and data settings.

The exercise I'm working on:
Audit one real or practice setup. Produce a one-page report with at least five findings, each with a level, evidence and an owner.

I'm stuck. Please:
1. Explain the main idea in plain, simple words with one everyday example.
2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step.
3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.
I'm a parent helping my child (about 8 years old) with a lesson called "Audit a team's Claude setup" from the course "Claude Practitioner: design, teach and audit Claude workflows".

Here's what the lesson says:
A good inspector walks through a house with a checklist, looks at everything, and writes down what is fine, what is broken and what is never used. You do the same for a team's Claude: look, record, and then suggest fixes.

The activity:
Audit one real or practice setup. Produce a one-page report with at least five findings, each with a level, evidence and an owner.

Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words.
Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.
Open Claude
Sources
My notes
02

Test a workflow: success criteria and a test set

This lesson is part of full access: every course and every level for one payment.

03

Risk review: wrong answers, injection and high-risk uses

This lesson is part of full access: every course and every level for one payment.

04

Teach with a framework: the 4Ds of AI Fluency

This lesson is part of full access: every course and every level for one payment.

05

Build a short training programme

This lesson is part of full access: every course and every level for one payment.

06

Write a governance plan

This lesson is part of full access: every course and every level for one payment.

07

Measure results and report honestly

This lesson is part of full access: every course and every level for one payment.

++

Final project

This lesson is part of full access: every course and every level for one payment.

??

Quiz

  1. Which roles can view usage analytics on a Team plan?

  2. During an audit, should you change settings?

  3. Name the four properties of good success criteria in Anthropic's guide.

  4. When a model grades outputs, what does the guide suggest where possible?

  5. Do anti-hallucination techniques eliminate wrong answers?

  6. What is indirect prompt injection?

  7. What does the Usage Policy ask for in high-risk areas such as legal, medical, finance or employment?

  8. What are the 4Ds?

  9. Why start with a baseline?

  10. Who can create surveys, and on which plans?

  11. Are survey responses anonymous to admins?

  12. Why must a governance rule be specific and checkable?

EX

Final exam

This lesson is part of full access: every course and every level for one payment.

CE

Certificate

This lesson is part of full access: every course and every level for one payment.