Signals permissions and states
Reference Signals route access, shared and organization-scoped data boundaries, dataset sources, lifecycle states, and destructive actions.
Signals requires authentication and an organization membership, but its dashboard intentionally combines shared reference records with organization-specific dataset summaries.
Route and action access
| Visitor | Access |
|---|---|
| Signed out | Cannot open the Signals organization routes. |
| Signed in without membership in the URL’s organization | Redirected with You are not authorized to access this page. |
| Organization Admin, Member, or Guest membership | Passes the current organization route gate. |
The current upload and delete handlers add no admin-only or capability check after the membership gate. All three organization membership roles can reach those controls at the pinned product revision. Review organization membership before granting access to a workspace that contains deletable datasets.
The Signals host has no bare-root dashboard route. Organization pages are /<org-slug>, /<org-slug>/datasets, and /<org-slug>/datasets/<dataset-id>.
Data scope
| Surface | Scope |
|---|---|
| Fund records overview on Dashboard | Shared latest record for each normalized fund name across every ingested filing. |
| Total unique funds and Geographic regions | Derived from the shared master-fund view. |
| Total capital tracked, Recent filings, and Top strategies by capital | Derived from datasets belonging to the current organization. |
| Datasets list | Current organization only. |
| Dataset detail and its Fund records overview | The selected dataset, after confirming that the dataset belongs to the current organization. |
A dataset identifier from another organization returns Dataset not found rather than exposing that dataset.
Dataset sources
The browser accepts these source values:
| UI label | Stored source |
|---|---|
| Preqin | preqin |
| SEC Form D | sec_form_d |
| FMA | fma |
| BaFin | bafin |
| SEBI | sebi |
| SEDAR+ | sedar_plus |
Fund-size values currently come from Preqin and are interpreted as USD millions before display.
Dataset lifecycle
| State | Current meaning |
|---|---|
| Pending | The dataset record exists and processing has not started; it normally awaits background processing. |
| Processing | The background worker started parsing the CSV. |
| Completed | Processing finished and the detail page can report processed and failed record counts. |
| Failed | Parsing or completion failed. |
The status filter also recognizes Cancelled, Accepted, and Rejected because they remain supported dataset values. The current Signals pages expose no customer action to move an upload into those three states; the automated upload path normally uses Pending, Processing, Completed, or Failed.
Delete behavior
Delete permanently removes the dataset and all fund records associated with it. The current page has no restore action. A delete is organization-scoped, so a crafted identifier cannot delete another organization’s dataset.
Integration boundary
The separate signals:write API endpoint requires an organization-bound token and ingests captured social events into the Profiles signal model. The scope itself can exist on an organization-less token, but the endpoint rejects that token. It is not an API for these CSV datasets or their fund records. Browser dataset access and API token access therefore use different routes, records, and authorization contracts.