Funcionalidades | PartnerView

Sales and CRM

Leads

Capture and qualify prospects before they become deals.

Lead capture: Record a lead with company, contact, source, and notes.
Lead source tracking: Categorize where each lead came from, using an admin-managed source list (referral, inbound, partner intro, and so on).
Structured source type: A source_type enum (web form, referral, partner, outbound, event, other) sits alongside the free-form source field for clean reporting.
Lead status workflow: Move a lead through New, Qualifying, Disqualified, and Converted.
Contact picker: Link an existing contact or create a new one inline, directly from the lead form.
Lead interests: Lead interests are first-class rows on the lead. They carry forward to the converted deal as quote-line candidates.
Convert to deal: Turn a qualified lead into a deal with its information pre-filled.
Source lead attribution: The source lead id is stamped on the converted deal so attribution survives downstream reporting.
Escalations anchor: Escalations anchored to a lead carry over to the converted deal, so issues raised during qualification stay attached.
Lead editing: Edit a lead after creation; converted leads become read-only and point to the deal they became.

Companies

The master record for every client, tying their deals, projects, and contacts together.

Company records: Name, website, industry, employee count, and location.
Company detail tabs: Overview, tech stack, deals, contacts, projects, and activity history in one place.
Lifecycle parent: A company holds all of its deals and projects over time, so the full client history lives in one record.

Contacts

The people at each client, and the roles they play in deals.

Contact records: Name, title, email, phone, and linked company.
Deal roles: Assign a contact as Champion, Decision Maker, or Influencer on a deal.
Multi-deal contacts: One contact can serve as a champion across multiple deals.

Deals

Where consulting deals are qualified, valued, and moved to a close.

Deal records: Name, company, owner, practice line, pipeline stage, and source.
Estimated value: Capture recurring (ARR) and services value as separate figures.
Critical Date countdown: A color-coded countdown widget that keeps a time-sensitive deal visible to everyone on it.
Budget capture: Record the prospect's actual budget, separate from your quoted value.
Multi-champion support: Track every advocate on a deal, mark one primary, and keep notes per champion.
MEDDPICC qualification: The full MEDDPICC framework built natively into every deal.
Deal-to-project handoff: Convert a closed deal into a project, with a delivery template applied and the discovery document carried across.
Closed Won and Closed Lost: Terminal stages, with a reason captured on every lost deal.

Quotes

A quote builder that understands the four ways a consulting firm sells.

Quote builder: Build quotes inside the deal, with role-by-hours-by-rate line items.
Four pricing models: Time and Materials, Fixed Fee, Retainer, and License, all native.
Rate cards: Role-based rates pulled from an admin-managed catalog.
Discounts and tax: Percentage or flat discounts, plus tax support, with automatic totals.
Commission preview: See the commission a quote would generate before it is sent.
Quote status and versioning: Draft, Sent, Accepted, and Rejected, with draft versions saved.

Pipeline

The sales pipeline as a board you can work.

Kanban board: Deals grouped by stage, with drag-and-drop between stages.
Configurable stages: Pipeline stages and their order are admin-managed.

Lead Intake Forms

Configurable public lead forms that route to the right practice and owner, feed straight into leads and convert-to-deal.

Configurable forms: Build a form with up to 12 field types covering short text, long text, select, multi-select, email, phone, number, date, file, hidden, product, and consent.
Product selector field: A product field links to the existing service and vendor catalogs so submissions land with structured product interest, not free text.
Practice auto-routing: Practice routes from the first-selected product so the lead lands in the right queue without manual triage.
Assignment rules: Single owner, round-robin, or fallback when the primary owner is out.
Fair-distribution round-robin: Round-robin tracks last_assigned_at and total_assigned_count so load stays even across the eligible pool.
Three embed modes: JavaScript snippet, iframe, or hosted URL. Pick what fits the partner microsite.
Cross-origin support: CORS configured for embedding on any partner microsite without browser warnings.
Spam protection: Honeypot field plus per-IP rate limiting to keep bot submissions out.
Per-form theming: Colors, brand logo, and brand name configurable per form so each microsite stays on brand.
View and submission analytics: Per-form view counts and submission counts roll up to a conversion rate.
Submissions audit trail: Each submission is logged with raw_data preserved, so the original payload survives even if the form schema changes later.
Interests carry to deal: Lead interests captured at submission carry through convert-to-deal as quote-line candidates.
Admin form CRUD: Admin-only form lifecycle with draft, published, and archived statuses.

Proposals

Branded client proposals built from a quote, with native e-signature, payment through QuickBooks, rich authoring, client-configurable pricing, engagement analytics, and a template gallery. Freeze-on-send means the executed agreement is exactly what was signed.

