Issuer relationships
A reporting-owner CIK identifies the filer across issuer relationships and name aliases. A filer may be an individual or an organization; the filing role is the relevant evidence.
| SYMANTEC CORP | 0000849399 | SYMC | Yes | Yes |
| AUTOMATIC DATA PROCESSING INC | 0000008670 | ADP | No | Yes |
| Mandiant, Inc. | 0001370880 | FEYE, MNDT | No | Yes |
| FORESCOUT TECHNOLOGIES, INC | 0001145057 | FSCT | No | Yes |
| DOCUSIGN, INC. | 0001261333 | DOCU | No | Yes |
| BTRS Holdings Inc. | 0001774155 | BTRS | No | Yes |
| Flywire Corp | 0001580560 | FLYW | No | No |
| SmartRent, Inc. | 0001837014 | SMRT | No | No |
| AvidXchange Holdings, Inc. | 0001858257 | AVDX | No | No |
| Rent the Runway, Inc. | 0001468327 | RENT | No | No |
| Atlassian Corp | 0001650372 | TEAM | No | Yes |
| Rubrik, Inc. | 0001943896 | RBRK | No | Yes |
| Netskope Inc | 0002063196 | NTSK | No | Yes |
No matching rows. Clear the filter to see all records.
Recent SEC transactions
Code P identifies a purchase, S a sale and A an award. Awards and open-market purchases describe different events. Use the public availability date when deciding when a researcher could have known about the transaction.
| 2026-07-11 | 2026-07-08 | NTSK | A | 16,778 | Not reported |
| 2026-06-03 | 2026-06-01 | DOCU | A | 4,384 | Not reported |
| 2025-06-27 | 2025-06-26 | RBRK | S | 1,041 | Not reported |
| 2025-06-27 | 2025-06-26 | RBRK | S | 2,704 | Not reported |
| 2025-06-27 | 2025-06-26 | RBRK | S | 18,179 | Not reported |
| 2025-06-18 | 2025-06-13 | RBRK | S | 700,000 | Not reported |
| 2025-05-31 | 2025-05-29 | DOCU | A | 2,916 | Not reported |
| 2025-02-01 | 2024-12-11 | TEAM | A | 1,056 | Not reported |
| 2025-01-17 | 2025-01-15 | RBRK | A | 76 | Not reported |
| 2025-01-15 | 2025-01-10 | DOCU | S | 10,000 | Not reported |
| 2024-12-07 | 2024-12-06 | TEAM | A | 1,048 | Not reported |
No matching rows. Clear the filter to see all records.
Up to 50 transactions from the recent two-year owner window.
Source evidence and strategy eligibility
The transactions below come from filings; a historical tracker separately simulates following eligible events. Joint filers can report the same transaction, and an owner can have filings at multiple companies. Public availability, amendment lineage and verified coverage determine which events a historical tracker may use.
The current directory marks this owner's filing coverage verified.