EDGAR filer credentials, explained

CIK, CCC, and EDGAR Next

• ✓CIK: the company's Central Index Key, the stable numeric identifier on EDGAR.
• ✓CCC: the CIK Confirmation Code used to authenticate submissions for that CIK.
• ✓EDGAR Next: the SEC's filer account and submission system companies use to manage access and file.
• ✓Section 16 Forms 3, 4, and 5 file under each reporting person's own CIK and CCC, not the company codes used for 10-K, 10-Q, and 8-K.

Why verify before the due date

Wrong CCC, mismatched CIK, or an unverified EDGAR Next setup surfaces as a submission error when time is shortest.

• ✓Early verificationCompanies that verify credentials early turn filing day into a submit-and-poll step instead of an access-recovery fire drill.
• ✓TEST modeTakePublic runs EDGAR Next submission in TEST mode by default until credentials are verified, so a test submission can confirm CIK and CCC before anything live goes out.

How TakePublic stores credentials

• ✓Company admins enter CIK and CCC under Settings, EDGAR credentials.
• ✓The CCC is stored encrypted; only company admins can view or update credentials.
• ✓Platform admins can manage credentials when assisting a tenant.
• ✓Submission requires verified credentials plus a counsel sign-off that still matches the current document hash.
• ✓Companies using their own EDGAR agent can export a filing package after sign-off (CCC redacted) and record the accession number when it files externally.

The counsel gate still holds

Verified credentials authorize the transmission path. They do not authorize the content. Only counsel can move a filing to signed off, and submission re-checks that the sign-off hash still matches. Any edit after sign-off forces a new attorney review before EDGAR sees the filing.