Audit a team's Claude setup
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.
- 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 level | Example | What to do |
|---|---|---|
| High | A former colleague is still a member | Report at once to an Owner |
| Medium | A connector has write tools on Always allow | Recommend Needs approval |
| Low | A shared Project has no owner name in its instructions | Add to the next review |
- Write the scope: which team, which Claude plan, which date.
- Ask the Owner for the member list and the settings screens you are allowed to see, or ask them to share their screen.
- Open Organization settings > Members and check each person is still on the team and has the right role.
- Open the connectors page and write down each connector, who added it and its tool permissions.
- Open Analytics if you have access and note active members versus assigned seats, and the skills and connectors in use.
- Open two shared Projects and check instructions, knowledge and who can edit.
- Write each finding with a level (high, medium, low) and the evidence you saw.
- Write one recommended action per finding with a suggested owner.
- Check: every finding has evidence, a level and an owner, and you changed nothing.
Videos by other creators on YouTube, for reference. They are not made by or affiliated with The Future Market.
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."
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.
Sources
- Claude Help Center, View usage analytics for Team and Enterprise plans: support.claude.com/en/articles/12883420-view-usage-analytics-for-team-
- Claude Help Center, Roles and permissions: support.claude.com/en/articles/9267276-roles-and-permissions
- Claude Help Center, Use connectors to extend Claude's capabilities: support.claude.com/en/articles/11176164-use-connectors-to-extend-claud
Test a workflow: success criteria and a test set
This lesson is part of full access: every course and every level for one payment.
Risk review: wrong answers, injection and high-risk uses
This lesson is part of full access: every course and every level for one payment.
Teach with a framework: the 4Ds of AI Fluency
This lesson is part of full access: every course and every level for one payment.
Build a short training programme
This lesson is part of full access: every course and every level for one payment.
Write a governance plan
This lesson is part of full access: every course and every level for one payment.
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
Which roles can view usage analytics on a Team plan?
Owners and Primary Owners.
During an audit, should you change settings?
No, report first and let the owner decide.
Name the four properties of good success criteria in Anthropic's guide.
Specific, measurable, achievable, relevant.
When a model grades outputs, what does the guide suggest where possible?
Use a different model from the one that wrote the output.
Do anti-hallucination techniques eliminate wrong answers?
No, they reduce them; critical information must still be validated.
What is indirect prompt injection?
Hidden instructions in third-party content Claude reads, such as emails, web pages or tool results.
What does the Usage Policy ask for in high-risk areas such as legal, medical, finance or employment?
Meaningful review by a qualified person, and clear notice that AI was used.
What are the 4Ds?
Delegation, Description, Discernment, Diligence.
Why start with a baseline?
So you can show what changed after the workflow.
Who can create surveys, and on which plans?
Primary Owners, Owners and Admins, on Enterprise plans only.
Are survey responses anonymous to admins?
No, the CSV export includes each respondent's email, group and surface.
Why must a governance rule be specific and checkable?
A vague rule cannot be followed or audited.
Final exam
This lesson is part of full access: every course and every level for one payment.
Certificate
This lesson is part of full access: every course and every level for one payment.