Decide whether an investor gets ongoing access to your data, and to which parts.
A data access request is different from a report request. A report is a
point-in-time answer you assemble and send; data access is a standing
permission that lets an investor read specified data as it changes.Because it persists, it deserves a slower decision than a report request does.
Pending requests are listed with who asked and what they asked for. Nothing
is granted until you act; a request sitting unanswered gives no access.
The Data Access page, where investor requests wait for your decision.
2
Read the scope, not just the name
The request names specific data rather than asking for everything. Check
what is actually being requested against what that investor needs; the two
are not always the same, and narrowing is a normal response rather than an
unfriendly one.
3
Approve or deny
Approving grants access to the named scope. Denying closes the request. In
either case the investor sees the outcome in their own view.
If a request is broader than you want but the relationship is one you
value, deny it and ask them to request a narrower scope. That is a cleaner
outcome than approving something you will want to revoke later.
Approval is not permanent. Access granted through this flow can be withdrawn,
and doing so stops future reads, but it does not retract data the investor has
already seen or reports they already hold. Treat the decision as one about what
they see from now on rather than one you can fully undo.
Access is read-only in every case. An investor with data access cannot change
your metrics, edit your reports, alter your connections, or see anything outside
the scope you approved.
