Give Meta's Muse your recurring project work and keep the decisions yourself

Module 1Decide Whether Muse Fits Your Work3 lessons

1. 1What Muse Is and Is Not

   • Distinguish Muse from the Meta AI app and from Muse Spark
   • Describe three things Muse can do that a single-exchange chat assistant cannot
   • Identify which announced features are not yet available to teach or use
2. 2Access, Plans and Usage Limits as of October 2026

   • Check your own eligibility against the official age and country rules
   • Choose between the Free, Power and Maximum plans for a project workload
   • Spot third-party pricing and token claims that conflict with Meta's help pages
3. 3Terms, Incidents and Your Firm's Rules: A Go/No-Go Check

   • List the Muse prohibited uses that apply to professional work
   • Explain what each dated incident teaches about settings and oversight
   • Write a one-page go/no-go note covering policy, client NDAs and IT approval

Module 2Safe-Start Setup4 lessons

1. 4Create a Separate Account and Turn Off Training

   • Create a Muse account with an email that isn't linked to other Meta accounts
   • Turn off Help improve our AI models and confirm the change
   • Name the agent neutrally, with no client or employer names
2. 5Set Permissions to Always Ask

   • Set Connectors and Web access defaults to Always ask
   • Explain the difference between Ask for some actions and Always ask
   • Locate Manage permissions, Artifacts and scheduled tasks, and Allowed websites
3. 6Answer Approval Cards Safely

   • Use See task details to check what Muse intends before approving
   • Choose Allow once or Deny for each request
   • Explain how Always allow and broad grants contributed to the Marketplace incident
4. 7Give Muse Your Role and Keep Projects Apart

   • Write a role briefing for the main chat that leaves out confidential details
   • Review and edit entries under Identity > Memory
   • Create a side chat for the sample project with a codename

Module 3Connect Only What the Work Needs3 lessons

1. 8Choose Connectors and Know What Never to Connect

   • Choose the minimum set of connectors for the sample project
   • List the data and accounts that must not be connected in professional work
   • Write a connector request to send to IT for approval
2. 9Connect One Read-Only Service

   • Connect one service through Settings > Connectors
   • Set retrieval-only access where it is offered
   • Disconnect a service and ask Muse to forget what it read
3. 10Run a First Low-Risk Task and Read the Activity Log

   • Run a read-only task without anything being created or changed
   • Find the task in Activity log and match it to your request
   • Explain what can and cannot be undone

Module 4From One-Line Request to Sourced Brief4 lessons

1. 11Unpack the One-Line Request

   • Separate the stated request from unstated assumptions
   • Identify who acts on the answer and what decision it supports
   • Write questions for the requester instead of guessing
2. 12Write the Brief and Its Acceptance Criteria

   • Write a brief with audience, purpose, deliverables, exclusions and acceptance criteria
   • Turn the job's gates into testable acceptance criteria
   • Save the brief as an Artifact with a neutral title
3. 13Build a Sourced Evidence Summary

   • Write a prompt that requires a source for every claim
   • Mark disputed, missing and unverified figures with [CHECK]
   • Spot-check claims against the original documents
4. 14Compare Options and Keep the Recommendation Yours

   • Produce an options table with effort, dependencies and marked estimates
   • Write a recommendation that asks for a decision without claiming approval
   • Turn the brief into a slide outline with no client names

Module 5Meeting Notes to Action Register3 lessons

1. 15Extract Decisions, Actions, Owners and Dates

   • Produce an action register table from meeting notes
   • Separate decisions, actions and unresolved questions
   • Check every row against the source notes
2. 16Flag Inferred Owners and Dates as Unconfirmed

   • Require a confirmed or unconfirmed status for every owner and date
   • Spot an action with no owner and route it to yourself
   • Write the confirmation questions to raise
3. 17Hold Follow-Ups and Writes for Approval

   • Draft a follow-up email without sending it
   • Approve the exact text before Muse writes to Notion or Asana
   • Check Activity log to confirm nothing was sent or written early

Module 6Scheduled Evidence Watch4 lessons

1. 18Brief a Standing Task Like a New Colleague

   • Write a standing-task brief with trigger, sources and escalation
   • State what the task may and may not do
   • Save the brief so you can reuse and revise it
2. 19Schedule the Evidence Watch and Keep the Last Accepted Version

   • Create a scheduled task with day, time and time zone
   • Confirm the task and its approval settings under Upcoming and Permissions
   • Define what counts as a reportable change
3. 20Surface Conflicts Instead of Rewriting

   • Spot an output that merges or resolves a conflict on its own
   • Write a conflict report format with both values and both sources
   • Decide which value to accept and record why
4. 21Spot-Check Reports for Duplicates and Noise

   • Classify each reported item as real, irrelevant, duplicate or wrong
   • Revise the task brief to cut noise
   • Run a repeat-input test

Module 7Status Drafts and Controlled Revisions4 lessons

1. 22Schedule an Action Check and an Unsent Weekly Status Draft

   • Schedule an action check that reports only new slips and ownerless actions
   • Schedule a status draft from approved, read-only sources
   • Check the draft against the action register and evidence watch
   • Shorten it for an executive reader
2. 23Draft a Proposal From Your Own Template

   • Draft a proposal using your own template and approved takeaways
   • Use [PRICE] and [CHECK] placeholders instead of invented figures
   • Rank the assumptions the client or sponsor must confirm
3. 24Revise Only What a Change Touches, With a Change Log

   • Write a revision prompt limited to affected sections
   • Produce and check a change log
   • Spot quiet scope growth or a dropped requirement
4. 25Test a Full Project Week

   • Run a seeded week of changes through the evidence watch, action check and status draft
   • Check that each output reflects the same accepted versions
   • Release the Friday pack yourself after checking it against the acceptance criteria

Module 8Review What Muse Did3 lessons

1. 26Run the Weekly Review Routine

   • Review Activity log, Upcoming, permissions and Allowed websites
   • Revoke sites, permissions or tasks that go beyond what you intended
   • Correct mistakes promptly, including with third parties
2. 27Prune Memory and Don't Trust the Agent's Self-Report

   • Edit or delete Memory entries that hold client or personal details
   • Ask Muse to forget a matter and verify the result
   • Investigate unexpected behaviour using Activity log instead of chat explanations
3. 28Share Artifacts Safely and Leave Cleanly

   • Decide whether an Artifact is safe to share
   • Rename Artifacts and chats to remove client names
   • Export data, reset Muse or cancel the plan in the right order