Built from any quote scenario: Author a proposal from any quote scenario on the deal. Edit the cover, overview narrative, scope narrative, pin a versioned Terms and Conditions, set an expiry, and choose which deal attachments are client-visible.
Branded client viewer: Token-gated public link at /public/proposals/[token]. Responsive, mobile-first page themed with the org logo and primary color. Rate-limited per IP, noindex, host-gated.
Native e-signature: Typed signature, ESIGN/UETA consent checkbox, and a Decline action. The signer confirms the recipient bound at send rather than self-asserting authority. Signing records an append-only signature with consent text, T&C version and hash, IP, and user-agent.
Freeze-on-send invariant: Sending freezes line items, totals, scope, the full Terms and Conditions body and its SHA-256 hash, embedded-document references by stable id and content hash, and branding into an immutable snapshot. The client viewer renders strictly from the snapshot, never the live quote.
Countersignature and full execution: Countersigning the client-signed proposal appends a second signature, flips the proposal to fully executed, moves the deal to Closed Won (idempotent), and creates the project via the deal-to-project handoff.
7-year retention and legal-record immutability: Signed and fully-executed proposals refuse trash and purge for everyone, admin included. Attachments on a signed proposal cannot be deleted. Proposals, snapshots, and signatures are retained 7 years. Signatures and audit events are append-only.
Append-only audit chain: Every consequential event captured append-only with actor, IP, and user-agent: sent, viewed, signed, countersigned, executed, declined, paid.
Pay through QuickBooks: When the deal's invoice is in QBO with online payment enabled, the executed viewer surfaces Pay now deep-linked to the QBO hosted invoice page. Card data never touches PartnerView. When payment is not enabled, the page shows View invoice in QuickBooks instead. Never a dead Pay now.
Automatic paid-in-full reconciliation: QBO payment reconciliation flips the proposal to paid automatically and fires the proposal.paid notification once per proposal.
Executed-copy client email: On full execution the client is emailed a copy linking back to the executed proposal viewer (the same client-safe frozen snapshot). Gated by an org-level switch and the master transactional-email switch.
Rich-text WYSIWYG: Toolbar formatting (bold, italic, bulleted and numbered lists, links). Server-side sanitizer at store and render. Scripts, styles, and unsafe links never reach the client viewer or PDF.
Allowlisted video embeds: YouTube, Vimeo, and Loom only. Other hosts stripped by the sanitizer.
Client-safe merge tokens: Contact name and title, client company, deal name, contract value, quote total, your organization, sender name, today's date. Resolve live while draft, freeze on send. No cost, margin, or internal field is tokenizable.
Reusable content snippets: Save as snippet from a rich-text block; Insert snippet from the block palette. Snippets store client-safe shell only.
Interactive client-configurable pricing: Mark any line client-selectable with a quantity range. Group lines under select-at-least-1 or select-between-1-and-3 rules. The client toggles options in the viewer and sees the grand total update live.
Same pricing engine end to end: The same pure pricing engine computes the total in the viewer, at signing (authoritative), and in the PDF, so the number the client sees always equals the executed number.
Forced-minimum-to-sign gate: Signing is blocked until every group's minimum-select is satisfied and no group exceeds its maximum.
Executed selections in the signature record: The client's exact line and quantity selections and the resulting grand total freeze into the append-only signature record as the legal executed total.
Per-section engagement analytics: Time-on-page per section (Overview, Scope, Investment, Your options, Documents, Terms, Sign), maximum scroll depth, PDF downloads, and a soft multi-device count. Retained 90 days. Surfaces on the proposal editor for the deal owner.
Privacy-respecting telemetry: No raw IP address or user-agent stored or shown. Distinct devices counted with a salted one-way hash. Multi-device count is a soft signal, not a hard claim.
Engagement notifications: Two fire-once notifications: proposal downloaded, proposal viewed from another device. Existing proposal-signed and proposal-paid-in-full notifications unchanged.
Template gallery: Curated system starters grouped by category (SaaS implementation, Professional services, Retainer, Managed services, Quick quote), alongside the user's own saved templates. Live mini-preview on each card and a full shell preview before applying.
Pricing always seeds from the deal: Use this template applies the selected template's shell to a new proposal; pricing always seeds live from the deal's quote, never from the template. Templates are shell-only, so a starter cannot leak another deal's numbers.

Quick Deals and templates

A lightweight path for small deals and recurring deal shapes. Per-practice templates carry field config, pricing defaults, default turnaround, and a configurable approver, so the common deals do not get rebuilt from scratch every time.

PM-initiated expansions: Capture a small add-on, such as a ten-hour expansion, from inside a project, with a manager approval step before it becomes a real deal.
Per-practice templates: Admin authors named templates per practice for the firm's recurring deal shapes (monday.com partner license plus services, vendor sub, partner-led co-sell, retainer expansion).
Field config per template: Each template carries a field config: which fields show on the form and which are required, so each shape collects exactly what it needs.
Pricing defaults per template: Templates default to hourly with a default rate and hours, or flat with a default amount, so quoting does not start from zero.
Default turnaround seeds the target date: A default turnaround on the template seeds the target close date on the deal.
Configurable approver per template: Approver is the project manager by default, or a specific named user, so quick deals route to the right reviewer.
MEDDPICC defaults: MEDDPICC defaults seed alongside the field config so qualification starts populated for the shape.
Quote scaffold pre-fill: Spinning a new deal from a template pre-fills the quote scaffold with line types and defaults from the template.
Central approvals tab: A central Quick Deals tab in the approvals inbox at /admin/approvals collects all submitted quick deals routed to the current approver.

