Deal registration gives your partners a way to formally claim credit for a prospect they are actively working. When a partner registers a deal, your team reviews it, decides whether to approve exclusive protection on that opportunity, and — once approved — converts it into a tracked deal in PartnerOS. This process protects partners from channel conflict, encourages them to bring deals to you early, and gives your team visibility into the pipeline your partners are generating.Documentation Index
Fetch the complete documentation index at: https://docs.partneros.ai/llms.txt
Use this file to discover all available pages before exploring further.
Deal registration statuses
Every registration moves through a defined lifecycle. Understanding these statuses helps both your team and your partners know exactly where a deal stands.| Status | Meaning |
|---|---|
| Submitted | The partner submitted the registration; it is waiting for your team to begin review. |
| Under review | A team member has started evaluating the registration. |
| Approved (converted) | The registration was approved and converted into a tracked deal. An expiry date is set automatically. |
| Rejected | The registration was declined. The partner receives a notification with the reason if one was provided. |
| Expired | An approved registration was not converted to a closed deal before its expiry date. |
A registration moves to Converted automatically when it is approved — PartnerOS creates a matching deal record at the same time.
Submit a deal registration
Partners and internal users with the appropriate permissions can submit deal registrations.Go to Deal Registrations
In the left sidebar, click Deal Registrations. The table shows all existing registrations for your organization.
Select the partner
Choose the partner that sourced or is co-selling this deal from the Partner dropdown.
Enter the account details
Fill in the required fields:
- Account name — the prospect or customer organization’s name.
- Deal value — the estimated contract value in your organization’s currency.
- Expected close date — the date by which the deal is expected to close.
Add supporting context (optional)
Providing detail here helps reviewers make faster, more informed decisions:
- Customer contact name and email — the buyer-side contact.
- Business challenges — what problem the customer is trying to solve.
- Proposed solution — how your product and the partner’s capabilities address it.
- Partner value-add — the specific work or expertise the partner is contributing.
- Internal notes — information for your team only; not visible to the partner.
Review and approve incoming registrations
Admins and team members with deal-review permissions can approve or reject registrations.Filter to registrations awaiting review
On the Deal Registrations page, use the Status filter to show only Submitted and Under review registrations. The summary cards at the top of the page also show the current count awaiting review.
Open a registration
Click a row to open the registration detail panel. Review the account name, deal value, close date, partner tier, and any context the partner provided.
Approve or reject
Select Approve or Reject from the action menu.
- When you approve, PartnerOS converts the registration into a deal record and sets an expiry date based on your policy (default: 90 days).
- When you reject, enter a reason in the Decision note field. This note is included in the notification sent to the partner.
Extend an expiring registration (optional)
If an approved deal needs more time, open the registration and click Extend. PartnerOS extends the expiry date by the number of days configured in your policy (default: 30 days). Each registration can be extended up to the maximum number of times set in your policy (default: 2).
Deal registration policies
Your organization’s deal registration policy controls default timelines, notifications, and approval routing. To view or update the policy, go to Deal Registrations and open the Policy settings.Validity and extensions
Validity and extensions
- Validity period — how many days an approved registration stays active before expiring (default: 90 days).
- Partner notification before expiry — how many days before expiry PartnerOS alerts the partner (default: 14 days).
- On expiration — the action taken when a registration expires without converting (default: auto-expire and notify).
- Extension days — how many days each extension adds to the expiry date (default: 30 days).
- Maximum extensions — the maximum number of times a registration can be extended (default: 2).
Approval routing
Approval routing
- Approver role — the role responsible for reviewing registrations (default: opportunity owner).
- If unresolved — the fallback action when a registration sits unreviewed (default: route to partner manager).
- Approval happens in — whether approvals are managed in PartnerOS or your CRM (default: PartnerOS).
Notifications
Notifications
- Email notifications — enabled by default. Configure which groups receive each type of email (new submission, approved, declined).
- Slack notifications — optionally route notifications to a Slack channel.
- In-app notifications — enabled by default; team members see alerts in PartnerOS.
{{trigger.registration.accountName}} and {{trigger.partner.name}} to personalize messages automatically.Search and filter registrations
Use the toolbar controls on the Deal Registrations page to find specific registrations quickly.| Control | What it does |
|---|---|
| Search bar | Filters by account name |
| Status filter | Filters by Submitted, Under review, Approved, Rejected, or Converted |
| Partner filter | Shows registrations from a specific partner |
| Date range | Filters by submission date |
| Sort | Sorts by submission date, deal value, expiry date, or account name |