📥 My Work

My Work answers one question: what actually needs me today? Everything waiting on you across the whole platform is gathered into a single list, so you never have to check each module in turn and hope you have not missed one.

The attention counter

The badge in the header reads immediate / total — how many items need action now, out of everything not yet finished. When it clears, you are genuinely up to date. The sidebar carries the same count.

What appears here

Awaiting your review, your submissions due, returned to you, your open action items, and meetings needing attention. Sections only appear when they have something in them, so an empty queue really does look empty rather than showing five headings with nothing under them. Every row links straight to the screen where you can deal with it, and the item drops off the list once it is done.

Long queues

Each section shows the most relevant handful of items while its summary tile counts the whole queue. Where the two differ you see a Showing 5 of 23 note, so a long list is never silently truncated into looking complete. The action-item and meeting sections link out to their full screens.

My Action Items

The action-item side has its own screen at My Action Items, with four ways to look at the same list — a compact list, a sortable table, a due-date calendar, and a board grouped by status. It is covered in full under Meeting Notes AI.

📈 Ups & Downs

The Ups & Downs module is a structured cycle review workflow. Each project has a recurring cycle (weekly, bi-weekly, or monthly) during which Project Leads submit account-level highlights (Ups) and risks (Downs).

Approval chain

Submissions travel up a fixed 6-level chain: PL → PM → Delivery SPOC → Sales SPOC → POD Owner → Cluster Head. Each reviewer can approve and forward, or return with a comment.

The advantage over a status report is that you write it once. A risk a team raises on Monday becomes visible to cluster leadership without anyone building a deck for it, and if something needs rework a reviewer returns it with a comment attached rather than starting an email thread.

Your role in this workflow

• 📈 Project Lead — you start each cycle: compose your Ups & Downs and Submit for Review, or Save Draft to continue later. You cannot edit after submitting — ask your PM to return the cycle if you need a change.
• ✅ Project Manager — review your PLs’ submissions, optionally add your own items (labelled “Added by Project Manager”), then Approve (forwards to the Delivery SPOC) or Return (back to the PL with your comment).
• 🚚 Delivery SPOC — second-level review. Approve forwards to the Sales SPOC; Return sends it back one level, to the PM’s queue.
• 🤝 Sales SPOC — review after the Delivery SPOC, adding client / commercial context. Approve forwards to the POD Owner.
• 📦 POD Owner — review cycles across every project in your POD; Approve forwards to the Cluster Head.
• 🏛️ Cluster Head — final approval. Approving marks the cycle Cluster Head Approved (closed). You also see the full Review Chain Summary.
• 👁️ PMO Observer — read-only oversight across all projects and cycles, with no approval actions.

Next-cycle pre-planning

A Next Cycle tab lets a Project Lead start drafting the following cycle before the current one closes, so nothing is lost between windows.

Cycle History

Cycle History browses every closed cycle for any project you have access to, and opening one gives a read-only detail view with the full item list and the activity trail — which is what makes the archive worth keeping.

🎯 Priorities & Achievements

The P&A module captures weekly priorities and achievements for each project lead (and contributors), an AiDE adoption entry, and travels through a bilateral review chain.

Submitting your weekly P&A

Open Priorities & Achievements from the sidebar — the current active week is pre-selected, and if no week is open a message tells you when the next one does. Click + Add Priority, type it in the rich text editor, and choose a category. Achievements are added the same way against the previous week.

Reviewing your team’s P&A

As a reviewer (PM, Delivery SPOC, Sales SPOC, POD Owner or Cluster Head) the same screen shows a team-level view with one card per submitter. Click a name to expand their submission; the card carries the submission time, the categories, and your approve / return controls.

Cluster Head weekly digest

Cluster Heads see P&A Digest in the sidebar instead of the standard review screen — every submission from every team member in one consolidated view, grouped by project and role. Acknowledge records that you have read the week.

P&A History

P&A History reviews any past week: pick a week from the selector and browse every submission, its categories and its approval status. PMO Associates can view submissions from all team members.

Approval chain

The P&A chain follows the reporting graph, not the role ladder. Your direct manager is always the first reviewer, and the chain then steps up the reporting hierarchy to Cluster Head level. Empty rungs are skipped automatically — if your manager is a Delivery SPOC with no PM in between, the chain simply goes straight there.