Delivery and Projects

Projects

The delivery-side home for every engagement, pre-populated from the sale.

Project records: Name, company, practice, status, budget, contract value, and dates.
Pre-populated handoff: A project arrives from sales with the template applied, the team assigned, the discovery document snapshotted across, and the sales sponsor retained.
Sales Sponsor and Project Lead: The deal owner carries into delivery alongside the delivery-side owner.
Status workflow: Planning, Active, On Hold, At Risk, Completed, and Cancelled, with a full status history.
Health Score: Automatically computed from the project's open risks and issues.
Multi-deal linkage: A project can tie to a founding deal plus expansion deals over its life.

Phases and Tasks

The work breakdown, with dependencies that catch impossible plans.

Phases: Major work groupings with dates, status, and an owner.
Tasks: Live inside phases, with status, owner, and planned versus actual hours.
Dependencies: Mark tasks that block other tasks, with automatic detection of impossible dependency loops.
Project templates: Admin-managed phase and task structures applied automatically at project creation.

Timeline

A visual project timeline.

Gantt timeline: Phases and tasks shown as bars across their date ranges, with dependency arrows and a marker for today.

Budget

Quoted versus actual, continuously, so budget drift is visible early.

Quoted vs Actual: Every project compares quoted figures against actual logged time, broken down by role, with the variance shown.

Risks and Issues

Track what might go wrong and what already has, feeding project health.

Risk tracking: Description, category, likelihood, and impact, with severity computed automatically and a mitigation plan and owner.
Issue tracking: Record problems that have already happened, with severity, owner, and resolution.
Health feed: Risk and issue severity feeds directly into the project Health Score.

Status Reports

Weekly client status reports that write their own first draft.

Auto-populated reports: Reports fill themselves from real project data, including phase progress, task velocity, recent risks, and budget variance.
Override fields: The project manager writes the narrative: executive summary, what went well, what is next, blockers and asks.
Send to client: Sending snapshots a version; the client sees only the latest sent version.

Change Orders

Capture scope changes and their commercial impact in the same motion.

Commercial change capture: Record a scope change with its hours impact, dollar value, and justification.
Automatic expansion deal: An approved change order automatically creates a linked expansion deal, so the revenue is tracked the moment the scope is.

Insights

PartnerView Insights: rule-based suggestions that flag projects before they slip. Rule-based, not AI.

Rule-based project suggestions: A suggestion pane that runs seven rules on real project state, including blocked tasks, off-schedule phases, budget variance, stale status reports, aging risks, unassigned tasks, and disengaged sponsors.
Dismissible suggestions: Each suggestion can be dismissed, and dismissals persist for that project.

Portfolio

Every project at a glance, worst-first.

Portfolio view: A top-level view of all projects, with a KPI strip and a health matrix sorted worst-first.
Pipeline Expansion KPI: The total value of expansion deals tied to existing projects, separated from new business.

Escalations

First-class escalation records anchored to lead, deal, project, or task. State machine, post-mortem closeout, action items, dashboards.

Anchor anywhere: Anchor an escalation to any lead, deal, project, or task. Anchors carry over when a lead converts to a deal or a deal converts to a project.
Five-state workflow: Status moves through open, acknowledged, in_progress, resolved, closed. Reopening from closed requires a written reason.
Four priority levels: Low, medium, high, critical. Descriptive in v1, no automated SLA tripwires.
Owner and participants: Owner badge plus a participants list, with @mention auto-add so anyone tagged in a comment joins the record.
Scoped comments and attachments: Comments and file attachments live on the escalation, not on the anchor record, so the thread stays clean.
Structured post-mortem closeout: Closeout requires root cause and resolution summary. Customer impact, internal impact, and lessons learned are optional fields.
Action items at closeout: Capture action items with assignee, target date, status, and an optional link to a project or task.
Per-type closeout templates: Templates pre-seed the post-mortem prompts and default action items so each escalation type closes consistently.
Closeout lock: Locked closeouts freeze the post-mortem and action items. Unlock requires admin plus a written reason.
Multi-closeout history: Re-closing an escalation creates v2, v3 and onward. Prior closeouts are preserved in full.
Six reports plus linkage: Reports for by_status, by_type, by_age, time_to_resolve_trend, by_owner, and action_item_completion, plus a linkage_patterns view that surfaces fragile projects.
Dashboard at /admin/escalations/dashboard: Five-panel layout that gives ops a single view of in-flight and recently-closed escalations.
Visibility-aware analytics: Counts and aggregates respect permissions so non-admins cannot leak hidden escalations through totals.

Requirements and Documents

Requirement Documents

A connected chain from discovery to business to functional requirements, plus a change log.

