27-lesson course · about 9 hours
Set up Meta's Muse safely and hand it your weekly legal prep work
For Attorneys, paralegals and in-house legal teams
Everything for Legal teamsA hands-on course for attorneys, paralegals and in-house teams. Give Muse the least access that works, then run four standing tasks that cite their sources, keep client data out and stop for your approval.
What you’ll be able to do
By the end, you can…
How it works
A tutor that meets you where you are
- Lessons that adjust to your levelEach of the 27 lessons is a tutorial you follow with Muse open. It covers the goal, what you need before you start, numbered steps, prompts you can copy, a legal worked example, a checkpoint, and what to do if a step fails. The lessons adapt to where you start, whether you've only used a chat tool or have already tried Muse.
- An AI tutor you can ask anythingWhen a setting looks different on your screen or a prompt returns something odd, ask the tutor. You can type your question or say it out loud, and it answers for your situation.
- Quizzes and flashcards for every lessonShort quizzes and flashcards go with each lesson. They cover the settings, approval choices and review steps that are easy to forget a month later.
- Progress tracking and a certificateYour progress through the 10 modules is saved, so you can work in short sessions at your desk. When you finish, you get a certificate of completion.
Curriculum
The curriculum
The course has 27 lessons in 10 modules, about 9 hours in total. The first modules cover whether Muse fits your work and how to set it up safely. The middle modules take one standing task each, and the course ends with practice on a fictional matter and a weekly review routine.
Module 1Is Muse Right for This Work?3 lessons
1What Muse Is and Who Can Use It
- Distinguish Muse from Meta AI, the Muse Spark model and unrelated products named Muse
- Confirm whether you are eligible to use Muse by country, age and device
- Choose a plan (Free, Power or Maximum) that fits a small set of standing tasks
2Meta's Terms, Data Access and Incidents Since Launch
- Identify the clauses in Meta's terms that limit Muse's use in legal work
- Explain to a colleague who at Meta can see Muse data and what training-by-default means
- Name the setting choices that each public incident points to
3The Fit Test: Does This Task Belong in Muse?
- Sort candidate tasks into 'allowed in Muse', 'not in Muse' and 'ask the approver'
- Write a one-page fit note that records your firm's approval and the default no-client-data rule
- Explain why privilege, discovery, filings, client advice and deadlines stay outside Muse
Module 2Safe-Start Setup4 lessons
4Create a Separate Muse Account
- Create a Muse account that isn't linked to your personal Meta accounts
- Name your agent and set its avatar during onboarding
- Check that no Facebook, Instagram or Threads profile is connected
5Turn Off Training and Set Permissions to Always Ask
- Turn off Help improve our AI models and confirm the change
- Set both the connector and web-access defaults to Always ask
- Set approvals for Artifacts and scheduled tasks under Manage permissions
6Answer Approvals: Allow Once, Deny, See Task Details
- Read an approval card with See task details before deciding
- Choose between Allow once, Allow for this task, Allow for this site and Deny for a given request
- Explain to a colleague why Always allow is off-limits in legal work
7Memory and Side Chats Without Client Information
- Write a memory brief that contains role and jurisdiction facts but no client information
- Inspect and edit Memory.md under Identity > Memory
- Set up one side chat per standing task
Module 3Connect Only What a Task Needs3 lessons
8Web Access and an Allowed-Websites List
- Draft a list of permitted sources for one practice area and jurisdiction
- Approve sites one at a time and review them under Allowed websites
- Revoke a site that falls outside the list
9Retrieval-Only Connectors, One at a Time
- Decide whether a standing task needs any connector at all
- Connect a single approved service with retrieval only
- Ask Muse what a connector can do and confirm it on the permission screen
10What Never to Connect in Legal Work
- List the systems and settings that stay disconnected and give the reason for each
- Set Mac permissions so client files are out of reach
- Explain why payments, custom connectors and shared Artifacts stay off
Module 4A Prompt Pattern for Legal Standing Tasks3 lessons
11Role, Jurisdiction, Sources and Deliverable
- Write a prompt that states role, jurisdiction, permitted sources and deliverable format
- Turn a vague request into a goal-style task
- Specify table columns, length and audience for a deliverable
12Stop Points, [CHECK] and Facts Versus Allegations
- Add explicit stop points before anything is sent, booked, bought or published
- Require [CHECK] on anything Muse couldn't confirm at the primary source
- Write instructions that keep facts, allegations and open questions in separate columns
13Scheduling a Standing Task and Running a First Read-Only Test
- Schedule a recurring task with day, time and time zone
- Confirm and edit the schedule under Upcoming
- Set per-task approvals under Artifacts and scheduled tasks
Module 5Workflow: Weekly Public Legal-Update Digest2 lessons
14Build and Schedule the Digest
- Write a digest prompt that names sources, topic, period and output columns
- Schedule it for a weekly run and confirm it under Upcoming
- Ask for a plain-English follow-up on a single item
15Verify Every Item at the Primary Source
- Verify each digest item by opening and reading the cited primary source
- Clear or keep [CHECK] tags and record what you verified
- Spot invented, misdated or misattributed items
Module 6Workflow: CLE and Bar-Admin Tracker2 lessons
16Build the CLE Tracker Artifact
- Create a tracker Artifact with credits needed, earned, deadline and program columns
- Check each requirement against the bar or CLE regulator's website
- Keep the Artifact private and unshared
17Program Searches That Stop Before Payment
- Write a program search prompt with topic, place, date and price limit
- Deny any registration or payment approval card
- Add chosen programs to the tracker by hand-approved edits
Module 7Workflow: Client-Data-Free Templates and Clause Comparisons2 lessons
18Intake Checklists and Templates Without Client Data
- Draft a generic intake checklist with conflict-check fields and no real data
- Flag jurisdiction-dependent items as [CHECK]
- Route the draft to the responsible attorney for approval
19Comparison Tables of Public Sample Clauses
- Produce a difference table from two pasted public sample clauses
- Check every row against the pasted text
- Write drafting notes from the reviewed table for the attorney to approve
Module 8Workflow: Client Alerts, Bios and Hearing Logistics3 lessons
20Client Alerts With a Verification List
- Draft a client alert that cites primary sources and avoids specific advice
- Work through every item on the verification list
- Spot statements that could read as promises of results
21Rewrite in Your Own Words and Get Attorney Approval
- Rewrite a Muse draft in the lawyer's own voice
- Draft a bio that adds no credentials, results or awards
- Run a release chain that ends with recorded attorney approval
22Hearing and Travel Logistics Without Confidential Details
- Write a logistics prompt that contains no matter names or confidential details
- Verify entry and security rules on the court's official site
- Deny every booking approval
Module 9Practice: A Fictional Sample Matter3 lessons
23A Source-Linked Facts List
- Assemble a fictional matter file with no real people or clients
- Produce a facts list with a source passage for every fact
- Separate allegations and open questions from established facts
24A Source-Linked Chronology
- Produce a chronology with event IDs, dates, sources and confidence notes
- Add a new document so it updates existing entries instead of restarting the task
- Trace each correction to every place it appears
25A Discrepancy Table and Conflict Queue
- Produce a discrepancy table that lists every conflict between sources
- Queue each conflict for attorney resolution without picking a winner
- Explain why a newer document does not automatically outrank a better-supported one
Module 10The Weekly Review Routine2 lessons
26Weekly Review: Activity Log, Upcoming and Permissions
- Run the weekly review across the Activity log, Upcoming, Allowed websites, Connectors and Memory
- Spot actions, sites or memories that went beyond your instructions
- Record the review in a short log
27Correct, Stop, Export, Disconnect or Reset
- Stop or correct a task that went beyond what you intended
- Export Muse data and disconnect services
- Choose between forgetting, resetting, cancelling and deleting the account
Who it’s for
Made for you if…
Made for: Attorneys, paralegals and in-house legal teams
Paralegals and legal assistants
You repeat the same prep every week: tracking public developments, keeping checklists and templates current, planning court appearances. You want an agent to take on the first pass without going near a client file.
Attorneys in small firms or solo practice
You handle your own CLE, alerts, bios and logistics. You want time back, with settings and review habits that respect your duties of competence, confidentiality and supervision.
In-house legal team members
You watch regulators and courts for the business and maintain internal forms. You need a clear, documented line between what Muse may touch and what stays inside approved systems.
Legal professionals who have used chat AI but not agents
You've typed prompts into a chat tool but never let an agent act for you. You want to learn approvals, permissions and weekly review step by step before trusting it with anything.
Questions
Good to know
Can I put client information into Muse?
No. The course's default position is that Muse is used only for work that is not client work and not privileged. You don't enter client-confidential, privileged or identifying information, and you don't connect firm email, drives, document-management systems, Slack or calendars that hold matters. As of 2026-10-28, Meta can access Muse data when needed to operate the service. Training is on by default, and the Confidential VM is not yet available.
Where is Muse available, and who can use it?
As of 2026-10-28, Meta offers Muse in the US, Canada and Japan, to people who are 18 or older (or the local age of majority). It runs on iPhone, Android, the web at muse.ai and Mac. The course does not cover ways around region, age, plan or terms limits. Availability changes, so check Meta's official pages.
Do I need a paid Muse plan?
Lesson 1 helps you choose. As of 2026-10-28, Meta's help page lists Free (with a usage limit Meta doesn't publish), Power at $20 a month and Maximum at $100 a month. There is no team plan, so each person needs their own account. Prices change, so confirm them on Meta's subscriptions page.
Do I need my firm's approval first?
Yes. Before you start, you should know your firm's or department's AI policy and who approves new tools. Get written approval before you connect any work account. Lesson 3 has you record that approval in a fit note.
Will Muse track my filing deadlines?
No. Your docketing system stays the source of truth for deadlines. The CLE tracker in this course covers your own CLE and bar-admin reminders, not matter deadlines.
Does the course cover Westlaw, Lexis+ AI, CoCounsel or Harvey?
No. Dedicated legal research platforms, and checking authority inside them, are outside this course. Here you check each item by opening the primary source Muse cites, and an attorney approves anything before it is used.
Are voice mode, the Muse email address or phone calls covered?
No. As of 2026-10-28, those features had been announced but not confirmed as available, so the course doesn't teach them. It also leaves out payments, wallet cards, custom connectors and sharing Artifacts that contain confidential material.
What equipment do I need?
An iPhone, Android phone, web browser or Mac where you can install or open Muse. You also need an email address that isn't tied to an existing Meta account, so your Muse account stays separate. Meta updates the app often, so your screens may look a little different from the lessons. The lessons point out where that's likely.