The LP portal

Overview

The LP portal is a distinct, mobile-responsive surface from the GP admin interface — not a cut-down view of the same screens. It is where LPs interact with NAVdryx directly, from the day they subscribe, and it is treated as production-grade rather than a later phase of the platform.

What an LP sees

An LP’s dashboard shows what it committed, what has been called, what remains uncalled, distributions received, current NAV, and its MOIC and IRR. From there, an LP can reach its capital activity, statements, delivered documents, tax documents, consents, messages, and data room, along with three pages about its own account: Communications (notification settings and the security phrase), Emails we sent you (verification codes), and Security (how to recognize a genuine message).

Deliveries and read receipts

Statements, reports, K-1s, and capital call and distribution notices reach an LP as deliveries: a copy placed in that investor’s portal, with a record of when it arrived. Opening a delivery records a read receipt; downloads are counted separately. Consents — the kind an LPAC conflict workflow or a governance change might require — go through an explicit acknowledgment flow rather than an email reply nobody can point to later.

The fund team can withdraw a delivery, for example one sent to the wrong investor. It then disappears from the LP’s portal and its download stops working. A withdrawal is final. Two fund-level reports, the unfunded schedule and the rollforward summary, list every investor’s position, so they stay with the fund team and are never delivered to LPs.

Capital notices and the wire view

A capital call or distribution reaches LPs when the fund team sends it, not before. Each LP then sees its own amount, the due date, and its notice PDF, which carries a verification code and no bank details.

On a capital call, the portal shows the fund’s receiving account masked: the bank, the beneficiary, and the last four characters of each number, under a fixed warning that names the number to call before paying. The full numbers need an authenticator code entered in the last ten minutes. Every reveal is audit-logged and rate-limited, and the numbers show for two minutes. The mobile app shows the warning and the number only; wire details never reach it. LPAC members don’t see the account unless the organization grants their role access to wire instructions.

Notifications

Each notice is recorded in the same transaction as the change that triggers it, then sent by email and as a push notification to the mobile app. A background job retries any that are still pending. Notices about money, tax, consents, and legal matters, and alerts about changed bank details, are mandatory: an LP can’t turn them off, and they never wait. Statements, message replies, documents to sign, shared documents, and newsletters are optional: an LP can turn each off, and collect all but newsletters in a daily or weekly digest.

The fund team decides which contacts at each LP receive each kind of notice, and what a notice email contains, including whether it links to the portal, per fund and per group of LPs. See Set up LP emails.

Email trust

Because a capital call email is worth forging, genuine emails carry marks a forger can’t easily copy, and the portal gives LPs a way to check them:

• The sender is “<Organization> via NAVdryx”, with no reply address.
• An LP’s private security phrase appears at the top of emails sent to the address they sign in with. Account emails (invitations, password resets, security notices) and signature requests, which the e-signature provider sends itself, carry neither the phrase nor a code.
• A verification code appears on every notice email and every notice PDF, and on a newsletter or legal notice sent to the address an LP signs in with. The LP checks it on Emails we sent you, after signing in by typing the address or opening the app.
• No email or PDF carries bank details, and tax documents are never attached.
• A fund can leave the portal link out of its notice emails. Such an email tells the LP to sign in the usual way, and still carries its code.
• An LP can report a suspicious email. The report opens a flagged thread at the top of the fund team’s inbox. Replies to it reach the LP in the portal only, with no email or push.

See For limited partners for the LP’s view, and Security and trust for the controls behind it.

Data room and messaging

The fund team shares vault documents into LP data rooms, with one investor or with a fund’s investors as they stand at the time of sharing, and optionally until an end date. A document that belongs to one investor can be shared only with that investor. LPAC document shares are separate and send no notification.

LPs and the fund team exchange messages in threads, one fund per thread. The LP sees replies from “Fund team”; neither side can attach files, and both composers warn against putting bank details in a message.

Payout accounts

When an LP’s payout account changes, every contact of that investor is alerted, portal login or not. The fund team verifies the change by calling a number that was on file before the request, and payments to the new account are held for 72 hours after it becomes active. See Issue a distribution.

What the fund team sees

• Deliveries. For each capital notice, report, and K-1: who received it, when, whether it was opened, and, for capital notices, how often it was downloaded. Capital notice receipts export as CSV.
• The LP messages inbox. Every investor thread the reader may see, filtered by fund, investor, status, assignee, awaiting reply, or unread. Suspicious-email reports come first, then threads awaiting a reply, longest-waiting first. A thread can have one assignee and shows the date it has been awaiting a reply since. The dashboard lists LP messages awaiting a reply.

Access is scoped at the data layer

An LP can only ever see its own records, and that boundary is enforced where the data is read, not just in what the interface chooses to display. A finance contact can view statements but cannot sign; a contact who is not an authorized signatory cannot execute a subscription, regardless of what the UI might otherwise let them click toward. Consent acknowledgments are not yet limited to signatories. A suspicious-email report is visible on the LP side only to the person who filed it. See Security and trust for how this scoping works underneath the portal.

Branding

The portal carries NAVdryx branding, with a per-fund colour accent. A per-fund logo is not yet shown, and full white-labeling is not part of the current product.