Discovery Requirements (DRD): Lives on the deal during the sale, then promotes to the project as a frozen snapshot at handoff.
Business Requirements (BRD): Lives on the project, with each row linked back to a discovery row.
Functional Requirements (FRD): Lives on the project, linked back to business requirements, with status, priority, and level-of-effort fields.
Change Log: Tracks scope changes that happen after functional requirements are approved.
Live joins: Linked fields stay current, so a business requirement always shows its up-to-date discovery context.
Status and sign-off: Every document type carries a status workflow and sign-off fields capturing who signed off, when, and in what role.
Task-driven approval: When all the tasks linked to a requirement row are complete, that row surfaces as ready for approval.
Document versions: Every save creates a version, building an audit history.
Requirement-to-task linking: Link requirement rows to project tasks and back, in both directions.
Excel round-trip: Export a requirement document to Excel, edit it in bulk, and import it back, with a validation preview before anything is written.

Documents Hub

Every requirement document across the whole firm, in one searchable place.

Cross-project view: All discovery, business, functional, and change-log documents across every project and deal, in one table.
Search and filter: Search across document text, project and deal names, and exact IDs; filter by type, status, project, or owner.
Deep links: Click any row to jump straight to the source document in its project or deal.
Permission-scoped: Each user sees only the documents in projects and deals they have access to.

Document Generation

Claude-assisted DRD-to-FRD generation with per-row provenance, budget caps, and monday.com board config JSON output.

DRD-to-FRD generation: Submit a DRD and get a structured FRD draft back, ready for review.
Per-row provenance: Every FRD row records the source DRD rows it derived from, so reviewers can trace each requirement back to the discovery doc.
Batch versioning: FRD batches version as v2, v3 and onward. Previous batches are preserved for comparison.
Approval gate: FRD batches move from draft to approved through an explicit approve action. Nothing downstream runs against an unapproved batch.
monday.com board config output: Generate a monday.com board configuration JSON from an approved FRD batch. Manual paste in v1. Output is blocked until the batch is approved.
Token and cost tracking: Token usage and USD cost recorded per call, with a monthly summary per org.
Per-org monthly cap: Set a monthly USD ceiling. Calls return HTTP 429 once the cap is hit, so a runaway prompt cannot drain the budget.
Configurable model and prompts: Admin settings hold the Claude model id and system prompts, with prompt history so changes are reviewable.
Graceful degradation: When the Anthropic API key is not configured, read paths remain functional. Only the generate action is disabled.

People and Organization

People Directory

The whole team, searchable by who they are and what they can do.

Org directory: Every team member as a card with photo, title, team chips, top skills, and time zone.
Search by name or skill: Find people by name or by skill, with a minimum-proficiency filter.
Profiles: A full profile per person, with skills and proficiency, team memberships, bio, and contact details.

Teams

Group the org into teams, with leads.

Team records: Name, description, color, and member list, with lead designation.
Multi-team membership: A person can belong to more than one team.

Titles

Job titles, kept separate from access.

Title catalog: Job titles with a career-level field, managed independently of access roles.

Skills Matrix

A real skills inventory, with proficiency.

Skills catalog: An admin-managed catalog of skills by category, such as platform, methodology, tool, language, and industry.
Per-person proficiency: Skill assignments with proficiency level, years of experience, and last-used date.
Skill-based search: Powers the find-a-person-by-skill search in the directory.

Tech Stack

Track what tools every client runs, and who is switching.

Tools catalog: An admin-managed catalog of tools by category and vendor.
Per-client tech stack: Track which tools each client uses and the status of each, such as current, evaluating, migrating, or churned.
Cross-client queries: Find every client using a given tool, or every client mid-migration.

Performance Reviews

Structured review cycles with confidentiality. Reviewees never see a draft or submitted manager review.

Cycle CRUD: Create and manage review cycles with template, participants, and schedule.
Separated self and manager reviews: Self review and manager review are kept separate. The reviewee never sees a draft or submitted manager review.
Per-participant workflow: Each participant moves through share, acknowledge, and close states independently.
Dedicated permission gates: Permission gates for performance reviews are separate from cost-visibility gates.
Append-only audit: Every state change writes an append-only audit row.
Confidential by design: The data model and UI enforce confidentiality, not policy alone.

PTO Accruals

Daily accrual engine with rollover, request workflow, and audited balance adjustments.

Per-user PTO balance: Each person carries a PTO balance that reflects accruals, requests, and adjustments.
Daily accrual cron: A daily job accrues PTO per policy.
Rollover engine: Carryover rules per policy decide what rolls over at the cycle boundary.
Request workflow: PTO requests move through requested, approved, rejected, and cancelled states.
Manager approval queue: Managers approve PTO requests from a dedicated queue.
Audited balance adjustments: Manual balance adjustments require a reason and write an audit row.
PTO-aware utilization: The resource heatmap accounts for approved PTO when calculating utilization.

Compensation History

Append-only effective-dated salary and rate history. Permission-gated, distinct from cost-visibility.

Append-only history: Every salary and rate change for a person is preserved as a new row, not an edit.
Effective-dated: Each entry carries an effective date, and future rates can be scheduled in advance.
Distinct permission gate: A permission gate separate from cost-rate visibility means admins and HR see compensation while PMs see cost rates.
Audited changes: Every change writes an audit row with actor, reason, and timestamp.
Drives downstream comp and payroll: Variable-comp and payroll read directly from compensation history.

