Skip to main content
Notes in mpath let you capture context, documentation, and supporting materials. You can attach notes to entities (initiatives, tasks, meetings, people) or create standalone notes that exist independently.
Notes are flexible documentation tools that help you:
  • Capture meeting minutes and decisions
  • Document context for initiatives and tasks
  • Create standalone documentation
  • Share information with team members
  • Attach files and images

​
Overview

mpath supports two types of notes:

Entity Notes

Notes attached to specific entities like initiatives, tasks, meetings, or people. They provide context for that entity.

Standalone Notes

Independent notes with titles that exist on their own. Perfect for documentation, wikis, or general knowledge.

​
Key Features

Notes support rich text editing with:
  • Markdown support - Format text with headers, lists, links, and more
  • Inline images - Upload and embed images directly in note content
  • File attachments - Attach multiple files (PDFs, documents, images)
  • Timestamps - Automatic creation and update timestamps
Control who can see your notes:
  • Private - Only you can see the note
  • Shared with specific people - Share with selected team members
  • Shared with everyone - Make the note visible to all organization members
Entity notes inherit permissions from the entity they’re attached to. Standalone notes have their own sharing settings.
All notes are scoped to your organization:
  • You can only see notes from your organization
  • Notes are automatically filtered by organization membership
  • Complete privacy between different organizations

​
Entity Notes

Entity notes are attached to specific entities in mpath:

​
Where You’ll Find Entity Notes

  • Initiatives - Document decisions, context, and progress
  • Tasks - Capture requirements, blockers, or updates
  • Meetings - Record meeting minutes and action items
  • People - Keep notes about performance, growth, or context
  • Teams - Document team processes and decisions

​
Creating Entity Notes

  1. Navigate to the entity detail page (e.g., an initiative)
  2. Find the Notes section
  3. Click Add Note or New Note
  4. Enter your note content (supports markdown)
  5. Optionally attach files or embed images
  6. Save the note
Use entity notes to keep all context in one place. Instead of scattered docs, attach notes directly to the work they relate to.

​
Editing Entity Notes

  • Click on any note to edit it
  • Make your changes
  • Save to update the note
  • The note will show when it was last updated
Only the note creator or organization admins can edit notes. Make sure to capture important information correctly the first time.

​
Standalone Notes

Standalone notes are independent notes with titles that exist on their own. They’re perfect for:
  • Documentation and wikis
  • General knowledge articles
  • Process documentation
  • Team guides and resources

​
Creating Standalone Notes

  1. Navigate to Notes from the main navigation (or use the command palette)
  2. Click New Note
  3. Enter a title for your note
  4. Add your content (supports markdown and inline images)
  5. Optionally attach files
  6. Configure sharing settings:
    • Keep it private (only you)
    • Share with specific people
    • Share with everyone in the organization
  7. Save the note
Standalone notes have titles, making them easy to find and organize. Use descriptive titles to make notes searchable.

​
Viewing Standalone Notes

Access your standalone notes:
  • Go to Notes from the main navigation
  • See all notes you have access to
  • Filter by:
    • Notes you created
    • Notes shared with you
    • Notes shared with everyone

​
Sharing Standalone Notes

Control who can see your standalone notes: Private (default):
  • Only you can see the note
  • Perfect for personal documentation or drafts
Shared with specific people:
  • Select team members who can view the note
  • Useful for team-specific documentation
Shared with everyone:
  • All organization members can see the note
  • Great for public documentation, wikis, or team resources
Use “shared with everyone” for documentation that should be accessible to the whole organization, like onboarding guides or process documentation.

​
Inline Images

You can embed images directly in note content:

​
Uploading Images

  1. While editing a note, click the image button in the toolbar
  2. Or paste an image from your clipboard
  3. Or drag and drop an image into the editor
  4. The image will be uploaded and embedded in the note
Images are stored securely and are only accessible to people who can view the note. They’re organized by note for proper access control.

​
Image Best Practices

  • Use images to illustrate processes or concepts
  • Keep images reasonably sized for fast loading
  • Use descriptive alt text for accessibility
  • Consider image placement for readability

​
File Attachments

Attach files to notes to provide supporting materials:

​
Supported File Types

  • Images - PNG, JPG, GIF, WebP
  • Documents - PDF, DOC, DOCX
  • Text files - TXT, MD
  • Other - Most common file types

​
Attaching Files

  1. While creating or editing a note
  2. Click Attach Files or drag and drop files
  3. Select one or more files
  4. Files will be uploaded and attached to the note
Files have size limits (typically 50MB per file). If you need to share larger files, consider using external storage and linking to it in the note.

​
Viewing Attachments

  • Attached files appear at the bottom of the note
  • Click to download or view the file
  • Files are organized by upload date

​
Best Practices

Use entity notes for context
Attach notes directly to initiatives, tasks, or meetings to keep context where it’s needed. This makes information easy to find.
  • Use standalone notes for documentation
    Create standalone notes for wikis, guides, or general knowledge that doesn’t belong to a specific entity.
  • Keep notes focused
    Each note should cover a single topic or decision. This makes notes easier to find and maintain.
  • Use descriptive titles
    For standalone notes, use clear, descriptive titles that make them easy to find and understand.
  • Share appropriately
    Use sharing settings to control access. Private notes for personal use, shared notes for team documentation.
  • Update notes regularly
    Keep notes current. Outdated documentation can be worse than no documentation.
  • Link related notes
    Use markdown links to connect related notes and create a knowledge network.

​
Real-World Examples

Entity Note on an Initiative:
  • Document key decisions made during planning
  • Capture stakeholder feedback
  • Record progress updates and blockers
  • Attach relevant documents or screenshots
This keeps all initiative context in one place, making it easy for stakeholders to understand status and decisions.
Standalone Note: “Code Review Process”:
  • Title: “Engineering Code Review Process”
  • Content: Step-by-step guide with screenshots
  • Shared with: Everyone in Engineering team
  • Attachments: Review checklist PDF
This creates a reusable resource that team members can reference anytime.
Entity Note on a Meeting:
  • Record discussion points
  • Document decisions made
  • List action items with owners
  • Attach relevant documents
This ensures meeting outcomes are captured and accessible to all participants.
Standalone Note: “My Development Goals”:
  • Title: “Q1 2024 Development Goals”
  • Content: Personal goals and progress tracking
  • Shared with: Private (only you)
This creates a personal space for tracking your own development and goals.

Initiatives

Learn how to use notes to document initiative context and decisions.

Tasks

See how notes help capture task requirements and updates.

Meetings

Understand how notes are used for meeting minutes and documentation.

People

Learn how notes can provide context about team members.