Fund II LP Portal Access: Check It Before You Invite Anyone
A practical pre-invite check for Fund II reporting, community access, and the investor view in a shared firm workspace.
Fund II does not need a second firm workspace. It does need its own reporting boundary. Before you invite an investor, check the fund they can open, the documents they can read, and the community where their profile might appear. A shared firm directory is not permission to read Fund I's letters.
- Select Fund II in the manager workspace and check its portfolio, people, updates, and resources.
- Give each person the right vehicle access. Community membership is not LP reporting access.
- Preview the portal as a Fund II investor and as a community-only member.
- Open a Fund I route from the Fund II-only view. It should not reveal Fund I's reporting.
- Invite people only after the audience for each published item is right.
Start with the vehicle, not the invitation list
Say Northwind Capital has Fund I and Fund II. Both sit in one firm workspace, but an investment recorded for Fund II remains a Fund II position. The manager's selected fund scopes the portfolio, deals, and people views. "All funds" is useful for the team; it is not an investor permission level.
Before inviting anyone, select Fund II and review its portfolio and updates. Check that the company pages and published letters belong there. If a firm-wide issue should reach both funds, label it as firm-wide. Do not copy a Fund I-only letter into Fund II just to make the new portal look populated.
Decide what each person may actually read
The same person can be an investor in one fund, have reporting access to another, and choose to join a community. Those are separate facts. In GPAgent, granting reporting access does not assert that the person invested. Inviting a community member does not hand them LP financial reporting.
| Person in the example | Access to check | What not to assume |
|---|---|---|
| Fund II investor only | Fund II portal reporting and its eligible community | Fund I letters or portfolio reporting |
| Investor in both funds | Both authorized fund views | That every resource is firm-wide |
| Fund II community member who is not an LP | Community and content shared with that audience | Investor-only documents or financial fields |
In People, review access for each vehicle. Then check the audience on the items you plan to share. A Fund II resource can be for its LPs, or for LPs plus eligible community members. An administrator login can point an LP to their account without moving investor-specific statements or K-1s into the portal.
Preview the portal before the first invite
Use the manager's portal preview for a Fund II investor. Read it as that investor would: fund header, company pages, updates, resources, and community. Then preview a community-only member. The second view should not expose LP-only reporting. If a person belongs to both funds, use the multi-fund investor preview to check the fund switcher and each fund's content.
Finally, try a Fund I route from the Fund II-only view. A manager's own access can hide a mistake in an ordinary browser tab. The narrower preview makes the boundary visible before an invitation goes out. For a real unauthorized visitor, a fund they cannot access stays unavailable.
This is also a content check. A technically correct permission boundary will not fix a Fund II page carrying a Fund I PDF by mistake. Review the title, fund label, and audience of every published item.
Keep community consent separate from fund reporting
A Fund II investor may choose to publish a profile to Fund II's community without joining the broader firm community. An invited non-LP can participate in an eligible community without becoming an investor. Members control where their profiles appear, and can hide them later. The fund team chooses which communities are enabled; a profile choice does not override reporting permissions.
That separation matters when the second fund starts to build its own network. A useful directory can cross a firm when people opt in. Confidential reporting cannot cross a fund merely because someone appears in that directory.
For the product view, explore the GPAgent LP Portal. If you're planning a Fund II rollout, join the LP Portal waitlist and tell us which access boundary you need to check first.
FAQ
Can a Fund II investor see Fund I because both funds share a firm workspace?
No. The firm team can work across funds, but an investor's portal view follows the vehicle access they have been granted. Preview the Fund II-only view before inviting them.
Does joining the firm community give someone access to both funds' reports?
No. Community publication and fund reporting are separate permissions. A community-only member does not get investor-only documents or financial fields.
Should I upload every LP document to the portal?
No. Share documents meant for the chosen fund audience. Investor-specific statements and tax forms belong with the fund administrator; link to that account where useful.
Build on the fund record, not a prompt.
See how GPAgent keeps agentic investing workflows tied to a durable CRM, API, and activity ledger.