Portal

Return to Investor Profiles · Base Apps

What this tab does

Check the investor’s displayed member assignments, portal login history and eligible shared documents. Use it to investigate who appears linked to an investor and what documents are in that investor’s sharing scope.

Portal review follows several distinct relationships: a user has a member assignment; that assignment links the user to an investor; eligible sharing links documents to that investor. Contact information identifies whom operations may communicate with, but it supplies none of those access relationships. Login history records use of the portal, rather than proving access to each document.

Creating Avery Example as a contact therefore does not give Avery a login or share a document.

Find your way around

Real local OpenAdmin UI, with Cedarbridge Demonstration Investor selected. The investor group is expanded: Portal Access shows No members with access, and Documents shows No results. This is a valid profiles-only setup. The footer’s Count: 1 counts the investor placeholder row; it does not mean one member has access. Some column labels are truncated in the normal table; scroll horizontally for additional columns.

• Investor selector: scopes both sections. Keep the same selection while comparing them.
• Portal Access: one displayed investor/member assignment, grouped by investor. An investor with no displayed member has a placeholder instead. Archived members and internal OpenAdmin email addresses are excluded.
• Documents: one eligible, non-deleted, non-sensitive document already shared with this investor directly or through folder sharing, including inherited and share-to-all access. It is a shared subset rather than the full document inventory.
• Table controls: search, Filter and Hide fields help inspect each section. Expand an investor group to see its member rows.

Inspect access

1. Open Investor Profiles → Portal and select the intended Investor.
2. Expand its Portal Access group. Check Member and Email against the person you intended to investigate.
3. If No members with access appears, there is no displayed member assignment in this query. The placeholder is not an invited person or someone with zero visits.
4. For an existing member, interpret the fields at their own level:
   • Access Type identifies a displayed Team or Portal member. Status is the member’s mirrored status; neither is an invitation-acceptance record or a live authorization test.
   • Access Granted is when the member’s investor assignment was created, not an invitation, acceptance or first-login date. The investor-group date is the earliest displayed assignment.
   • Portal Visits and Last Portal Access describe the member’s recorded successful portal logins. They are not per-investor or per-document views. A member linked to several investors can appear repeatedly; do not sum that history across groups.

This tab inspects existing assignments. If access is required, give the authorized administrator the investor ID and intended person. A real access test belongs to that access workflow.

Inspect documents

Keep the Investor selection and inspect Documents. In the fictional example there are no eligible shared documents. An empty result does not establish that no source document exists or prove a person’s effective file permissions.

When rows exist:

• Investors Shared and Investors Accessed are document-wide distinct-investor counts, even when one Investor is selected. They are not reader counts or numbers of opens, and they do not prove the selected investor read the file.
• Recorded document events are attributed through current member–investor links and eligible sharing. One member linked to several investors can contribute to several investor counts.
• Open links to the document’s record in Documents. It is not itself a file download or a test of portal permission.

For a missing required document, check Investor, search and table filters, then ask the authorized document administrator to inspect the source record and its sharing scope. Keep Sensitive and sharing settings governed by that workflow.

Profile records and portal access

Cedarbridge Example Holdings Ltd exists in Legal Entities and Avery Example exists in Investor Contacts, while Portal Access and Documents are empty for the selected investor. Profile setup, member assignment, login history, document sharing and file access are separate facts; the profile records alone do not establish access.

If something looks wrong

• A contact appears in Data but not Portal: confirm Investor and the intended person. Ask the access administrator to inspect membership and investor assignment if access is required; duplicating a contact does not grant it.
• Documents is empty: check scope and filters. Deleted, sensitive or unshared documents are outside this result. Identify the intended document for its authorized owner instead of treating the empty table as a complete inventory.
• Counts differ from your expectation: distinguish member logins from document-wide investor counts, and account for one member linked to several investors.

When a correction is required, give its authorized owner the investor, member or document identity and the specific assignment or sharing issue. Keep profile setup, displayed access and actual file permissions distinct.

Continue

• Investor Profiles — Investor Profiles overview; Data maintains relationships, subscribers and contacts.
• Subscriptions — Subscriptions; processing state is separate from portal login history.