Referral Program Submissions Open to Enterprise Identity Platforms

TechAmerica.ai is opening its referral section to enterprise identity platforms. Vendors that sell single sign-on, multifactor authentication, user lifecycle management, privileged access or identity governance, and that reward resellers, managed service providers, consultants or publishers for new customers, can now submit their programs to our editors.

Nothing here is an offer. TechAmerica.ai has no partnerships, sponsorships, affiliate approvals or discount codes with identity vendors. This is an editorial guide to how partner economics work in identity and access management, followed by what we need from vendors who want their programs reviewed.

Why identity deserves careful scrutiny

Identity systems decide who can get into everything else. A company's email, finance tools, source code and customer data all sit behind the sign-on and access policies these platforms enforce. When a recommendation for an identity product is shaped by a commission, the stakes are higher than for most software, because a poor fit can leave gaps attackers exploit.

Our security coverage regularly reports breaches that begin with stolen credentials or misused access. This section looks at a quieter part of the same story: how identity vendors pay the partners who sell, deploy and manage their products, and whether those arrangements are explained honestly.

What these platforms do and how they are sold

• Workforce single sign-on that lets employees reach many applications through one login, usually with SAML or OpenID Connect.
• Multifactor authentication, including push approvals, hardware keys and passkeys.
• Lifecycle management that creates, changes and removes accounts automatically as people join, move and leave, often through SCIM provisioning.
• Privileged access management for administrators and sensitive systems.
• Identity governance for access reviews, certifications and audit evidence.
• Customer identity for sign-up and login in a company's own apps.

Most organizations already have some identity infrastructure, often a directory that has grown over many years, plus a patchwork of passwords for applications that never joined single sign-on. Projects therefore start with discovery and clean-up rather than a fresh install. That work is where partners earn much of their revenue, and it is also where they gain detailed knowledge of a client's environment.

Pricing is typically per user per month, with modules sold separately or bundled into suites. Customer identity is more often priced by monthly active users. Enterprise deals are usually annual or multiyear, and implementation can involve directory clean-up, application integrations, policy design and migration from an older system.

Who evaluates the purchase

Identity decisions usually involve IT operations, the security team and, in larger companies, compliance and audit staff who need evidence of who had access to what. Human resources often has a stake too, because hiring and departures drive account creation and removal. A partner who understands all of these groups can shorten a sale considerably, which is one reason vendors pay well for partners with real identity expertise.

A channel-heavy market

Identity has long relied on resellers, distributors, managed service providers and security consultancies. Many organizations buy security software through a trusted IT provider that bundles licenses with setup and ongoing support. For smaller businesses, the managed service provider may effectively be the identity administrator. That makes partner programs central to how these products reach customers.

Buyers should also expect implementation to change behavior across the company. Employees will sign in differently, administrators will lose some of the informal access they relied on, and help desks will field new kinds of requests. Partners who plan for that change management tend to deliver deployments that last.

Program models you will see

Reseller programs

Resellers buy licenses at a discount and sell them to customers, usually with deal registration to protect opportunities they bring. As of October 2026, 1Password's published partnership agreement defined resellers as partners that market and sell its services without altering them, allowed partners to set their own prices above a minimum set by the company, and incorporated a data processing addendum covering customer personal data.

Managed service provider programs

MSP programs let IT providers deploy and run identity tools for many client organizations from a multi-tenant console, often with monthly per-seat billing that tracks how many users the MSP manages. The same 1Password agreement described a separate MSP track with a monthly net seat fee and a rule against delivering services through sub-distributors.

Distributors

In many regions, vendors sell through distributors that onboard, finance and support smaller resellers. Distributors handle credit, billing and local logistics, and they often run their own enablement for partners. For readers, the practical effect is that the price and terms a customer sees may reflect several layers of margin, and support can come from a partner rather than the vendor.

Referral partner programs

Consultancies and advisers who prefer not to resell can register opportunities and receive a referral fee when the vendor closes the deal directly. These programs suit firms that want to stay vendor-neutral in billing while still being compensated for introductions. Clear rules on deal registration and conflict with the vendor's own sales pipeline are essential.

Affiliate programs

Vendors with self-service business plans, particularly password managers and small-business access tools, run affiliate programs for publishers. Keeper's partnerships page, viewed in October 2026, described separate consumer and business affiliate tracks run through different networks, with commissions on sales and a cost-per-lead payment for business leads that start a demo or trial. NordPass's affiliate page, seen the same month, listed distinct commission types for consumer and business sign-ups and a fixed cookie window.

Affiliate content about identity tools tends to cluster around comparisons and best-of lists aimed at small businesses. Those articles can be useful, but they rarely test enterprise features such as provisioning, delegated administration or audit reporting. Readers evaluating identity for a larger organization should treat them as a starting point rather than a verdict.

Technology integration partners

Software companies that integrate with an identity platform's app catalog join technology programs. Their reward is distribution and credibility rather than commission. Readers should remember that a catalog listing confirms an integration exists, not that it has been independently tested for every use case.

The partner access problem

Identity partners often hold administrative rights over a client's tenant. An MSP may manage policies for dozens of companies from one console. That arrangement is efficient, but it concentrates risk: if the partner's own accounts are compromised, every client could be exposed.

