Partner application
Start with a clear, reviewable application
The application collects the minimum evidence needed to assess fit, capability, conflicts and a first activation outcome. It can be reviewed before any authority is granted.
Use the common Nebulas sign-in. Access depends on active assignments.
What the application will request
Prepare organization and legal contact details, territory and customer profile, relevant software and integration capability, delivery and support capacity, portfolio conflicts, preferred contribution path and supporting evidence.
Minimum necessary detail
Provide evidence that helps a reviewer assess the proposed contribution.
Authorized contact
Use a person permitted to represent the organization.
The public page collects no application evidence. Starting or submitting does not create partner status, customer access or commercial rights.
Application sections
The journey is organized into organization, market and customer fit, capability, delivery and support, portfolio and conflicts, contribution path, obligations and review.
Progressive collection
Complete one bounded section at a time.
Evidence before claims
Support material capabilities with a reviewable reference.
The public page collects no application evidence. Starting or submitting does not create partner status, customer access or commercial rights.
How information is used
Application information is used to verify identity, assess fit and capability, resolve conflicts, manage review and, only after the required decisions, establish scoped program records.
No public application
Application evidence is not published by the Partner Hub.
Read the policies
Review the privacy policy and terms before starting.
The public page collects no application evidence. Starting or submitting does not create partner status, customer access or commercial rights.
Save, resume and correct
The authenticated onboarding will keep an authoritative application record so the applicant can resume, respond to requested changes and safely retry supported actions.
One common account
Partner intent does not create a separate account type.
Authoritative status
The Portal loads the server record instead of trusting a URL flag.
The public page collects no application evidence. Starting or submitting does not create partner status, customer access or commercial rights.
What happens after submission
A reviewer may request changes, approve or reject the application with recorded reasons. Submission or approval does not itself grant customer access or commercial authority.
Separate decisions
Agreement, enablement, partner authority and customer assignment remain explicit.
Scoped access only
An active partner sees only capabilities and customers separately assigned to it.
Application, approval, agreement, authority and customer assignment are separate controls.
Readiness check
Start when you can name the organization, authorized contact, customer situation, contribution, relevant capability evidence, delivery capacity, conflicts and a realistic first outcome.
Need clarification?
Contact Nebulas before starting if the applicable path is unclear.
Ready to proceed?
The secure handoff preserves only bounded journey context and creates no authority.
The public page collects no application evidence. Starting or submitting does not create partner status, customer access or commercial rights.
FAQ
What evidence is requested in the application?
Expect organization and contact authority, territory and customer fit, relevant software, integration, delivery and support capability, portfolio conflicts, obligations and a proposed first outcome. The public page collects no application evidence. Starting or submitting does not create partner status, customer access or commercial rights.
What happens after submission and how can changes be made?
The review may request changes, approve or reject with recorded reasons. The authenticated onboarding is designed for resume, correction and safe retry against the authoritative application record.
Does applying or approval grant customer access?
No. Customer administration requires a separate, explicit, active assignment and allowed capability. Application and approval do not grant it.
How are commercial terms, territories and support responsibilities decided?
They are defined for the applicable path, scope and evidence during review and in the relevant agreement. The public Hub publishes no amount, margin, commission, lead promise or service guarantee. The public page collects no application evidence. Starting or submitting does not create partner status, customer access or commercial rights.
How does an existing partner sign in or get support?
Use the common Nebulas sign-in shown on every Partner Hub page. The Portal exposes only active, authorized capabilities; use the published support channel for assistance.