This page is part of the customer access review remediation guide. It answers one question: who can say yes.
The decision tree: five questions from first contact to signer
Answer in order. Each answer either moves you on or adds someone to the introduction.
1. Who runs the access review program for customer-facing systems? Usually the security operations head, sometimes the CISO. This is your first contact and sponsor. Go to 2.
2. Which legal entity controls the records today?
- The company itself: go to 3.
- A parent or acquirer (for example, after a closing that triggered a tenant merger): the authorizing CEO is the parent's. Add them and their counsel. Go to 3.
- A receiver, administrator or trustee: authority sits with them; see data access in receivership. Go to 3.
3. Do customer contracts limit how security and access records can be used?
- No specific limits found: go to 4.
- Limits or confidentiality commitments apply: general counsel or the privacy lead must clear the rights question before any discussion. Go to 4.
4. Do the records name employees or contractors? They almost always do: reviewers, owners, approvers. Privacy review applies to how employee information is handled, and de-identification is decided during SourceX's rights review. Go to 5.
5. Who can approve licensing company data, and does the board need to agree? The CEO. Some companies also need board sign-off for a data license; this explainer covers when. The CEO is the authorized contact your introduction must reach.
Roles at a glance: knowledge, ownership and authority
| Person | What they know or hold | Can they open a licensing discussion? |
|---|---|---|
| Security operations head | Systems, coverage, volumes, gaps, log retention | Rarely alone; best first contact |
| CISO | Customer security commitments, program history | No; can sponsor, with legal |
| Resource owners and managers who review | Their own decisions inside each review | No; they act within the program |
| GRC or compliance lead | Findings, statuses, audit requests | No; advises |
| General counsel or privacy lead | Customer contract limits, employee notices | Clears rights; usually not the commercial decision |
| CEO | Whether licensing fits the business | Yes |
| Identity consultant (you) | Technical access to one or both tenants | No |
The third row matters because access reviews spread decisions across many people. Microsoft Entra, for example, can assign reviews to resource owners, delegates, managers or the users themselves, in up to three stages. Hundreds of reviewers may appear in the records, but none of them owns the records or can license them.
Access is not authority: what the consultant can and cannot do
As the identity consultant, you may be able to open review campaigns, run reports or read audit logs. Administrators can generate review history reports for any date range in a few clicks. That ease is exactly why the line matters.
You can:
- describe, with the client's consent, what record classes exist, roughly how many cycles and findings, and which systems hold them;
- tell the security operations head that a licensing route exists and what SourceX does;
- introduce the sponsor and the authorized executive together.
You cannot:
- export, copy or summarize review decisions, findings or log lines for anyone outside the company;
- suggest that your access means the records are available;
- speak for the company on rights or price.
Why data rights matter explains what SourceX's rights review settles once the company is engaged.
Where sign-off stays open until SourceX's rights review
Some answers cannot be known by the partner or the company in advance:
- whether a buyer wants access review remediation records;
- what the rights review concludes about customer contracts and employee data;
- what must be removed or de-identified, for instance customer tenant names;
- whether the parent company or board must approve, if that is not already clear;
- what the company would be offered, if anything.
How the records join across systems, which affects what can be offered, is on the records across systems map. Unlike auditor-raised points on the management letter remediation page, access reviews are the company's own control, which usually simplifies ownership. For context on technology leaders in sponsor-backed companies, see the CIO in a private-equity-backed company and data quality due diligence.
Qualification facts to confirm first
- Records: review decisions, findings, change tickets and removal evidence exist for several cycles and can be linked at least by account.
- Control: the company or its parent holds rights to license them, subject to review.
- Authority: the CEO, who can approve a discussion, is named.
- Size and location: the introduced company needs 50+ full-time employees at peak (contractors excluded), a 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. The first valid introduction within the 90-day window is credited when the company submits a verified application; one partner is credited per company, and duplicates are reviewed.
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 tree ends at the CEO of the entity that controls the records, register as a partner, check the company against who qualifies and read the program terms before you introduce the security operations head and the decision-maker.