After your first paid-via-Atlassian (PvA) app is approved and published, you can access Partner Central and request internal use license (IUL) benefits.
Partner Central provides access to the Partner Portal, Partner Business Center, Partner Service Desk, and Atlassian University learning management system. Available resources depend on your account and roles.
Before you begin
Confirm that:
Your organization has at least one approved and published PvA app on the Atlassian Marketplace.
You use a business email address on your organization's approved domain. Public or generic email domains, such as Gmail, Yahoo, and Hotmail, aren't accepted.
All business domains your team uses are registered on the partner account before users from those domains join.
You know your organization's designated Partner Principal. This is usually the primary contact selected from your Marketplace team contacts. They help coordinate access and onboard additional users.
Publishing your first PvA app enables initial partner account setup. It doesn't automatically give every employee access to partner systems.
Sign in with your Atlassian account. If you don't have an account, follow the onscreen instructions to create one using your business email address and verify your email.
On the home page, find the partner account linked to your business email domain.
Select Join next to the correct account.
Select roles that match your responsibilities. During onboarding, select the Learner persona for Marketplace Partner access.
Enter the required profile details to complete onboarding.
Explore the apps and resources available for your account and roles.
Marketplace Partners must select the Learner persona. Choosing a different persona can delay access or leave you without the tools you need.
Request internal use license benefits
Internal use licenses are a Partner Program benefit for using eligible Atlassian products within your organization. Your available entitlement depends on your partner account structure and applicable program rules.
Complete your Partner Central onboarding and confirm that you're associated with the correct partner account.
If your organization also operates as a Solution Partner, confirm the account structure with your Partner Principal before requesting benefits.
Account structure
Access and IUL handling
Separate Marketplace Partner and Solution Partner accounts
Each account has its own IUL entitlement and revenue association. Users on one account don't automatically receive the other account's benefits. Separate IUL budgets can't be combined or shared as a single budget.
Hybrid account combining Marketplace and Solution Partner operations
This is the default combined setup. Approved users can access permitted resources across both businesses. Revenue visibility and IUL budgets are managed within the hybrid structure, subject to program rules and permissions.
A contact can be associated with only one organization or account structure at a time for partner access. Decide whether to keep the businesses separate or combined before onboarding users.
Troubleshoot access
If you can't join your organization or access the expected resources:
Your account isn't listed: Ask your Partner Principal to confirm that your business email domain is registered on the correct partner account. If your company uses multiple domains, each domain must be added before its users join.
Your company is already an Atlassian customer: A customer-only account association can block partner access. Your organization must be associated with the correct partner account.
You're missing Marketplace Partner tools: Confirm that you selected the Learner persona during onboarding.
You're linked to another partner account: Check your association with your Partner Principal. A single contact can't access separate Marketplace Partner and Solution Partner entitlements through one account association.