Pipelines in Partner Fleet’s Developer Portal guide integration partners from application to launch. Here’s how to set yours up quickly and effectively.

1. Prep Before You Build

Configure these three areas first:

Roles & Permissions - Control what partners can see at each stage.
Folders & Resources – Share the right docs and tools at the right time.
Forms & Applications – Collect info for qualification, scoping, and launch.

💡 Tip: Map your ideal partner journey first so stages match access and resources.

2. Align Roles with Pipeline Stages

Early Stage (Steps 1–3) – Limited access; basic program info only.
Build Stage (Step 4) – Access to technical folders, API docs, dev resources.
Fully Fledged Partner (Steps 7–8) – Full access to marketing toolkits, co-sell resources, marketplace listing creation.

3. Example: Developer Portal Pipeline

Step	Stage	Goal	Example Automation
1	Application Received	Capture interest	Auto-confirm email
2	Pre-Qualification	Check fit	Trigger review task
3	NDA Execution	Secure confidentiality	Auto-send NDA + advance stage
4	Technical Scoping	Define requirements	Assign tech contact + share docs
5	Development in Progress	Build integration	Send updates via app revision
6	Testing & QA	Validate integration	Go/No-Go workflow
7	Launch Approval	Confirm readiness	Notify marketing/legal
8	Go Live & Promotion	Launch + promote	Auto “Congratulatory” email

4. Expand for Other Partner Types

You can create unique pipelines for Service Partners, SIs, ISVs, or any other partner type — each with tailored stages, access, and resources.

5. Need Help?

Check out the full Developer Portal Pipelines guide for detailed setup instructions, automation ideas, and best practices.

Or reach out to your Customer Success Manager for personalized guidance.