The FTC's security guidance for businesses stresses limiting third-party access to what a job requires, protecting administrator accounts with strong authentication, making remote access temporary and monitored, and verifying that service providers keep their security commitments. Those principles apply with extra force when the provider controls sign-on itself.

Security agencies have warned for years that attackers target IT service providers precisely because one breach can open many doors. An identity partner program that rewards rapid growth in managed tenants without matching security expectations creates an incentive mismatch that customers end up absorbing.

What good programs require of partners

• Phishing-resistant multifactor authentication on all partner administrator accounts.
• Separate, named admin accounts rather than shared credentials.
• Scoped delegated administration so partners see only the tenants and settings they manage.
• Audit logs visible to the client.
• A defined process for removing partner access when a contract ends.
• Incident notification duties if a partner suspects compromise.

Vendors that publish these expectations give customers a basis for holding partners accountable. Programs that say nothing about partner security leave a gap that buyers should ask about.

Claims, certifications and disclosure

Identity marketing is full of compliance language: audit reports, certifications, government authorizations and standards alignment. Partners should repeat only what the vendor states publicly for the specific product and plan being sold. 1Password's agreement, for instance, barred partners from making functionality or performance claims beyond approved materials and from publishing competitive benchmarks without approval.

The FTC's Endorsement Guides apply to identity products as they do to any other. A security blogger or MSP who earns commission on a recommendation should disclose that relationship clearly, near the recommendation, in words readers understand. Reviews of identity tools on software review sites should disclose incentives, and the FTC's consumer reviews rule bars conditioning those incentives on positive sentiment.

Employee advocacy is common in security companies, where staff post product tips and threat research. When those posts promote the employer's identity product, the FTC expects the employment relationship to be disclosed in the post itself. A job title on a profile page is not enough on its own, according to the agency's guidance.

Security of the referral itself

Referral programs in this sector should avoid asking partners to collect sensitive information about a prospect's security setup through unprotected forms. A referral needs a contact and a company, not a list of the prospect's applications, admin names or known weaknesses. Detailed technical discovery belongs in a properly protected sales process.

Terms worth checking

1. Deal registration. How opportunities are registered, how long they stay protected and how conflicts with direct sales are resolved.
2. Margin versus fee. Whether partners resell at a discount, receive a referral fee or can choose.
3. Minimum pricing. Some agreements set floors partners cannot undercut.
4. Seat true-ups. How growth in users during a contract affects partner revenue.
5. Export and trade controls. Identity software is security software, and agreements often require partners to comply with trade control laws and screen customers.
6. Data processing terms. Whether a data processing addendum covers partner handling of customer personal data.
7. Termination. Notice periods and how existing customers are handled when a partner leaves.

What a strong program page discloses

The clearest identity program pages separate each partner type and state, for each one, how partners are paid, how deals are registered and protected, what security standards partner administrators must meet, which products are included and which regions are covered. They also say how pricing floors work and whether the vendor may sell directly to a partner's customers. When those items are public, partners can compare programs on substance rather than marketing.

Pages that lead with a large commission figure but bury the conditions, or that describe partner security only in general terms, tell us less. We will ask vendors for the missing pieces before writing.

Questions buyers should ask an identity partner

Companies relying on a reseller or MSP for identity can ask a few direct questions before signing. They help reveal both commercial incentives and operational risk.

1. How are you paid for this product, and do you earn more from one identity vendor than another?
2. Which of your staff will hold admin rights in our tenant, and how are their accounts protected?
3. Will we see audit logs of everything your team changes?
4. How quickly can we remove your access, and what happens to our configuration if we leave you?
5. Which certifications or audit reports cover the exact product and plan you are proposing?
6. Who do we call during a sign-on outage at night: you or the vendor?

A reliable partner will welcome these questions. Vendors can help by giving customers direct visibility into partner access, so trust does not depend solely on the partner's own reporting.

How to submit an identity program

Send your program through our contact page with the official program URL, governing terms and effective date; the partner types you support; the reward or margin structure; deal registration rules; partner security requirements; geographic coverage; and a named contact. If some details are available only to signed partners, explain what they cover and whether a public summary exists.

It also helps to tell us how your program treats partners that sell competing identity products. Some vendors expect a degree of exclusivity at higher tiers, while others accept that MSPs support several platforms. Either approach can be reasonable, but readers weighing a partner's advice benefit from knowing which applies.

Editors compare every submission with the vendor's public pages and report figures only when they appear there when checked. We may ask follow-up questions about partner access and claims. Sending a program is a request for consideration, not a booking: we can decline coverage, and we never accept payment for review or placement.

A market in motion

Standards are shifting as well. Passkeys and other phishing-resistant methods are replacing passwords and one-time codes in many deployments, and partners who recommend identity products need to keep their knowledge current. Programs that tie partner tiers to certifications on current methods give customers some assurance that the person advising them understands the technology.

New entrants are pushing identity toward AI agents and machine identities, as our report on Oak's AI-native identity platform describes. Partner programs will change as products do. When your tiers, margins, MSP pricing or registration rules change, send the update with the new URL and effective date so our coverage stays accurate.