Team and Attribution

← Back to Features

In a shared vault, TaskNotes maps each device to a person note so tasks are automatically attributed, assignees can be picked from a list, and notifications filter to show only your work. Everything runs inside Obsidian — no external server or account system. Person and group identities are regular Markdown files in your vault.

flowchart TB
    subgraph VAULT["Shared Vault (synced via Obsidian Sync, iCloud, git, etc.)"]
        direction TB

        subgraph PEOPLE["Person & Group Notes (User-DB/)"]
            P1["Alice Chen
type: person"]
            P2["Bob Rivera
type: person"]
            G1["Platform Team
type: group
members: Alice, Bob"]
        end

        subgraph TASKS["Task Notes"]
            T1["Review report
creator: Alice
assignee: Platform Team"]
            T2["Fix bug
creator: Bob
assignee: Alice"]
        end
    end

    subgraph DEV1["Alice's Laptop"]
        U1["UUID: a3f8...
(localStorage — never synced)"]
    end

    subgraph DEV2["Bob's iPad"]
        U2["UUID: 7c2b...
(localStorage — never synced)"]
    end

    U1 -. "registered to" .-> P1
    U2 -. "registered to" .-> P2
    P1 -- "member of" --> G1
    P2 -- "member of" --> G1
    P1 -. "auto-set creator" .-> T2
    P2 -. "auto-set creator" .-> T1
    G1 -. "assignee resolves to
Alice + Bob" .-> T1

    style VAULT fill:#1a1a2e,stroke:#555,color:#ccc
    style DEV1 fill:#2a2a2a,stroke:#888,color:#ccc
    style DEV2 fill:#2a2a2a,stroke:#888,color:#ccc
    style PEOPLE fill:#1a2e1a,stroke:#3a9a5c,color:#ccc
    style TASKS fill:#1a2233,stroke:#4a86c8,color:#ccc
    style U1 fill:#332a1a,stroke:#c87a2a,color:#ccc
    style U2 fill:#332a1a,stroke:#c87a2a,color:#ccc
    style P1 fill:#1a2e1a,stroke:#3a9a5c,color:#ccc
    style P2 fill:#1a2e1a,stroke:#3a9a5c,color:#ccc
    style G1 fill:#1a2e1a,stroke:#3a9a5c,color:#ccc
    style T1 fill:#1a2233,stroke:#4a86c8,color:#ccc
    style T2 fill:#1a2233,stroke:#4a86c8,color:#ccc

How it works in three steps:

1. Register once — each device gets a UUID stored in localStorage. You map it to your person note in Settings → Team & Attribution.
2. Create tasks normally — TaskNotes auto-fills the creator field with your person note. Assign tasks to people or groups via the picker.
3. Notifications filter automatically — enable "Only notify for my tasks" and you only see notifications for tasks assigned to you (or a group you belong to).

Device Identity

Every device that opens the vault gets a unique UUID stored in localStorage:

• Not synced — Obsidian Sync, iCloud, and git do not touch localStorage
• Persists across Obsidian restarts

TaskNotes also detects a human-readable device name from the platform (e.g., "Windows PC", "Mac", "iPhone"). You can set a custom name in settings.

Person Notes

A person note is a Markdown file with type: person in its frontmatter:

---
type: person
title: Alice Chen
role: Engineer
department: Platform
availableFrom: "09:00"
availableUntil: "17:00"
---

TaskNotes discovers person notes by scanning a folder you configure (e.g., User-DB/). You can also add a tag filter if you want to be more selective.

Group Notes

Groups are notes with type: group and a members array of wikilinks:

---
type: group
title: Platform Team
members:
  - "[[Alice Chen]]"
  - "[[Bob Rivera]]"
  - "[[DevOps Team]]"
---

Groups can nest — DevOps Team above could be another group with its own members. TaskNotes resolves nested groups recursively (up to 10 levels deep) and detects cycles.

flowchart LR
    G1["Platform Team"] --> P1["Alice Chen"]
    G1 --> P2["Bob Rivera"]
    G1 --> G2["DevOps Team"]
    G2 --> P3["Carol Kim"]
    G2 --> P4["Dave Park"]

    style G1 fill:#1a2e1a,stroke:#3a9a5c,color:#ccc
    style G2 fill:#1a2e1a,stroke:#3a9a5c,color:#ccc
    style P1 fill:#2a2a2a,stroke:#888,color:#ccc
    style P2 fill:#2a2a2a,stroke:#888,color:#ccc
    style P3 fill:#2a2a2a,stroke:#888,color:#ccc
    style P4 fill:#2a2a2a,stroke:#888,color:#ccc

Groups appear in the person/group picker when assigning tasks, in notification filtering (if you are a member of an assigned group, you get notified), and in the discovery panel in settings.

Creator and Assignee

TaskNotes uses two frontmatter fields for attribution:

Both are stored as wikilinks (e.g., [[Alice Chen]]). The assignee field can hold a single person, a group, or an array of multiple assignees.

Person/group picker: Task modals and the bulk tasking action bar include a picker that shows all discovered persons and groups. Start typing to filter, or scroll through the list. Groups show their member count.

Assignee-Aware Notifications

When "Only notify for my tasks" is enabled, the notification system checks each task before showing it. See also Reminders for per-task and global reminder configuration, and View Notifications for query-based alerts.

flowchart LR
    N["Notification
triggered"] --> L["Look up
device → person"]
    L --> C{"Assignee
includes me?"}
    C -- "Yes (direct or via group)" --> S["Show
notification"]
    C -- "No" --> F["Filter out
silently"]

    style N fill:#332a1a,stroke:#c87a2a,color:#ccc
    style L fill:#2a2a2a,stroke:#888,color:#ccc
    style C fill:#1a2233,stroke:#4a86c8,color:#ccc
    style S fill:#1a2e1a,stroke:#3a9a5c,color:#ccc
    style F fill:#2a1a1a,stroke:#c84a4a,color:#ccc

If the assignee is a group, TaskNotes resolves it to all member persons recursively. You only see notifications for tasks assigned to you or to a group you belong to.

This setting is per-device — each person can independently choose whether to filter or see everything.

Settings

These settings are in Settings > Team & Attribution:

Person notes:

Group notes:

Attribution:

Notification filtering:

Related

• View Notifications for the notification system that supports assignee filtering
• Reminders for per-task reminders
• Custom Properties for adding fields like assignee to task modals