Role Fit Review

Confidential role-fit reviews with the same privacy posture as performance reviews.

Cycle workflow per role: Each role-fit review runs through its own cycle.
Confidential manager review: The reviewee never sees a draft or submitted manager review.
Permission-gated: Visibility is limited to the participants and approvers the cycle specifies.
Same posture as performance reviews: The confidentiality model matches the performance review module.
Append-only audit: Every state change writes an append-only audit row.

Finance and Compensation

Quotas

Sales quotas and attainment.

Sales quotas: Quota records with period dates and target values, plus a personal dashboard showing attainment and the deals contributing to it.

Spiffs

Targeted incentive programs.

Spiff programs: Incentive programs with eligibility rules, target criteria, payout amounts, and window dates; once a payout is paid, it is locked from edits.

Variable Comp

One clear view of what each rep is owed.

Variable comp dashboard: A per-rep view combining commission earned and spiff payouts into a single total payable.

Commission Engine

Commission rules with a snapshot mechanism that protects trust.

Commission rules: Tiered rates by recurring revenue or by margin, with bonuses for stretch goals.
Rate snapshot: At deal close, the active commission rate is frozen on the deal, so later rule changes never retroactively alter commissions already paid.
Commission preview: The same engine surfaces a commission preview on quotes during the sale.

Invoices and Payment Schedules

Invoices tied to the work, with milestone-based schedules, pushed live to QuickBooks Online.

Invoice records: Linked to deals and projects, with amount, status, and payment dates.
Payment schedules: Configure milestone-based payment schedules per deal, for example a percentage on signing, on UAT, and on go-live.
QBO push gate: Submit, approve, push workflow on every invoice with idempotency keys; pushing cascades the customer + service item and tags each line with the deal's practice class.
Sync state per invoice: Per-row sync state (synced, pending, failed) visible on the invoice list with manual sync trigger per row.
Automatic retry queue: Failed pushes retry with 1/5/15-minute back-off; after three failures they queue for manual review at /queue with admin notification.
Payment reconciliation queue: Payments sync back webhook-primary with a 15-minute polling backstop; unmatched payments queue at /admin/integrations/qbo/payments/reconciliation for manual matching.

Time Tracking

Logged hours that roll all the way up, plus week-by-week allocation.

Time entry: Log hours against assigned tasks; hours roll up to task, phase, and project actuals and feed the budget comparison.
Resource allocation grid: Allocate people to tasks week by week.
Spread-evenly helper: Allocate a set number of hours per week across a span of weeks in a single action.

Month-end Close

A structured monthly close that closes the loop with QuickBooks Online.

Close workflow: Reconcile invoices against payments, confirm revenue recognized, and lock the period.
Live QBO integration through close: Customer + invoice push, payment sync back, and rev-rec journal entries posted to QBO all flow through the close: nothing is rebuilt in QBO by hand.
Revenue flow runbook: Ten canonical revenue flows documented end to end at /help/revenue-flows, with mermaid diagrams, worked dollar examples, and an interactive decision tree.

Revenue Recognition

Revenue recognized the right way for each pricing model, with journal entries posted live to QuickBooks Online.

Recognition by model: Time and Materials recognized as hours are logged, Fixed Fee on milestones, Retainer monthly, and License per recurring-revenue rules.
Rev-rec journal entries posted to QBO: Monthly recognition batch at /admin/integrations/qbo/recognition: generate, approve, post workflow gate. One journal entry per recognition event, balanced by construction (debit=credit asserted before any entry is persisted; unbalanced entries can never exist), with reversing entries on schedule changes.
GL account mapping: Map system GL accounts to QBO accounts at /admin/integrations/qbo/accounts (sync by number/name, manual override). Unmapped accounts route the entry to the review queue instead of posting to the wrong account.

Contractor payroll

Weekly payroll batches for 1099 contractors. Approval workflow, period locking once sent to HR, and an hours-by-person report ready to hand off. The "who got paid for what hours this week" question becomes a query, not a spreadsheet.

Weekly payroll batches: Weekly payroll batches with date range selection.
Per-user filtering: Filter a batch by user before generating.
Approval workflow: Three-state approval workflow with bulk approve.
Period locking: Once a batch is sent to HR, the time entries in that period become edit-locked.
Hours-by-person report: Hours-by-person report with pay rate, total hours, billable vs non-billable split, and per-user payout.
Xlsx export: Xlsx export of the payroll batch and the hours-by-person report.
Cancellation flow: Cancel a batch to unlink the entries and unlock them for editing again.
Supplemental batches: Supplemental batches for off-cycle pay.
Dry-run preview: Preview a batch before generating the real one.

Platform

Permissions

Granular, role-based access built for firms where contractors, partners, and staff all coexist.

