TL;DR: A SaaS partner certification program trains and tests the people at each partner, attributes every certification to the partner company, and turns the count into a tier a customer can check. Partner certification software has to issue certificates automatically from your LMS or CRM, keep them on your own domain, revoke them when a partner loses a tier, and let anyone verify them without calling you. TRUE Original issues partner certificates as blockchain-secured TRUE documents on your domain, from the TRUE dashboard, the REST API or Salesforce, and anyone can check one in TRUE Verify.
A partner certification is a credential a software company issues to a partner, or to the people who work at one, to confirm they have been trained and tested on its product. Most SaaS programs certify individuals first: the consultant, the developer, the sales engineer. The partner company then earns a tier, such as Silver, Gold or Platinum, from the number of certified people it employs.
Certified partners close more deals. When a prospect is evaluating implementation partners, a verifiable certification from the software vendor carries weight. The certificate is what a customer looks at when two implementation partners pitch for the same project. Both say they know the product. Only one may be able to show it. A buyer rarely asks the vendor's channel team to confirm a partner's status, so the proof has to sit in the certificate itself, one click or one QR scan away.
Certification also changes how partners behave. A consultant who spent weeks earning a certificate has a reason to stay in the ecosystem. When that consultant adds it to a LinkedIn profile, the product's name travels into a professional network the vendor's own marketing never reached.
Build a SaaS partner certification program in four steps: define the tiers and what earns each one, move training and assessments into an LMS, issue a certificate automatically when a partner passes, and let customers verify that certificate on your own domain. Most programs get there in stages. Each stage holds until the partner count outgrows it.
A shared sheet tracks who completed training. Someone in partnerships builds each certificate in a slide or design tool and emails it as a PDF. It works at ten partners. At fifty, the person who owns it spends whole days on it, names get misspelt, and an expired certificate keeps circulating because nothing can withdraw it.
Training moves into an LMS such as Canvas, Moodle or Learnster, and completions are tracked automatically. The certificate is still a PDF. When it breaks: Around 100 to 200 partners. A partner can forward it, edit it or keep showing it after the tier has lapsed, and the vendor never learns how often it is opened or shared. Training is automated. Credentialing is not.
When a partner passes the final assessment, the LMS or CRM calls the certificate platform's API and a blockchain-secured certificate is issued without anyone touching it. The certificate opens on the vendor's own domain, carries a QR code and is tied to the partner's record in the CRM. TRUE Original issues these certificates straight from Salesforce: a record-triggered flow calls TRUE when the partner's record reaches the state you choose, and the person named on the record receives a blockchain-secured certificate. A tier upgrade issues a new certificate on its own, and a lost tier is revoked the same day. The process is the same at 200 partners as at 20,000.
Certified partners share their certificates on LinkedIn, and every shared link opens on the vendor's domain. The compounding effect: Every partner who shares a credential exposes your brand to their network. For a company with 500 certified partners, each sharing to an average LinkedIn network, that's hundreds of thousands of professional impressions, all trusted, organic, and free. TRUE customers have generated over 100 million marketing impressions from documents issued through TRUE Original. The mechanics are in your certificate is a marketing channel.
Attribute each certification to the person who earned it, then link that person to the partner company's account, so the partner's tier counts its certified people. Microsoft runs its partner program this way: each certified person links a Microsoft Learn profile to the partner organisation in Partner Center, and the organisation gets the credit. In a SaaS program the partner account usually lives in the CRM, so the certificate should be issued from that record. This article covers partner programs at SaaS (software as a service) companies, not the partner certification run by the analytics company SAS Institute.
Microsoft's documentation gives the purpose in one line: after linking, "your organization gets credit for the trainings, certifications, and other learning credentials that you complete" (Microsoft Learn, Partner Center documentation, updated September 2026). According to the same page, linked certifications appear in Partner Center within 10 days, a person can link or unlink up to three times per year, and each link starts a 30-day wait before the next. Linking to a new company automatically unlinks the person from the previous one.
"These limits help maintain an accurate association of employment and certifications in Partner Center." Microsoft Learn, Partner Center documentation, 2026
A SaaS vendor can copy the model without Microsoft's overhead. Store the partner account ID with every certified person. Put the partner company and the tier on the certificate, next to the person's name. When a consultant leaves a partner, the personal certificate stays with the consultant and the partner's count drops by one. When a partner loses a tier, revoke the tier certificate.
TRUE Original handles the issuing end of that model. A record-triggered flow in Salesforce calls TRUE when a training record or a partner status reaches the value you choose, and TRUE issues the certificate to the person named on the record, with the name and the credential taken from Salesforce itself. You decide which fields the certificate carries, so the partner company and the tier can sit on it. Nothing has to be installed from the Salesforce marketplace; the setup is described on the Salesforce certificate integration page.
The certification program that earns the most trust is the one whose certificates a customer, a partner or a regulator can check without asking the issuer. That takes a record that shows whether the certificate was changed, a status that shows whether it was revoked or has expired, and an address that shows who issued it. TRUE Original gives partner certificates all three: a fingerprint on a public blockchain, a live status the issuer controls, and the issuer's own domain. ISO 27001 and SOC 2 answer a different question: they certify a company's information security, not the people at its partners.
Trust in a certification program for people also rests on who runs it. ISO/IEC 17024 is the international standard for bodies that certify persons, and according to the International Accreditation Service, accreditation to it "builds trust with employers, industry regulators, and consumers." Whatever standard a program follows, a certificate issued through TRUE Original can be checked by anyone in TRUE Verify, free and without an account.
Checking is where trust usually fails. Prospects Luminate, part of Jisc, reported in November 2025 that only 52% of large businesses verify all academic credentials and that 45% uncovered false qualification claims, in YouGov research among more than 500 HR decision makers (Prospects Luminate, 2025). Partner tiers work the same way. A check that takes a phone call does not happen. A check that takes a QR scan does.
The blockchain record does the tamper-proofing. A PDF "Gold Partner" certificate can be edited to say "Platinum" in thirty seconds. A TRUE document cannot be changed without the change showing, because its fingerprint is anchored on a public blockchain at issue. The US National Institute of Standards and Technology describes the property in its Secure Hash Standard: "Any change to a message will, with a very high probability, result in a different message digest." (NIST FIPS 180-4, 2015)
TRUE Original uses several public blockchains, among them Ethereum and Polygon, and a customer who wants a specific chain can have it. The record outlives the systems around it. A tier certificate issued today stays checkable after a CRM migration, a rebrand or a change of partner manager. Anyone can paste a certificate URL, document ID or PDF into TRUE Verify and get a security level rating in seconds, free and without an account.
Partner certification software should issue certificates automatically from the LMS or CRM, publish them on the vendor's own domain, make tier status impossible to change unnoticed, revoke a certificate the moment a partner loses it, and report how each certificate is viewed, shared and verified. TRUE Original is built to do each of these.
Manual certificate creation does not scale. The software has to issue when your training platform, CRM or own workflow says so. The TRUE Original REST API has five endpoints (Issue, Preview, Templates, Content and Issued) and a Postman collection to test them before anything is connected. Teams integrate it in hours, not weeks. TRUE also issues from Canvas LMS, Moodle, Learnster and Salesforce, and from the TRUE dashboard for teams that issue by hand.
Partner certificates belong on your domain, such as certs.yourcompany.com. The certificate carries your brand and your address, so a customer who clicks it lands somewhere they recognise. Every certificate can become an indexed page on your domain, building your domain authority. Issue 1,000 certificates and you have 1,000 new pages. Platforms that host credentials on their own domain capture this value for themselves. Your certificates, your partners, your content: indexed on someone else's domain. More in custom domain certificates.
A partner should not be able to claim a tier it has not earned. TRUE Original anchors each certificate on a public blockchain and gives it a QR code and a verification link, so a customer confirms the tier with a scan instead of an email to your channel team. A separate template per tier (Silver, Gold, Platinum or your own names) makes the difference visible at a glance, and the API issues the right template for each tier.
A tier that can be lost has to be revocable. TRUE Original revokes a certificate from the dashboard or through the API, and anyone who opens its link or scans its QR code sees the current status. The original issue stays recorded on the blockchain, so revocation changes the certificate's status and leaves its history intact. Expiry is different: an expiry date is set at issue and ends a fixed term, while revocation withdraws a certificate early because the basis for it no longer holds. Certificate expiry and renewal management covers both.
If sharing a certificate means downloading a PDF, writing a post and attaching a file, most partners will not bother. TRUE Original documents are animated, branded pages that go onto a LinkedIn profile in one click, and the shared link leads back to your domain. The steps are in how to add a digital certificate to LinkedIn.
A partner manager needs to know which partners opened their certificate, who shared it and where, how often customers verified it, and which tiers draw the most attention. TRUE Original tracks when, where and by whom documents are opened and shared. The program can then be reported to leadership as a channel instead of a cost.
A SaaS company should choose partner certification software that lets a customer verify a partner's tier without contacting the vendor, keeps every certificate on the vendor's own domain, and issues and revokes from the systems the company already runs. TRUE Original is partner certification software built that way. Partner certificates are blockchain-secured TRUE documents on your domain, issued from the TRUE dashboard, the REST API or Salesforce, revocable at any time and checkable by anyone in TRUE Verify.
TRUE Original was founded in Sweden in 2020 and is based in Stockholm. It has issued over 900,000 documents for more than 200 issuers, with customers in over 15 countries, and it is Cyber Hygiene Certified by OneMore Secure. A partner program on TRUE runs on the same platform as diplomas, licences and memberships, which is why the record is built to last for years and not for one campaign.
Connect them with one trigger per system: the LMS issues on course completion, the CRM issues or revokes on a tier change, a CSV batch upload handles cohort renewals, and a structured email covers teams without developers. TRUE Original supports all four triggers. Most programs start with one and add the next when they need it.
Your LMS tracks training completion. When a partner passes the final assessment, a webhook fires to your credential platform's API. The credential is issued automatically, and the partner receives it via email within seconds. No one in partnerships has to know it happened. Works with: Canvas LMS, Moodle, Learnster, and any LMS that supports webhooks or completion events.
A partner reaches its revenue target, Salesforce moves it to Gold, and the API issues the Gold certificate. The same flow can revoke the Silver one. Works with: Salesforce, HubSpot, custom CRMs with API capability.
For programs that certify in cohorts (quarterly assessments, annual recertifications, or event-based certifications), CSV batch upload handles hundreds or thousands of credentials in one operation. Expired certificates can be revoked the same way.
For pilots and small programs, send TRUE a structured email with the recipient's details. The certificate is issued and delivered without touching the dashboard or the API.
Partner certificates become a marketing channel when partners share them and every shared link opens on the vendor's own domain. A certificate in someone's inbox does nothing. The same certificate on LinkedIn, on the partner's website and in an email signature puts the vendor's name in front of buyers each time someone sees it.
Design decides whether partners share. Use your brand colours, a clear tier name and a layout a partner is proud to post. After issue, send a congratulations email with a one-click LinkedIn link and a suggested caption, and name the most active sharers in your partner newsletter. Certificates that companies want to show get seen: Great Place To Work issues its certifications through TRUE Original, and close to a thousand of them have been viewed well over a hundred thousand times (Great Place To Work case).
Scale makes the effect measurable. Bank of Georgia has issued over 26,000 blockchain-secured documents through TRUE's automated API pipeline. Across all issuers, TRUE documents have generated over 100 million marketing impressions. The organisations that figure out how to turn those credentials into marketing assets are the ones whose partner programs grow fastest.
Launch a partner certification program in four weeks: define the program in week one, set up the certificate platform in week two, pilot with existing partners in week three and roll out in week four. The first version does not need to be perfect. It needs a foundation that does not have to be rebuilt at 500 partners.
Week 1: define the program. Map the tiers, the training and assessment behind each, the renewal cycle, and how certifications attribute to partner accounts. Decide which LMS and CRM fields drive issuing.
Week 2: set up the platform. Connect your custom domain, design a certificate template per tier and choose the trigger: API, LMS, Salesforce or email.
Week 3: pilot. Issue certificates to 20 to 50 current partners. Ask them about the design, the delivery email and the sharing flow.
Week 4: launch. Roll out to every partner. Watch sharing and verification, then adjust templates and messages on real data. The first customer who scans a partner's QR code instead of emailing your channel team is the sign the program works.
A partner certification program is how a software company trains, tests and certifies the people at its partner companies, and grants each partner a tier based on its certified people. Customers use the certificates to check which partners know the product.
Attribute each certification to the person who earned it and link that person to the partner company's account in your CRM, so the partner's tier counts its certified people. Microsoft's partner program works the same way: a certified person links a Microsoft Learn profile to the partner organisation in Partner Center, and the organisation gets the credit.
The program whose certificates anyone can check without asking the issuer. TRUE Original gives partner certificates a fingerprint on a public blockchain that shows any change, a live status that shows revocation, and the issuer's own domain.
Partner certification software issues, hosts, revokes and verifies the certificates in a partner program, usually triggered from an LMS or CRM. TRUE Original is partner certification software that issues partner certificates as blockchain-secured TRUE documents on the vendor's own domain, from the dashboard, the REST API or Salesforce.
A customer scans the QR code on a TRUE Original certificate or opens its link, which shows the certificate on the issuer's own domain with its current status. Anyone can also paste the certificate URL, document ID or PDF into TRUE Verify for a security level rating, free and without an account.
The issuer revokes the certificate from the TRUE dashboard or through the API, and anyone who opens the link or scans the QR code sees that it has been revoked. The original issue stays recorded on the blockchain, so revocation changes the certificate's status, not its history.
No. ISO 27001 and SOC 2 certify a company's information security, while a partner certification confirms that the people at a partner have been trained and tested on a vendor's product. TRUE Original issues partner certificates that anyone can check in TRUE Verify, free and without an account.
Microsoft Learn, Link your Microsoft Learn profile and Skilling Hub account to Partner Center, updated 28 September 2026.
Prospects Luminate (Jisc), Matthew West, article on degree fraud and what employers can do about it, luminate.prospects.ac.uk, November 2025.
National Institute of Standards and Technology, FIPS 180-4, Secure Hash Standard, August 2015.
International Accreditation Service, ISO/IEC 17024 Personnel Certification Bodies Accreditation, checked October 2026.
Every organisation we work with started with the same question. Give us thirty minutes and we will show you what your own documents would be worth.
Book a callNot sure where to start? Let us help!
Trusted by leading organisations worldwide
