👥 People & Organisation
Everyone in the org and how they’re wired — users & roles, their invitations, the PODs & projects they belong to, and the reporting lines between them — all in one place.
💡
Ups & Downs submissions flow through: Project Lead → Project Manager → Delivery SPOC → Sales SPOC → POD Owner → Cluster Head. Assign all reviewer roles to a project to prevent cycles stalling at a stage with no assigned user.
4
Total Projects
3
Active
2
PODs
1
Inactive
🏢 Project Accounts
| Account Name | Senior Roles | Delivery Roles | Status | Actions |
|---|
💡
PODs are organisational groupings for projects. Each project belongs to exactly one POD. Deactivating a POD hides it from new project creation but does not affect existing projects or their cycles.
2
Total PODs
2
Active
0
Inactive
4
Projects
🧩 PODs
| POD Name | POD Owner | Cluster Head | Projects | Status | Actions |
|---|
👥 Users & Roles
Manage user accounts, role assignments, and invitations
💡
Roles determine which workflow stages a user participates in. A user may hold multiple roles. Invited users hold a pending activation link — they gain full access once they sign in for the first time.
11
Total Users
11
Active
2
Pending Invites
7
Distinct Roles
🎭 Role Definitions
| Role | Description | Permissions |
|---|---|---|
| Project Lead | Bottom of the delivery chain; submits Ups & Downs and Priorities & Achievements | Submit own items, view own audit |
| Project Manager | Reviews and consolidates Project Lead submissions | Edit all items, add/delete, forward to Delivery SPOC, return to PL |
| Delivery SPOC | Delivery single point of contact; manages PMs, reports to POD Owner | Edit items, approve/return; escalation recipient |
| Sales SPOC | Sales single point of contact; reports to POD Owner — no delivery reportees | View projects assigned, Priorities & Achievements bilateral with POD Owner |
| ESO SPOC | Engineering Services Ops SPOC; reports to POD Owner — no delivery reportees | View projects assigned, Priorities & Achievements bilateral with POD Owner |
| Recruitment SPOC | Recruitment SPOC; reports to POD Owner — no delivery reportees | View projects assigned, Priorities & Achievements bilateral with POD Owner |
| POD Owner | POD Owner — end-to-end accountability for Growth, EBITDA & NPS; reports to Cluster Head | Edit items, approve/return; penultimate review |
| Cluster Head | Owns 3 PODs; top of the reporting chain — final approval authority | Read-only view, final approve/return |
| PMO Associate | View-only observer across all projects | Read-only — no edit, approve or return |
| Administrator | System admin — manages users, projects, cycles, email templates, and audit logs | Full system access; no workflow approval rights |
| Project Contributor | P&A-only bottom tier; reports to a Project Lead. Not shown in reports, Ups & Downs, or project membership | Submit own Priorities & Achievements; reviewed bilaterally by their Project Lead |
👥 User Directory
| User | Roles | Projects | Status | Actions |
|---|
🌳 Org Hierarchy
The full reporting tree derived from active reporting relationships (Cluster Head → POD Owner → Delivery SPOC → Project Manager → Project Lead).
Roles:
Cluster Head
POD Owner
Delivery SPOC
Sales SPOC
ESO SPOC
Recruitment SPOC
Project Manager
Project Lead
🤝 Meeting Notes AI
Oversight of the Meeting Notes AI — every meeting, its AiDE processing state and action-item closure across the organisation.
🔐
Meeting content (MoM, mindmap, action items) is owner-controlled — administrators see the register and closure metrics here, not the transcripts. Reminder rules ET-030 – ET-032 are data-driven (per action item’s own due date) and surfaced read-only under Scheduler → Meeting Notes AI Reminders; the notification copy under Email Templates.
7
Meetings
5
AiDE Processed
8
Open Action Items
2
Overdue Action Items
0
Processing Failed
0
Stuck Runs
🔑 AiDE Fabric Token adoption
4 of 5 connected · 80%
Who has connected a token? (1 not yet connected)
| User | Role | AiDE token | Meetings processed | Last processed |
|---|---|---|---|---|
| Basavaiah Potla | POD Owner | ✓ Connected | 3 | 30 Jun 2026 · 4:12 PM GMT+5:30 |
| Devi Alekya Abburi | Recruitment SPOC | ✓ Connected | 1 | 2 Jul 2026 · 11:48 AM GMT+5:30 |
| Pavani Prathyusha Mulpuru | ESO SPOC | ✓ Connected | 1 | 26 Jun 2026 · 2:30 PM GMT+5:30 |
| Vish Lakshmanan | Cluster Head | ✓ Connected | 2 | 1 Jul 2026 · 10:05 AM GMT+5:30 |
| Sekhar Posina | Sales SPOC | ✗ Not connected | 0 | — |
🔍 Filter Meetings
Meetings
Most recent first · content stays owner-controlled
| Meeting | Owner | Project | When | Mode | Status | Access | Action items | Actions |
|---|
⏰ Scheduler & Automation
Configure review cycles, deadlines, and automated reminders
ℹ️
Cycles automatically trigger email notifications and submission deadlines. Reminders are sent via email. All times are in the configured timezone.
Active Cycles
—
Archived Cycles
—
🔄 Review Cycles
Auto-triggers submission window
| ID | Name | Frequency | Schedule | Projects | Next Run | Status | Actions |
|---|
🤝 Meeting Notes AI Reminders
Action-item reminders — data-driven (per action item’s own due date & assignee), swept daily at 08:30 IST. Read-only.
| Rule | Trigger | Recipients | Template | Status |
|---|---|---|---|---|
| Meeting Action Due Soon R-013 |
3 days before the due date | Assignee | ET-030 | ● Active |
| Meeting Action Due Today R-014 |
On the due date | Assignee | ET-031 | ● Active |
| Meeting Action Overdue Escalation R-015 |
Every 2 days while overdue | Assignee, cc meeting owner | ET-032 | ● Active |
⚙️ Global Automation Settings
Control automated triggers globally.
🛑 Disable All Automation
Pauses all automated cycle creation and email triggers. Use during maintenance or testing.
Automatically create review cycles on schedule (weekly/biweekly/monthly).
Send email/Teams notifications for workflow events and reminders. System maintenance (stuck-run recovery, data retention) keeps running — only Disable All Automation stops that.
Enable scheduled Project Health summary delivery — the weekly/monthly summary emails for users who opted in. Off by default.
Let meetings be processed with AiDE automatically once a transcript is staged, without anyone pressing Process. Off by default, and only ever runs on meetings whose owner has opted that meeting in — each run uses, and bills, that owner’s AiDE Fabric Token. One meeting is processed per minute.
Email each person a short AI-written briefing on weekdays, at 07:00–09:00 in their own timezone: what is waiting on them, in the order worth doing, plus a plan for their day. Off by default. Each briefing spends one AiDE call billed to that recipient’s own Fabric Token — or, when theirs is missing or expired, to the first working token up their reporting chain. Anyone with nothing pending and no meetings gets no email.
Each morning, ask AiDE whether the overdue action items it can see are actually worth chasing — today the reminder ladder simply re-sends every 2 days for as long as an item stays open, with no judgement. This changes no email. Nothing is sent, suppressed or rescheduled by it; the recommendations appear in Runs below, for a person to read and act on. Off by default. Each batch spends one AiDE call billed to the meeting owner’s own Fabric Token.
Email every active Cluster Head their AiDE risk radar (Downs and overdue actions across their own projects) once a week. Off by default. Each digest spends one AiDE call billed to that Cluster Head’s own Fabric Token — a Cluster Head with no assigned project, no token, or nothing to rank simply gets no email that week.
Email every active PMO Associate the AiDE commentary across all projects once a week. Off by default. Each digest spends one AiDE call billed to that PMO Associate’s own Fabric Token — someone with no token, or a week AiDE has nothing to say about, simply gets no email. Note the content is the same org-wide picture for every recipient, so this costs one call per PMO Associate for one answer.
Hours of inactivity before escalation alerts are sent (default: 48h).
How long an invitation link remains valid after sending (default: 72h). Expiry dates in all timezones are shown in the invitation email.
Days of timeline inactivity on a project before the stale-project nudge (ET-027) fires (default: 14).
Days to keep sent-email records before the daily cleanup purges them (default: 90; 0 = keep forever).
🔐 Access & Security
Org-wide access and role limits.
Maximum number of users that may hold the System Admin role org-wide (default: 2). Granting admin beyond this limit is blocked in Users & Roles.
0 of 5 admins in use
Max sign-in & token requests allowed per client (IP) in a 15-minute window before “Too many authentication attempts” is returned (default: 30; must be between 5 and 1000). Applies in production only. Takes effect within ~1 minute.
Notification templates and the outbound delivery log — edit a template, then check its recent deliveries, without a nav round-trip.
📧 Email Templates
Manage notification templates with dynamic variable tokens
🔒
Templates are read-only. Subject and body are owned by the codebase and ship with each release, so they stay in step with the data each email actually has. You can still enable or disable any template here — a disabled template is never dispatched, even when its trigger fires.
18
Total Templates
16
Enabled · 2 disabled
91
Sent (last 24 h)
2
Needs Review
Templates (12)
🔗 Reporting Relationships
Defines who reports to whom for the Priorities & Achievements weekly workflow. These relationships are resource-level (not project-linked).
ℹ️
Priorities & Achievements flow up through these bilateral pairs: Project Contributor → PL → PM → Delivery SPOC → POD Owner → Cluster Head. The Project Contributor is a P&A-only tier reviewed by its Project Lead; Sales, ESO & Recruitment SPOCs report directly to the POD Owner with no downward delivery chain. Each pair independently reviews and agrees their weekly commitments. This is separate from the project-based Ups & Downs workflow.
—
Total Pairs
—
Active
—
Inactive
—
Role Pair Types
👥 Direct Reporting Pairs
Used for Priorities & Achievements weekly cycle
| Reporting Pair | Direct Report | Manager | Level | Active | Actions |
|---|
🌳 Reporting Hierarchy Visualisation
Priorities & Achievements flow direction
🔑 MCP
Personal Access Tokens for AI assistants, and the audit log of every token-authenticated tool call they made.
🔑 MCP Access Tokens
Personal Access Tokens let AI assistants (Claude Desktop, Claude Code CLI) act on the POD Governance API on a user's behalf.
🔒
Tokens are shown once at creation and stored only as a hash — they cannot be recovered. A token inherits the role & project access of its owner. Use a read-only token for dashboards and digests; use read & write only when the assistant must forward, return, or submit. Revoke immediately if a token is exposed.
4
Total Tokens
3
Active
1
Revoked
1
Service accounts
All Tokens
| Name | Owner | Scope | Client | Last Used | Expires | Status | Actions |
|---|
DEV
— Logs shown are from the DEV environment
📋 MCP Interaction Log
Every token-authenticated API call made by MCP clients on a user's behalf.
🤖
Every API call made by an MCP client (Claude Desktop, Claude Code, custom integrations) using a Personal Access Token is recorded here. Use this log to audit AI-agent activity and investigate unexpected workflow changes.
142
Total Calls
131
Success (2xx/3xx)
8
Client Errors (4xx)
3
Server Errors (5xx)
247
Avg Duration (ms)
🔍 Filter Interactions
🩺 Per-tool health
| Tool | Calls | Error rate | 4xx | 5xx | Avg | p50 | p95 | p99 |
|---|
Interactions
Most recent first
| Time | Identity | Token | Tool | Endpoint | Status | Duration |
|---|
⚙️ Settings
Read-only view of the API's runtime configuration — what the server actually loaded, not what a file says it should have.
👁️
Everything here is read-only. Values come from the running API process, so this is the place to confirm what an environment is genuinely using. Secrets are never displayed — only whether each one is set.
✉️ SMTP connection test
Opens a real connection to the configured host and runs the full handshake (including STARTTLS and AUTH when credentials are configured). No email is sent.
🤖 AiDE Configuration
The model, endpoint and timeouts this deployment is actually calling AiDE with. Read-only — they are set in code, so changing one needs a release.
Updated 3 Sep 2026, 08:12
Current settings
- Model
- giga-brain
- Endpoint
- https://aide.valuelabs.com/v1/chat/completions
- Completion timeout
- 2m 0s
- Token-verify timeout
- 10.0 s
Calls by type
last 30 days
| Run type | Calls | Succeeded | Failed | In flight | Failure rate | p50 | p95 | Max |
|---|---|---|---|---|---|---|---|---|
initial | 412 | 401 | 11 | 0 | 2.7% | 6.2 s | 14.8 s | 41.0 s |
risk-radar | 88 | 86 | 2 | 0 | 2.3% | 9.1 s | 19.4 s | 28.7 s |
said-vs-done | 64 | 61 | 1 | 2 | 1.6% | 4.8 s | 11.2 s | 15.9 s |
daily-briefing | 3 | 0 | 0 | 3 | — | — | — | — |
pmo-digest | 24 | 21 | 3 | 0 | 12.5% | 18.4 s | 52.1 s | 94.6 s |
🪝 Webhooks
🔒
Each webhook gets a signing secret shown once at creation and stored only as a hash. Every delivery carries an
X-PodGov-Signature header — an HMAC-SHA256 of the exact request body — so your endpoint can verify the payload really came from POD Governance. The target must be a publicly reachable https URL; private, loopback and link-local addresses are refused, and redirects are not followed.3
Total
2
Active
6
Recent deliveries
2
Failed (24h)
🔗 Subscriptions
| Name | Target URL | Events | Secret | Status | Last delivery | Actions |
|---|
Delivery log
| Time | Webhook | Event | Attempt | Status | HTTP | Error |
|---|
DEV
— Emails shown are from the DEV environment
✉️ Email Log
Every email the system has sent — recipient, subject, final message body, time and delivery status.
✉️
Every email dispatched by POD Governance — scheduler notifications, sign-in links, invitations, test sends and scheduled reports — is recorded here with its final rendered body. Use this log to confirm delivery and review exactly what each recipient received.
1,284
Total Emails
1,271
Delivered
13
Failed
96
Sent Today
🔍 Filter Emails
Emails
Most recent first
| Sent | Recipient | Subject | Type | Template | Status |
|---|
📊 Reports & Exports
Generate and download governance reports across all projects and PODs
💡
On-demand exports generate a CSV snapshot of current data — refresh the page for the latest figures before downloading. Scheduled reports run automatically and are emailed to recipients; recipients are not required to have portal accounts.
18
Total Cycles (YTD)
14
Approved
3
In Progress
87%
Priorities & Achievements Completion
⬇️ On-Demand Exports
CSV downloads
to
All exports use the selected date range.
📊 Cycle Status Report
All cycles with status, reviewers, approval dates
📈📉 Ups & Downs Trend
Ups/Downs per cycle, net score, return count
🎯 Priorities & Achievements Completion Report
Weekly Priorities & Achievements submission rates and AiDE adoption
👥 User Activity Report
Logins, submissions, approvals per user
↩️ Return Rate Report
Returns by stage, reason, and reviewer
📋 Full Audit Log
All system events within the date range
⏰ Scheduled Reports
| Report | Frequency | Recipients | Next Run | Status |
|---|
DEV
— Logs shown are from the DEV environment
📋 System Audit Log
Complete record of all governance actions across all projects, cycles, and workflows
💡
This is a unified, append-only audit log — a single trail across every operation in the portal: U&D cycle submissions/approvals/returns, Priorities & Achievements bilateral reviews, admin changes (users, projects, PODs, settings, scheduler, email templates), reporting-relationship edits, access-token issue/revoke, and sign-ins. Each row is tagged with its entity so any record's detail screen can show its own activity trail. Entries are immutable. Filter by entity, actor, event type, or date range, then export to CSV for compliance reviews.
🔍 Filter Events
Events
Most recent first
| Time | Who | Role | Action | Entity | Project / Module | Cycle / Week | Detail |
|---|