Role-based access: Six roles, Admin, Sales, SE, Delivery, Finance, and IC, each with granular permission keys.
Granular control: Permissions can be granted or revoked per user, and the role builder automatically picks up every permission.
Scoped visibility: Sidebar items and records hide when a user lacks access, with clear "no access" messaging instead of generic errors.
Three-tier hierarchy: Permissions resolve through org, team, then user. The most specific grant wins, so an exception for one user does not require a new team.
117-permission catalog: A flat catalog of 117 permission keys covers every gated action in the product. Pick the exact keys a role needs.
18 sticky-on-admin permissions: 18 permissions stay on for any admin and cannot be revoked, so a misconfigured role builder cannot lock the org out of its own console.
Permission audit log: Every grant and revoke is written to permission_audit_log with actor, target, scope, and timestamp.
Project visibility editor: At /admin/projects-visibility, set per-project access independent of role for sensitive engagements.
Three permissions reports: users_with_admin lists every account that holds an admin permission. team_grants shows what each team confers. recent_changes lists grants and revokes in the last window.

Configuration

The catalogs and fields that let a firm shape the system to its own language.

Admin-configurable catalogs: Practice lines, pipeline stages, lead sources, loss reasons, deal relationship types, rate cards, tax rates, commission rules, and more.
Custom fields: Define custom fields and required fields per entity.
Column labels: Rename column headers to match the firm's own terminology.

Working in PartnerView

The consistent interface model that makes the whole system fast to learn.

Consistent interface: Tables, side drawers, status badges, and filters follow one pattern across every screen, so learning one screen teaches the rest.
Persistent filters: Filter and search state lives in the URL, so it survives a refresh and can be shared by link.
Search and filtering: Debounced search, multi-select filter chips, and sort controls on list pages.
Light and dark themes: A theme toggle across the whole app.
Transaction safety: Multi-step writes are atomic, so an operation either fully completes or fully rolls back, never half-done.

In-record discussion + mentions inbox

Threaded conversations on every lead, deal, project, and invoice. @ user mentions and # cross-record references. Threads follow the lifecycle as deals become projects. A unified inbox at the bell shows everything pointed at you. (Internally "Chatter.")

Discussion threads: Threaded conversations on leads, deals, projects, and invoices.
@ user mentions: @ user mentions with autocomplete.
# entity references: # entity references with autocomplete for cross-record linking.
Unread badges: Per-row unread badges on list pages.
Lifecycle links: Threads carry forward when a deal becomes a project.
Manual cross-record links: Manual cross-record links for threads that need to span beyond their lifecycle.
Bell icon in top nav: Bell icon in the top nav with unread counts and Mentions, Activity, and Notifications tabs.
Notifications tab: Notifications tab in the inbox alongside Mentions and Activity, for system-detected events like budget overruns and approval state changes.
Unified inbox page: Full inbox page at /inbox with filters and bulk mark-as-read.

In-app help center and guided tours

Built-in answers to the questions your team will actually ask. Approximately 113 articles, 102 documented workflows, 33 guided in-app tours, role-based learning paths, and inline help tooltips next to thirty-plus fields. New hires don't need a buddy assigned for their first week. (Used for onboarding, training, and as a knowledge base.)

Help center at /help: Help center at /help with full-text search across approximately 113 articles.
102 documented workflows: 102 step-by-step workflows documenting end-to-end paths through the product.
Article categories: Articles organized across categories covering essentials, each role, power-user topics, and admin and policy.
Inline HelpHint tooltips: HelpHint tooltips on thirty-plus fields and buttons, hover or click to expand.
Contextual "?" help drawer: In-product "?" links open relevant articles in a side drawer without leaving the page.
33 guided in-app tours: 33 guided tours walk through admin, sales, delivery, finance, IC, SE, staffing, and welcome flows.
Role-based learning paths: Learning pathways follow role, covering Getting Started, Sales, Delivery, SE/BA, Finance, IC, and Administrators.
Per-user progress: Per-user learning-pathway progress saved across sessions.
Tours from the ? menu: Tours launch from the "?" menu in the top nav.

Trash and Retention

Soft-delete substrate, 14 retention policies, cascade rules, snapshot-on-purge, 30-day emergency recovery, daily auto-purge cron.

Universal soft-delete: Every entity carries is_trashed, trashed_at, trashed_by, and trash_reason fields. Nothing is hard-deleted on the first action.
14 retention policies: Pre-configured retention windows for the 14 trashable entity types, with per-entity admin override.
Cascade trash: Trashing a parent trashes its children under a shared cascade run id, so a deal and its quotes move together.
Symmetric cascade restore: Un-trashing a parent restores the same children that came along when it was trashed.
Daily auto-purge cron: A 04:00 UTC job purges items past their retention window. Each run is logged.
Snapshot on purge: Purge writes a full snapshot to cold storage with a 30-day emergency recovery deadline before the record is permanently gone.
Admin Trash console: At /admin/trash, per-entity tabs for Leads, Deals, Projects, Tasks, Time, Expenses, Invoices, Quotes, Escalations, Closeouts, Action items, Comments, Attachments, and Audit.
Retention policies console: At /admin/retention-policies, edit windows per entity with a next-run impact preview that shows how many records the change will affect.
Full audit log: Trash, restore, and purge events are written to the audit log with actor, reason, and entity reference.
7-year invoice retention default: Invoices default to a 7-year retention window to match common tax record requirements.

