Andre Guy Carvalho715 downloadsManage your team: people cards with cadence health, 1:1s with agenda buffers, projects with logs, performance observations, and a universal quick capture.
Run your team from Obsidian. Team Manager turns plain markdown notes into a management workspace: a people dashboard with cadence health, 1:1s with an agenda buffer that never loses a thought, recurring meetings that track their own rhythm, projects on a Kanban board, performance observations you jot down as they happen, a calendar that turns events into meeting notes, and one universal quick capture to file any of it in two keystrokes.
Everything is stored as ordinary markdown with YAML frontmatter — no database, no lock-in. Turn the plugin off and your notes are still notes.
team-hub code block; project notes get a team-project block.Settings → Community plugins → Browse → search Team Manager → Install → Enable.
andyguy-dot/obsidian-team-manager.Download main.js, manifest.json and styles.css from the
latest release
into <vault>/.obsidian/plugins/team-manager/, then enable it.
Team Manager reads a calendar over its secret iCal address, so there is no Google Cloud project to create and no OAuth app to approve. In Google Calendar: Settings → pick the calendar → Secret address in iCal format. Paste it into Settings → Team Manager → Calendar. You can add several.
Two things worth knowing:
data.json in plain text like every other
setting. Treat it the way you treat a password.This is the only feature that talks to the network, and it only ever reads.
Guests are matched to your person notes by the email field; the ones it does
not recognize can be created straight from the event, with their address
already filled in.
On first run the plugin creates a Team Manager/ folder with People/,
Meetings/, Performance/ and Projects/ subfolders (all configurable in
settings). Open the dashboard from the ribbon (the people icon) or the command
Open team dashboard, then hit + Person.
A note is recognized only when it has the right type and lives in the
matching folder, so the rest of your vault is left untouched.
Everything is frontmatter on normal notes.
Person — People/Jane Doe.md
---
type: person
role: Staff Engineer
team: Platform
status: active
relation: team # team | peer | manager | other
cadence: 14 # days, or weekly / biweekly / monthly
---
1:1 — Meetings/2026-07-16 Jane Doe.md
---
type: meeting
person: "[[Jane Doe]]"
date: 2026-07-16
---
Project — Projects/Auth migration.md
---
type: project
status: in progress
people:
- "[[Jane Doe]]"
priority: high
---
Performance — Performance/Jane Doe - 2026-H1.md
---
type: performance
person: "[[Jane Doe]]"
period: 2026-H1
rating: Exceeds # free text, not a fixed scale
---
| Command | What it does |
|---|---|
| Open team dashboard | The main view |
| Quick capture | Type-first capture into any destination |
| New person / New 1:1 / New project / New performance note | Create notes |
| Add to next 1:1 | Buffer an agenda item for someone |
| Add project log entry | Timestamped update on a project |
| New recurring meeting | Create a series (standup, weekly) |
| New session of a recurring meeting | Hold the next one, with its regulars and buffer |
| Insert hub block in this note | Add the live dashboard to a person/project/series note |
| Create folder structure | (Re)create the configured folders |
Bind Quick capture to a hotkey (Settings → Hotkeys) for two-keystroke capture from anywhere in Obsidian.
Team Manager loads on mobile and quick capture, browsing, the calendar and the hubs all work. Drag-and-drop on the Kanban and right-click menus (delete, status change) are desktop-only, since touch has neither — organize on desktop, capture anywhere.
npm install
npm run dev # watch build
npm run build # type-check + production build
main.js is a build artifact and is git-ignored; releases are produced by the
GitHub Actions workflow when a version tag is pushed.
MIT © André