Following Profiles and Requesting Access
How following a directory profile works, when access requests are available, and how owner-approved permissioned access behaves.
Directory profiles offer two distinct actions, and they are not the same thing:
- Follow keeps a profile on your radar.
- Request access asks the profile's owner to share permissioned content with you.
The profile only ever shows actions that are truthful for its current state: the server decides whether an action is available, and the page renders that decision.
Following a profile
Signed-in users can follow an organization's profile from the Follow button in the profile header. While the follow is being set up the button shows Follow requested; once active, the header shows Following.
Following does not grant access to any permissioned content — it is a public interest signal and keeps you connected to the profile's public record.
Follow is available on organization (entity) profiles. If a profile cannot be followed in its current state, the button simply does not appear.
When "Request access" appears
Request access only appears on organization-managed profiles that have permissioned content:
- The profile must be managed — claimed by (or curated for) an authorized owner who can actually review requests.
- The profile must have permissioned content to request. The public record shows this as Permissioned packages: Approval required.
Unclaimed reference profiles never show Request access: there is no owner to approve a request, so offering the button would be untruthful. Profiles whose filings are all public have nothing to request, so the button does not appear there either.
The request and approval flow
On an eligible profile, choose Request access. The button changes to Request pending and stays that way while the owner reviews.
The profile's owner receives the request and reviews it. Owners can approve or reject, optionally with decision notes.
On approval, the owner chooses which collections to share. Access is provisioned as token-gated grants — each grant can carry an expiration date, and grants can later be revoked.
Once your access is active, the profile header shows Access granted, and you can open the shared collections and their contents from Sureshake.
What approved access looks like
- The profile shows Access granted in place of the request button.
- Permissioned entries in the report index remain labeled Permissioned; public entries are labeled Public.
- Shared collections open with their reports and downloadable artifacts. Download links are time-limited and access can expire or be revoked by the owner.
Approval is scoped to what the owner explicitly grants. An approved request never exposes content the owner did not select, and revocation or expiry ends access.
Related pages
- Understanding reference profiles
- Claiming your organization's profile
- Organizations & Follow Access — follow policies for entity reports outside the public directory
Claiming and Verifying Your Organization's Profile
Who can claim a directory profile, what claiming does and does not do, and how the review process works.
Interactive DCF Models
Build your own discounted-cash-flow view of a public company — per-year drivers, low/mid/high scenarios, saved and shareable scenarios, exports, and an AI assistant, all computed from SEC filings.