Granular Backup and Entity History

Per-write snapshot of every entity. Field, word, and child-array diff. Cross-entity batch restore as one transaction.

Per-write snapshot: Every insert, update, soft-delete, and restore writes a snapshot to entity_history.
Full row JSON preserved: Each snapshot stores the full row JSON, not just the changed fields, so any prior state can be reconstructed.
Changed-fields summary: Per-snapshot changed_fields summary keeps the history feed fast to render without loading full bodies.
Cross-entity batch restore: A change_batch_id groups related edits across entities. Restoring the batch rewinds all of them as one transaction.
Append-only restore snapshots: Restoring to a snapshot writes a fresh restore snapshot rather than rewriting history, so the audit chain stays intact.
Diff views: Field-level diff for short fields, word-level diff for long text, and child-array summaries for line items and action items.
Configurable retention: Per-entity-type retention with a 365-day default. Admins tune the window to match data sensitivity and storage budget.
Daily purge cron with dry-run: A 04:00 UTC purge job enforces retention. A dryRun preview shows what would be removed before the next live run.
Storage stats: Per-entity-type storage stats with budget hints so admins can see which entities dominate history volume.
Coexists with Trash: Entity History sits alongside the Trash console. Trash holds soft-deleted records, history holds the change log.

Global Search

Cross-entity search palette backed by SQLite FTS5 over 13 entity types.

Cmd+K command palette: Open the search palette from anywhere with Cmd+K. Type to query, arrow keys to navigate, enter to jump.
FTS5 index over 13 entity types: SQLite FTS5 indexes leads, deals, quotes, projects, tasks, contacts, companies, escalations, invoices, partners, files, activities, and requirements.
GitHub-style tag syntax: Filter inline with tokens like type:deal owner:anish status:open company:acme.
Visual filter chips: Filters render as chips with a "+ Add filter" picker for users who prefer click over typing.
Saved searches: Save a query per user. A team-share toggle promotes a saved search to the whole team.
Recent searches: MRU list of the last 20 queries per user, one click to re-run.
Grouped results: Results group by entity type with deep links straight to the record.
Manual reindex: Admin endpoint to rebuild the FTS5 index after a bulk import or schema migration.
Search analytics: Top queries, no-result queries, click-through rate, and daily query volume.
Visibility-aware results: Results respect permissions so non-admins cannot surface entities they would not otherwise see.

Audit Log

Append-only audit across permission grants, settings edits, retention policy edits, lock and unlock cycles, trash, restore, purge events, and import batches. 3-year retention. Viewer at /admin/audit-log.

Append-only log: Audit entries cannot be edited or deleted. The chain is preserved end to end.
Permission grant and revoke events: Every grant and revoke writes an entry with actor, target, scope, and reason.
Settings edits: Configuration and settings changes are captured with before and after values.
Retention policy edits: Changes to retention windows are logged with the prior value, the new value, and the next-run impact at the time of the edit.
Lock and unlock cycles: Escalation closeout locks, month-end locks, and any other lock state changes are recorded with the unlock reason where required.
Trash, restore, purge events: All three lifecycle events feed the audit log so the soft-delete substrate is fully reviewable.
Import batches: Bulk imports record the source, the row counts, and the actor responsible.
3-year retention default: Audit entries retain for three years by default, with admin override for longer windows.
Viewer at /admin/audit-log: Filter by actor, entity, event type, and date range. Deep link to the affected record.

Sage

A docs-grounded AI help assistant that answers composite how-do-I questions, walks decision guides, and runs troubleshooting trees against the product's own logic. Sage has no access to your live business data and no access to source code. Independently leak-tested.

Docs-grounded answers: Sage answers from product documentation and a code-derived domain-knowledge layer, not a generic web crawl. Anchored to how PartnerView actually works.
Code-derived domain-knowledge layer: A curated knowledge layer that captures the product's modeling vocabulary (T&M, ARR, retainer, MSP, co-sell, subcontract, rev-rec, commission) so Sage answers in the right terms.
Composite how-do-I-model questions: Handles cross-module questions like T&M plus multiple ARR licenses, subcontracted on vendor paper, or co-sell with partner-sold and vendor-sold.
Decision guides: Walks retainer vs MSP vs T&M, billable vs non-billable utilization, and similar trade-offs the data model actually surfaces.
Troubleshooting trees: Step-by-step diagnostics for margin not matching, rev-rec to QBO not posting, and commission calculating wrong. Names the screen and field to check at each branch.
Points to the right screen: Sage explains the answer and points you to the screen that holds the data. The click and the call stay with the human operator.
Graceful decline out of scope: Declines business-judgment and data-prediction questions cleanly, naming the human role that owns the call instead of guessing.
Privacy by design: No access to live business data. No access to source code. No internal identifiers in answers. Independently leak-tested. Powered by Claude with a per-org monthly USD cap.

Unified Approvals Inbox

One inbox for every approval routed to you, across deal, discount, payout, budget, time, and requirements approvals.