🗓️ Project Timeline

The Project Timeline is a shared, per-project running log where any team member can post events (milestones, blockers, announcements), note revisions, and capture items directly into Ups & Downs or P&A drafts.

Who can see what

Event visibility is controlled by the audience setting: Chain (author + everyone at or above them in the reporting chain) or Everyone (all project participants). PMO Associates always see every event as read-only observers regardless of the setting. The 👁 N can see badge on each event shows how many people that is; hover it for the full roster, sorted by seniority.

Posting an event

Pick the project from the Project dropdown at the top of the content area — only projects you have access to are listed, and the feed reloads when you switch. Compose in the Add an event box, choose a type, optionally back-date it, tick Visible to everyone if it should not follow the chain, and attach files before posting.

Editing an event

If you are the author, or at the same role level or above in the reporting chain, ✎ Edit / add info opens an inline form under the event body. Previous versions are kept, and if the event has drafted captures, editing the body updates the linked Ups & Downs or P&A draft too.

Deleting an event and its notes

Delete soft-deletes the event and takes its notes, revisions and attachments with it — but not the linked draft items in Ups & Downs or P&A, which you must remove separately. A note can be deleted only by the person who wrote it; the event author cannot delete someone else’s note.

Attachments

Every event card carries a file section at the bottom — screenshots, documents, spreadsheets, anything that is supporting evidence — and files can be added to an event that is already posted. Deleting an attachment is permanent, and delete is not restricted to the uploader: any manager above you in the reporting chain can remove one.

Timeline views

The toggle above the feed switches between 🗓️ Timeline — the event stream grouped by day, newest first, with back-dated events sorted by their back-date — and 📋 Activity log, a flat chronological list of every action: who posted, edited or deleted what, and when.

🤝 Meeting Notes AI

Meeting Notes AI turns what a meeting produced into structured minutes. You upload a transcript document, paste the text, or upload the video recording — a recording is transcribed for you first — and AiDE generates the minutes of the meeting, a topic mindmap, and a list of action items with owners and due dates. You then track those actions to closure and share the outcome with participants.

Who can use it

Any ValueLabs employee with a POD Governance account can create meetings. A meeting is visible to its owner, direct participants, and — when you toggle Visible to everyone — every member of the project team.

Connecting your AiDE Fabric Token

AiDE processing requires a personal AiDE Fabric Token (aide_fabric_token_…) obtained from aide.imagine.tech ↗. Enter it once via the Connect AiDE banner on any meeting — it is stored encrypted against your account.

Meeting lifecycle

Action-item reminders

Assignees receive an email three days before an action item is due, again on the due date, and every two days while overdue (the meeting owner is copied on overdue escalations). Reminders can be paused per meeting via the 🔔 toggle on the meeting detail page.

🩺 Project Health

Project Health writes the account summary you would otherwise assemble by hand — reading what a project has already reported over a period, so nobody is asked to report anything twice.

Where the content comes from

Three governed sources you already have access to: Project Timeline events, Meeting Notes AI outcomes, and Priorities & Achievements. Nothing is invented from outside the record, so every point traces back to something you can open and check.

Reading the output

An executive summary with highlights and risks pulled out separately, plus a health score and grade — and the rationale behind that score. The score is produced by AiDE as part of its analysis, not a formula applied afterwards, which is what lets the rationale genuinely explain it.

Sharing and scheduling

Use 📋 Copy to paste it into a message, ✉️ Email to send it, or 📄 PDF to export it for a pack. The scheduled-delivery card turns on automatic weekly or monthly generation for that project, so it arrives without you having to remember. Treat a summary as a strong first draft, not a finished document.

Generating a summary

Only projects you can already see are listed — if the list is empty you are not yet mapped to a project, so ask your administrator. Weekly gives you the detail for a review conversation; monthly steps back for a trend view, which suits a steering committee better than a stand-up. You can also pick a past period.

Access and prerequisites

You need a project assignment and a connected AiDE Fabric Token — the same token that powers Meeting Notes AI processing. If the screen reports a token problem, connect one from My Profile. Summaries also surface as suggestions inside the Ups & Downs and P&A screens.

