# Who can license entitlement exception records? | SourceX

Canonical: https://refer.sourcex.si/questions/who-can-license-entitlement-exception-handling-records
Last updated: 2026-11-04

Introduce the CEO, who can authorize a licensing discussion and sign for the company, with the customer support director as sponsor and working contact. The support director knows where the plan, permission and ticket records live. Billing, identity and helpdesk administrators can describe their systems but cannot approve the use of what they hold. Counsel weighs customer contracts and personal data in identity logs. What can be licensed stays unknown until SourceX's rights review.

This decision tree is part of [exception handling records for AI agents](/guides/exception-handling-ai-agents-data). It answers one question for customer platform consultants: who can say yes to a conversation about entitlement exception history?

## Who keeps each entitlement record, and who does not decide

Entitlement history is spread across systems, and every system has a keeper. Running a system is not the same as owning its contents.

| Record set | Kept day to day by | What they can tell you | Can they authorize licensing? |
|---|---|---|---|
| Plan history, add-ons, renewals in billing | Billing operations or finance | Years covered, plan codes, how merges were handled | No |
| Contracts and order forms in the CRM | Revenue operations, account managers | Which features were sold under which contract | No |
| Group and app memberships in the identity platform | IT or identity administrator | How long events are kept, whether grants cite tickets | No; admin rights are not authority |
| Tickets, approvals and resolutions in the helpdesk | Support agents and team leads | Volumes, tags, how exceptions are approved | No |
| The exception process across all four | Customer support director | Where every link lives, and the gaps | Sponsor; rarely the final decider |
| Customer records as a company asset | CEO | Whether the company will discuss licensing at all | Yes; the CEO authorizes and signs |

The confusion is understandable. Okta's System Log records which user was added to which group, and Zendesk keeps a read-only audit of every ticket update, so the people who run those tools can see a great deal. Seeing records is not authority over them.

## The yes path: four questions in order

Work down the tree. The first person who answers yes to question 3 is your introduction; then check question 4.

1. **Does this person administer one system?** If yes, they describe it. Ask who runs the exception process across systems, and move on.
2. **Does this person own the exception process from complaint to resolution?** If yes, this is usually the customer support director. Ask them to sponsor the conversation and to name the decider.
3. **Can this person commit company information to an agreement?** If yes, this is your introduction: the CEO, or in an owner-run company the owner, who is usually the CEO.
4. **Does anyone above them need to consent?** A parent company, a board or a private equity owner may. After an acquisition, the acquired company's former owners may also have kept rights under the purchase agreement. Note it; SourceX will ask.

The common mistake is stopping at question 1 or 2 because that person is helpful and knows the systems best.

## Branches that need counsel or customer sign-off

Some entitlement records carry other parties' rights or legal duties. A partner flags these and stops; the company's counsel and SourceX's rights review decide.

| Situation | Why it matters | Who decides | Typical outcome |
|---|---|---|---|
| Customer contracts with data-use clauses | They may limit how account and usage data can be used | Company counsel | Excluded, restricted or included as agreed |
| Identity logs naming end users | Names, email addresses and user IDs can be personal data | Counsel and the privacy lead | Redacted or excluded before any scope is agreed |
| Records inherited in an acquisition | The purchase agreement may limit their use | Counsel | Depends on the agreement |
| Tickets quoting customer content | The customer may own what they pasted in | Counsel | Usually redacted |
| Accounts in dispute or under legal hold | Records may be frozen | Counsel | Left alone |

Where EU law applies, the GDPR defines personal data as any information relating to an identified or identifiable natural person, including by reference to a name, an identification number or an online identifier. Group membership events tied to named users fall comfortably inside that. This does not rule a company out; it means redaction and rights review come first. [Why data rights matter](/proof/why-data-rights-matter) explains how these checks shape scope, and [contract review workflows](/data-types/contract-review-workflows) covers how companies track the clauses involved.

## What stays unknown until SourceX's rights review

Even when the right executive agrees to talk, four things remain open:

- **Rights:** which record classes the company can license, given customer contracts and any acquisition terms.
- **Scope:** which products, years and record types are included.
- **Demand:** whether any buyer wants this data when SourceX reviews it. Programs can change; see [what happens if a SourceX pauses data sourcing](/questions/what-happens-if-the-buyer-pauses-a-program).
- **Terms:** any offer, payout and schedule.

A partner predicts none of these. The [worked entitlement case](/guides/entitlement-exception-handling-exception-examples) and the [system map](/guides/entitlement-exception-handling-records-across-systems) help a partner describe the records accurately without promising anything about them.

## The company baseline and the partner's paperwork

The software company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Partners sign the Channel Partner Agreement before submitting introductions. Credit goes to the first valid introduction within the 90-day window, recorded when the company submits a verified application, and one partner is credited per company. Partners never ask for or handle raw client records. More sector context is on the [software and SaaS industry page](/industries/software-and-saas).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When the customer support director has named the executive who can say yes and flagged any contract or privacy limits, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before making the introduction.

## Sources

- https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
- https://developer.okta.com/docs/reference/system-log-query/
- https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits/
- https://refer.sourcex.si/terms
