Fundraising Operations
Protect Equity and Compensation Records With a Clear Access Map
Map equity-data access to the task someone needs to perform, not their curiosity or seniority.
What you will learn
- Map a legitimate task to the minimum records and fields needed.
- Separate individual, operational and external sharing scopes.
- Review access without exposing real employee records during testing.
Protect equity and compensation records by asking what task the recipient needs to perform and which information that task actually requires. Give access to the minimum appropriate material, identify its owner and revisit it when the work or relationship changes.
Start with the task, not the job title
NIST defines least privilege around the minimum privileges and resources needed for assigned tasks. That principle is useful for sensitive equity records: a recruiter, manager, administrator and adviser can need different information even when they all contribute to one hiring process.
The map below is an original planning framework, not a legal access determination, a compliance certification or a claim about controls in any particular software. Actual permissions and confidentiality obligations need their responsible owner.
Build a task-to-record access map
Original equity-data access planning map
| Recipient and task | Minimum proposed scope | Avoid sharing by default | Review trigger |
|---|---|---|---|
| Employee reviewing own award | Their relevant packet and explanation route | Other employees’ awards or company-wide compensation | Award changes or employment changes |
| Recruiter communicating an approved offer | Approved recipient-facing summary | Full cap table and unrelated grant history | Offer completes or role changes |
| Manager preparing a role proposal | Required role context and authorized proposal inputs | Unrelated personal tax or compensation records | Proposal decision or reassignment |
| Equity administrator maintaining records | Authorized operational source packet | Unnecessary personal attachments | Responsibility or access changes |
| Adviser reviewing a specific case | Approved case-specific documents | Unrelated records from the full employee population | Case completion or scope change |
| External investor reviewing an approved summary | Approved aggregate or specifically authorized material | Identifiable employee detail without a reviewed need | Diligence scope or recipient changes |
The same person can have more than one legitimate task. Record each scope deliberately instead of using the broadest possible access for every activity.
Write a sharing brief before granting access
- Purpose: What question or decision does this material support?
- Audience: Who exactly receives it, including forwarded or external access?
- Fields: Which identifiers, quantities and terms are necessary?
- Authority: Who can approve this scope and any exception?
- Duration: When should the owner review continued access?
- Evidence: How will the owner check what the recipient can actually see?
Unknown recipients and unrestricted public links are not equivalent to a named review group. An expiry setting, if available, does not remove the need to confirm the initial scope.
Use a safe test, not a real employee’s record
For a controlled check, create a harmless sample packet and an authorized test recipient. Verify the intended view through the actual sharing mechanism, then confirm unrelated sample material is not exposed. Do not impersonate an employee or use real private compensation data as a testing convenience.
Record both permitted and denied cases. A link opening for the owner does not prove the recipient sees the right scope; a screenshot of a settings page is not the same as a recipient readback.
Exercise: remove unnecessary fields
A recruiter needs to send approved terms to one candidate. The proposed attachment contains the candidate’s summary plus every employee’s awards, personal addresses and tax identifiers. What is the narrower output?
Example answer: An authorized candidate-facing summary with only the approved terms and necessary recipient details. Route questions about what can be disclosed to the responsible owner. Do not copy the whole file into an email and assume a confidentiality footer fixes the excess.
Keep document control and product claims honest
The ICO’s own document-control policy offers a useful example of traceable versions, but it does not certify your access model. Review both the scope of a share and the version being shared.
For external materials, the public pitch-deck redaction lesson addresses permanent removal of sensitive content. This lesson instead owns internal and case-specific access planning.
Use Finta Documents only within your verified authorization and sharing process. Do not assume a marketing description establishes field-level equity permissions, a secure data-room configuration or compliance for a specific record set.
General education with fictional examples, not individualized legal, tax, valuation or investment advice. Have the appropriate professional review decisions affecting actual awards or transactions.