📊 Reports & Analytics

The Reports screen is available to PMO Associates, Delivery SPOCs, POD Owners, and Cluster Heads. It shows cycle statistics, Priorities & Achievements trends, AiDE adoption, return rates, and notifications delivery metrics.

Filtering — date range, POD & project

A toolbar at the top re-scopes the whole page: 📅 Date range (All time, 7d, 30d, 90d or a custom from/to — the headline “Total Cycles” switches from its year-to-date default to your window), plus 🏢 POD and project narrowing.

Trend deltas & drill-downs

Each headline card carries a short trend delta — “▲ 3 this week” under Total Cycles, “▲ 2 this month” under Approved. Those are fixed-period indicators and do not follow the date filter. Lower down, By POD & project breaks completion and return counts down per project.

The charts

• Ups & Downs trend — a stacked bar per cycle (Ups green, Downs red) with the net figure labelled; toggle between the chart and the underlying table.
• Return rate — how often cycles were returned at each stage (PM → PL, Delivery SPOC → PM …). A high rate at one stage points at a quality or communication problem there; hover a bar for the most common reason.
• P&A completion — the weekly submission rate as a line. The SLA card below it gives average, minimum and maximum approval times and the share of cycles approved inside the 3-day target.

CSV exports & scheduled reports

The Export CSV dropdown downloads data files covering only the projects you have access to. Every file is formula-safe — any cell that would trigger a spreadsheet formula is prefixed automatically, so opening one in Excel cannot execute anything. System Admins can schedule reports from Admin → Scheduler, emailed weekly or monthly as a CSV attachment (there is no daily cadence and no PDF attachment).

🔔 Notifications

Notifications keep you informed about everything that needs your attention — cycles awaiting your review, Priorities & Achievements returned for revision, weekly digests, approaching deadlines, and bilateral approvals. They appear in two places: the 🔔 bell in the top bar (a quick dropdown of the latest items) and the full Notifications screen (the complete, filterable history).

The notification bell

The bell in the top bar shows an unread count badge. Click it for a dropdown of recent notifications; click any item to jump straight to the relevant cycle, Priorities & Achievements week, or report. A 🔕 icon means notifications are currently snoozed.

The Notifications screen

Open Notifications from the sidebar for the full, day-bucketed feed. Each row shows the category, title, message, and time. Unread rows are tinted light blue.

Notification categories

The same six chips filter the list, and the URL carries the filter (?category=Digest&unread=1), so a filtered view can be bookmarked or shared.

Preferences & snoozing

Control which notifications you receive — and how — from the Notification Preferences card on your Profile. You can mute individual project timelines and snooze all notifications for a set period (the bell shows 🔕 while snoozed). Email notifications mirror the in-app feed and respect the same preferences, including the weekly digest frequency (Weekly, Daily, or Off).

📋 Audit Log

Every state-changing action in the portal is recorded in the append-only audit log. Admins see the full app-wide log; other roles see the log filtered to their projects and submissions.

What is recorded

Cycle and P&A state changes, item edits, user and project administration, token issue and revocation, and email sends. Three things are deliberately not audited, to keep the log readable: notification read-receipts, the system health endpoint, and the dev-only scheduler reset.

Reading an entry

An entry names the actor and the role they were acting as, the action key (cycle.approved, cycle.item_edited …), the entity it touched, a plain-language description, and a UTC timestamp. Where a field actually changed, the before/after diff is carried with it; a pure state change says so rather than showing an empty diff.

Filtering the admin audit log

The filter bar on Admin → Audit Log narrows by entity (cycle, priorities, user, project …), entity ID for one specific record, actor by name, action by event type, and a date range. The filtered result exports to CSV.

🔌 MCP Integration

POD Governance ships an MCP (Model Context Protocol) server that lets AI agents (Claude, GitHub Copilot, etc.) query and update the portal via natural language.

Generating a Personal Access Token

You need a PAT to authenticate your AI agent with the MCP server. Go to My Profile → MCP Access Tokens, click Create token, copy the plaintext secret (shown only once), and paste it into your AI agent configuration.

MCP token vs AiDE Fabric Token

They point in opposite directions and are never interchangeable. The pgmcp_ MCP token lets an assistant call in to POD Governance as you; the aide_fabric_token_ Fabric Token lets POD Governance call out to AiDE.