Per-approver routing: Each approval routes to your manager plus the role-holder, with admin backup when neither is available.
Covers every approval type: Deal-stage gates, quote discount approval, partner payout approval, project budget threshold approval, time-period approval, and requirements approval all land in the same inbox.
Inline actions: Approve, reject, or hold each item inline without leaving the inbox.
Append-only audit per action: Every approval action writes an audit row with actor, decision, and timestamp.
Approval handoff: Handoff routes the approval when the assigned approver is out.
Notification routing aligned: The inbox bell, the email notification, and the inbox itself stay aligned through shared routing.

Vision and Plan

Vision, core values, and the company plan, versioned and editable.

Vision statement: A single vision statement, editable in place.
Core values list: Core values as first-class records the org can edit and reorder.
Plan revisions with history: Each plan revision is preserved, so prior versions stay readable.
Tied to OMS goals: The plan links into the goal cascade so strategy connects to execution.

Accountability Chart

Seats with explicit function and accountabilities, mapped to holders. Org-tree view with the hierarchy.

Seat CRUD: Create and edit seats with function, accountabilities, and a place in the hierarchy.
Holders per seat: Assign one or more holders to each seat.
Org-tree visualization: The chart renders as an org tree so reporting lines stay legible.
Versioned: The accountability chart is versioned, so prior structures remain available.

Cascading Goals

Goals cascade across org, team, and individual with parent linkage and manual or computed RYG.

Three goal levels: Goals exist at org, team, and individual levels.
Parent linkage: Each goal links to a parent goal to build the cascade tree.
RYG status: Each goal carries a red, yellow, or green status, set manually or computed from underlying metrics.
Aligned with quarterly priorities: Goals connect to quarterly priorities so the cycle closes between strategy and ninety-day commitments.

Quarterly Priorities

Ninety-day commitments scoped to a quarter, aligned via a priority tree, linked to goals.

Ninety-day priority records: Each priority is a ninety-day commitment with owner and status.
Priority tree alignment: Priorities organize into a tree so dependencies and alignment are visible.
Linked to OMS goals: Each priority links back to a goal in the cascade.
Quarterly cycle CRUD: Quarters are first-class records that scope which priorities are in-flight.

Weekly Scorecard

Weekly metric grid with manual and computed metrics, green / red per week.

Weekly grid view: Metrics by week across the scorecard period.
Manual and computed metrics: Enter values by hand or pull them from a computed source.
Green / red status per week: Each metric, each week, is green or red against its target.
Trend per metric: A per-metric trend line shows the direction over the period.
Auditable: Edits to scorecard values write audit rows.

Operating Model

Vision and plan, accountability chart, cascading goals, quarterly priorities, weekly scorecard, issues, weekly team meeting, and confidential role-fit reviews. One connected module on the same system as your delivery and revenue data.

Vision and Plan: Vision, core values, and the supporting plan captured as a versioned record so the leadership story stays legible over time.
Accountability Chart: Seats by function with explicit accountabilities and a place in the hierarchy. Holders assigned per seat, with an org-tree view.
Cascading Goals: Goals at org, team, and individual levels with parent linkage. Manual or computed red, yellow, green per goal.
Quarterly Priorities: Ninety-day commitments scoped to a quarter, organized in a priority tree, and linked to the goals they support.
Weekly Scorecard: A weekly metric grid with green or red per metric per week. Manual rows entered by the owner, computed rows pulled from delivery, finance, and CRM data already in the system.
Issues list: An issues list that persists between meetings, so the same items do not get re-raised every Monday.
Weekly Team Meeting view: An assembly view that pulls the scorecard, priorities, and issues into one screen for the weekly team meeting.
Role Fit Review: Confidential role-fit reviews with the same privacy posture as performance reviews. The reviewee never sees the manager's draft or submitted review.
Permission-gated reports: Reports across the operating model respect role and team permissions. Aggregate counts do not leak rows the viewer cannot see.

Product Roadmap

A customer-facing roadmap your whole team helps build. Read-only roadmap by quarter, customer demand capture, and an org-admin view that aggregates demand into roadmap priorities.

Customer-facing roadmap: A read-only roadmap surface inside the app showing what is shipped, what is in build, and what is next. Quarterly horizon. No estimates the team has not committed to.
Want this voting: Customers click Want this on a roadmap item to express demand. Per-org vote count is captured so the same org cannot run up the score by clicking on more accounts.
Feature request capture: Customers submit feature requests from inside the product, anchored to the surface they are on, with description, the problem the request would solve, and an optional contact reply preference.
Admin demand triage at /admin/roadmap-requests: Org admins see the aggregated demand: vote counts per item, the open feature-request queue, and a triage workflow to accept, decline, or roll requests into a roadmap item.
Roadmap items as code-owned content: Roadmap items are owned in the product repo, not editable from a database admin surface, so the roadmap a customer reads is the roadmap the team committed to.
Standing test on roadmap content: A standing test checks roadmap entries for the project's brand pattern and required identifier shape, so a typo or stale identifier fails CI rather than ships.

Todas las capacidades de PartnerView, en un solo lugar.