# Roles and granular permissions - LP Port

> Give each administrator only the access their job needs, with separate permissions for the CRM, investments, data rooms, content, internal notes, exports and administrator management.

URL: https://lpport.com/features/permissions
Last modified: 2026-08-08

Product / Roles and permissions

Roles and permissions



# Access that matches the job.

Not everyone at a fund should see everything. An analyst maintaining data rooms does not need to read internal notes or open a passport image. Permissions here are granular and enforced on the server, so the interface and the API agree about what someone may do.


Get started
Audit trail












## Enforced where it actually counts.

Hiding a button is not access control. Every permission is checked on the server for every request, so an administrator without a capability cannot reach the underlying data by any route.

Sensitive surfaces are deliberately separated from ordinary ones. The investor roster is one thing; internal notes, identity images, subscription form responses and wire details are each gated on their own.





-

Separate capabilities
Viewing the CRM, managing investments, managing data rooms, managing content, reading internal notes, exporting data, viewing as an investor and managing other administrators are all distinct.



-

Administrators cannot escalate
An administrator cannot edit, delete or reset another administrator unless they hold the capability for managing administrators, and cannot remove or demote themselves.



-

Read-only investor view
A permitted administrator can see the portal exactly as an investor sees it, without being able to act as them. Every mutating request in that mode is refused.



-

Sensitive data walled off
Identity images, form responses containing tax identifiers, wire details and internal notes each require the specific permission that governs them.










Team



## More people, less exposure.







### Bring in help safely

An operations hire can run data rooms and documents without ever seeing an investor's identity documents or your internal notes.






### Support without impersonation

Viewing as an investor answers "what do they see" without giving anyone the ability to act on their behalf.






### Every action attributed

Administrative actions are recorded against the person who took them, so access and accountability match.










Questions



## Permission questions.







### Can an administrator see everything by default?

An administrator with no restrictions has full access. Once you assign specific capabilities, they are limited to those, and every request is checked against them on the server.






### Can one administrator lock out another?

No. Acting on another administrator requires the capability for managing administrators, and nobody can delete or demote themselves, so a portal cannot be left without an administrator.






### What is "view as an investor"?

It shows an administrator the portal exactly as a specific investor sees it, for support and diligence. It is strictly read-only: every mutating request made in that mode is rejected, so it cannot be used to act as the investor.















## Give access deliberately.

Permissions, the audit trail and the isolation model are three parts of the same answer.


Get started
Security overview