Environment variables

The server needs two: MCP_API_BASE_URL (the POD Governance API it calls) and MCP_API_TOKEN (your pgmcp_ token). MCP_PORT is only needed for the HTTP transport — stdio is the default and is what every desktop client below uses.

Claude Desktop setup

Edit claude_desktop_config.json — on Windows %APPDATA%\Claude\, on macOS ~/Library/Application Support/Claude/, on Linux ~/.config/Claude/:

{
  "mcpServers": {
    "pod-governance": {
      "command": "node",
      "args": ["<path>/src/mcp/dist/index.js"],
      "env": {
        "MCP_API_BASE_URL": "https://vishnuvm.centralindia.cloudapp.azure.com/PODGovernance/api/v1",
        "MCP_API_TOKEN": "pgmcp_YOUR_TOKEN_HERE"
      }
    }
  }
}

Claude Code CLI setup

claude mcp add pod-governance node ./src/mcp/dist/index.js \
  --env MCP_API_BASE_URL=https://vishnuvm.centralindia.cloudapp.azure.com/PODGovernance/api/v1 \
  --env MCP_API_TOKEN=pgmcp_YOUR_TOKEN_HERE

The server name carries the environment when you are not on production (pod-governance-staging, -qa, -dev), so several environments can be registered side by side without clashing.

HTTP transport

For a client that cannot spawn a process, run the server over HTTP instead:

MCP_PORT=3100 MCP_API_BASE_URL=https://vishnuvm.centralindia.cloudapp.azure.com/PODGovernance/api/v1 MCP_API_TOKEN=pgmcp_… node dist/index.js

What the server exposes

64 tools, 3 resources and 3 pre-built prompts — listing, forwarding and returning cycles, full CRUD on Ups & Downs and P&A items, submitting and reviewing P&A, reports, AiDE-suggestion drafting, admin CRUD for projects/PODs/users, Meeting Notes AI and Project Timeline. Long-running calls report progress notifications rather than appearing to hang.

Token management & the interaction log

A token acts as you and inherits your role and project access, so scope it read-only unless the assistant genuinely needs to submit or forward. Revoke instantly from My Profile if it leaks; every call it makes is recorded per-token under Admin → MCP Interaction Log, with slow-call flags.

👤 Profile & Tokens

The My Profile screen lets you manage all personal settings: your display name and account details, appearance (light/dark/system), email notification preferences, MCP access tokens, and active sessions.

Display name

Your display name is what appears in audit entries, notifications, the timeline feed and review screens — so it is not only cosmetic. Edit it and click Save; changes take effect immediately.

Switching your active role

If you hold more than one role — say both PM and Sales SPOC — the Active Role dropdown switches between them. The sidebar, the access rules and every screen adapt immediately, and your role badge in the top bar follows. Audit entries record the role that was active at the time of each action, so switching is part of the record, not a display preference.

Appearance — light & dark mode

Pick Light (default), Dark, or System, which follows your operating system. The choice applies at once and is remembered per device. You can also toggle it from the command palette (Ctrl/⌘ K → Toggle dark mode).

Notification preferences

These control email only — the in-app 🔔 bell always shows everything regardless. Each switch covers a whole workflow: turning off Ups & Downs or Priorities & Achievements silences its reminders and its approval / return notices together, and there is no separate switch for one without the other. The digest card underneath sets its frequency (Weekly, Daily or Off), what it includes, and can preview or test-send it.

Active sessions

Lists every device currently signed in — browser and OS, IP, last-active time and when the session started — with your own marked This device. Sign out any you do not recognise. In a normal browser tab sessions also end after 30 minutes of inactivity, with a 5-minute countdown warning; in the installed app that idle window extends to 24 hours.

MCP Access Tokens

Create and revoke Personal Access Tokens for the MCP server. Give each one a label naming the machine it lives on (“Claude Desktop — Work Laptop”) so revoking the right one later is obvious. The token is displayed once, in full — copy it immediately; only a hash is stored. See MCP Integration for the setup snippets.

⚙️ Admin Portal

The Admin Portal is available to System Admins and PMO Associates. It provides management screens for the entire platform.