Partner requests
Platform-admin queue for triaging partner applications from the public Partners page — from New to Accepted or Declined.
Partner Requests is the platform-admin triage queue for applications to work with PulsVault as a partner. Each application lands here as a row you can open, read in full, and work through a short lifecycle. The page is admin-only; the management API behind it is gated to the admin role.
Where applications come from#
Applications are submitted on the public Partners page (/partners). The old early-access
address (/enterprise-contact) redirects there, and the Become a partner topic on the Contact
page links to it. The form is public, so treat name, email, company and website as claims.
Every new application is also emailed to the sales mailbox (leads@pulsvault.com), with the details and a link back to this screen. A mail outage never loses an application: it is saved first and the email follows.
Partner types#
The applicant picks the option closest to what they do:
| Type | Who it is for |
|---|---|
| Security governance & compliance consultancy | Advisers and auditors helping clients meet frameworks such as ISO 27001, SOC 2 or GDPR |
| Managed service provider | Teams that run security and identity for client organizations |
| Reseller or distributor | Companies that bring PulsVault to the organizations they already serve |
| Technology or integration partner | Products and platforms that work alongside PulsVault |
The Partner type filter above the table narrows the list to one of them, and the status toggle narrows it by lifecycle state. The list is paged on the server, newest first.
What an application contains#
| Field | Notes |
|---|---|
| Applicant | Name and email; open the application for a mailto link |
| Company | The company name, with its website (opens in a new tab) and country when given |
| Partner type | One of the four types above |
| Request | The first lines of "How would you work with us?", so you can scan the list; hover for the whole message, or open the application |
| Status | Current lifecycle state (see below) |
| Date | When the application was submitted |
Name (2–150 characters), work email, company (2–200), partner type and the message (30–4,000 characters) are required — lengths are counted without leading or trailing spaces, by the form and again by the server. Website, country and company size are optional. Refresh re-fetches the current page.
Working an application#
- Open Partner Requests and select Open on a New application.
- Read the details and the message in the side panel.
- Set the status to In review and add an internal note, then Save.
- Reply to the applicant by email, then set the final status with a note of what was agreed.
Triage lifecycle#
| Status | Meaning |
|---|---|
| New | Just submitted; nobody has looked at it yet |
| In review | Someone is reading it or talking to the applicant |
| Accepted | We agreed to work together |
| Declined | Not taking it forward |
Internal notes are for staff only and are never shown to the applicant.
If another admin saves the same application while you are editing it, your save is refused rather than overwriting theirs: the panel loads their version, keeps your draft on screen, and you save again once you have reconciled the two. Closing the panel with unsaved changes asks before discarding them.