DFIN has compiled a list of frequently asked questions pertaining to EDGAR. If you have additional questions, please search the knowledge hub or contact support for help.

See our Glossary of EDGAR Filer Terms article for a summary of the most common terms.

EDGAR Next

Understanding EDGAR Next, access to EDGAR, and compliance.

• EDGAR Next is a modernization effort by the SEC to bring identity management principles to EDGAR. The SEC wants to know the individual making a submission to EDGAR and to ensure that individual is authorized to make the submission. 
• Compliance with EDGAR Next is required as of September 15, 2025. 
• To obtain access to the EDGAR filing sites and submit EDGAR filings, an EDGAR account is required.
• If you did not enroll an existing CIK in EDGAR Next before December 22, 2025, you must submit a Form ID application for EDGAR access and await SEC approval. For guidance, please review the following:
  • Application for EDGAR Access (Form ID) - Filer lost electronic access to existing CIK account.
  • After regaining access, please ensure all users have the appropriate permissions for filing. 
    See Managing Delegated Filing Authority in EDGAR Filer Management. If you need assistance, please contact your DFIN representative.

Login.gov

Guidance regarding and managing a Login.gov account.

• If you manage an EDGAR account (CIK) and/or file electronically on EDGAR, you are required to obtain Login.gov individual account credentials. You do not need a Login.gov account if someone else manages your EDGAR account and submits your filings, for example if you are a reporting owner (i.e., Officer or Director).
• No; however, the person(s) that manages the EDGAR account on your behalf is required to have Login.gov account credentials. 
  
  If you did not enroll an existing CIK in EDGAR Next before December 22, 2025, you must submit a Form ID application for EDGAR access and await SEC approval.
• Go to Create your account | Login.gov to create your Login.gov credentials.
• Face or Touch unlock, Authentication Application, Security Key, Text Message/Phone Call, Back-up Codes (less secure). Please verify options on authentication-method site as options may change.
• The EDGAR Filer Manual Volume I, says individuals with Login.gov accounts created with personal email addresses who are concerned about their personal address being visible on the dashboard, or for other reasons do not wish their emails to be used in connection with EDGAR matters, should create new Login.gov individual account credentials with the email addresses they wish to use in connection with EDGAR.
• The SEC requires individual account credentials. Anyone that accesses the EDGAR filing sites, the EDGAR Filer Management Dashboard or submits filings must have a Login.gov individual account. The SEC wants to know the individual that is accessing the EDGAR sites and submitting filings.
• A filer must first add the new email address under “Edit my information” on the EDGAR Filer Management Dashboard prior to updating the email address on Login.gov. Then go to Login.gov and follow the steps to “Change the email address associated with a Login.gov account”. The Account Administrators assigned to your EDGAR accounts will receive a notification of the address change.

• If you join a new company, you do not need to create a new Login.gov account. You can change the email address of your existing Login.gov account. Follow the steps to “Change the email address associated with a Login.gov account”.

  The Account Administrators of the EDGAR account will receive a notification of the address change. If you no longer require access to an EDGAR account, you can remove yourself from an EDGAR account.

Filer Management Dashboard

The main things to know about the usage of the Filer Management Dashboard.

• The EDGAR Filer Management dashboard has interactive functions on EDGAR. After obtaining EDGAR access, filers will manage their EDGAR accounts using the dashboard. The following are managed from the dashboard:

  • CIK confirmation code (CCC)
  • Individuals that use the EDGAR account including the EDGAR Point of Contact
  • Delegation to another filing entity such as a Filing Agent
  • Annual Confirmation of the EDGAR account

  It’s also where the Form ID (application for access codes to file on EDGAR) is located.

• The dashboard will be available during EDGAR operating hours, 6 a.m. to 10 p.m. Eastern Time each day except Saturdays, Sundays, and Federal holidays. Optional APIs that provide much of the same functionality as the dashboard will also be available during those hours because the APIs rely on dashboard availability.
• Anyone with Login.gov credentials can access the dashboard; however, it will only contain EDGAR accounts if the individual has been added to an EDGAR account.
• See the SEC “Overview of EDGAR Filer Management Dashboard” YouTube video.
• Form ID processing times are currently longer than usual. Please contact the SEC at 202-551-8900 option 3 to speak with someone regarding your specific FORM ID.
  Please note, even if DFIN submits the Form ID, we are not able to get the status of the filings, nor do we receive any notifications on the filing.
• When a Form ID for a new EDGAR account is approved, the CIK is provided. The CCC is auto generated and available to the Account Administrators listed on the Form ID in the EDGAR File Management Dashboard under "Manage CCC". The CCC can be regenerated or a custom CCC can be created.
• As of December 19, 2025, the EDGAR passphrase, password, and PMAC have been discontinued; instead Login.gov credentials will be used to log into EDGAR.
• The CCCs of CIKs that did not enroll in EDGAR Next before December 22, 2025, cannot be updated. You must submit a Form ID application for EDGAR access and await SEC approval to regain access to your EDGAR account. A new CCC will be available once you regain access to the EDGAR account. 
  
  If you have access to the EDGAR account in EDGAR Filer Management and you are an Account Administrator, you can update an existing CCC under "Manage CCC".
• Company Information updates would continue to be done on the EDGAR filing website under “Retrieve/Edit Data”, except for the EDGAR Point of Contact.
• The EDGAR Point of Contact is selected in the Filer Management Dashboard under the Manage Individuals section. Click on the Actions menu across from the individual and choose “Select as primary Point of Contact”.
• Series and Class ID updates would continue to be done on the EDGAR filing website under “Retrieve/Edit Data”.

Roles

Questions about the different roles which can be applied to your EDGAR users.

• An Account Administrator is the person(s) authorized to manage the EDGAR account. Each EDGAR account is required to have at least two Account Administrators and can have a maximum of twenty Account Administrators. Filers that are individuals or single-member companies are required to authorize and maintain at least one Account Administrator, however the SEC encourages at least two Account Administrators for those accounts.

  An Account Administrator can add and remove Users, Account Administrators and Technical Administrators (including removing themselves as an Account Administrator); create and edit groups of Users; delegate filing authority to other EDGAR accounts and remove delegation; generate a new CCC; make submissions on EDGAR; and receive notifications regarding significant events affecting the account (notifications are emailed to the Account Administrator’s email address and available on their dashboard).

  If two Account Administrators are required on the EDGAR account, and there are only two, you cannot remove an Account Administrator until another is added first.

  An Account Administrator is also responsible for the annual confirmation of the EDGAR account.

  One Account Administrator will act as the primary EDGAR Point of Contact (EDGAR POC). The SEC staff may contact the filer’s other Account Administrators if, for example, the EDGAR POC cannot be reached or is nonresponsive.

• Yes. Although individuals or single-member companies are only required to have one Account Administrator, the SEC encourages listing two Account Administrators for each EDGAR account.

• Users are person(s) added by the Account Administrator to make submissions on EDGAR. The SEC doesn’t require a minimum number of Users. They allow up to 500 Users for each EDGAR account.

  Users can view basic information about the filer’s account including the filer’s name, CIK, CCC, corporate and contact information, as well as the contact information for Account Administrators.

  Users can update Company Information (COUPDAT) as well as Series and Class ID information (SCUPDAT) on the EDGAR filing sites.

  Users cannot add or remove individuals from the dashboard other than themselves. They also cannot alter or generate a new CCC.

• A Technical Administrator is a person(s) that manages the technical aspects of a filer’s connection to APIs. They are only required if the filer opts to connect to EDGAR APIs. A filer can use its delegated entity’s API connections.

  If used, there must be at least two Technical Administrators. The maximum number of Technical Administrators per EDGAR account is twenty.

  They generate the filer API token and manage the API connections as well as serve as points of contact for questions from SEC staff regarding the filer’s connections to the APIs.

• An Account Administrator is able to delegate authority to file to any other EDGAR account, such as a filing agent. The filing agent would then become a Delegated Entity.

• The Account Administrator of an EDGAR account that received delegation is considered a delegated Account Administrator. They accept delegation invitations; decide whether their Users should have access to the EDGAR account that has been delegated; view the CCC of the delegated EDGAR account; and submit filings for the account that was delegated.

  A delegated Account Administrator cannot access the dashboard of the account that was delegated and does not have the ability to make changes to the account except for Company Information and Series and Class ID information located on the EDGAR filing websites.

• The User of an EDGAR account that received delegation is considered a delegated User. They can submit filings for the account that was delegated.

  A delegated account User cannot access the dashboard of the account that was delegated and does not have the ability to make changes to the account except for Company Information and Series and Class ID information located on the EDGAR filing websites.

• User groups allow a delegated Account Administrator to group subsets of the filer’s users into user groups. The user group function would assist delegated entities to authorize certain of their users to make submission on behalf of specific filers.
• The first Account Administrator listed on the Form ID will automatically be the EDGAR POC. You can change the EDGAR POC in EDGAR Filer Management.

Delegation

Questions about delegating filing authority and managing requesting delegation.

• EDGAR requires the filer to programmatically give filing agents permission to use their CIKs (“delegate to”). This allows filing agents to update CIK company information and submit filings on your behalf.

• If you are an Account Administrator, you can delegate to more than one account at a time by using the “Bulk Actions” menu from the main account page of the Filer Management dashboard. Select the EDGAR accounts that you want to delegate, then from the “Bulk Actions” dropdown select “Add delegation”. This will take you to the “Delegate authority to file” screen where you will enter the CIK of the EDGAR account you want to delegate to.

  Account Administrators can also manage delegation at the account level using the “Manager Delegations and User Groups” section and selecting “Add Delegation”.

  Once successfully submitted, an invitation will be sent to the Account Administrators of the other EDGAR account. One of the Account Administrators from the other EDGAR account will need to accept the invitation for the delegation to take effect, unless auto accept is turned on. The other EDGAR account will become a Delegated Entity.

• Yes. In the dashboard a delegation preference of “auto accept delegation” can be checked to allow an EDGAR account to auto accept delegation. That means if a filer sends a delegation request to DFIN, DFIN will be able to automatically accept. DFIN would then become a delegated entity and will be able to make filings on the filer’s behalf.
• Delegation does not expire; however, the Account Administrator or delegated Account Administrator can cancel the delegation.

• Yes. The dashboard has a “Request Delegation” function. This process would enable filing agents to assist their filers in delegating to the correct EDGAR account. Once the delegation request is sent, an account administrator of the filer will have to accept the invitation.

  For this process to work, the filer’s EDGAR account delegation preference must be set to “Allow delegation request” before the delegation request is sent. 

• If you don’t delegate, only your EDGAR Account Administrators and Users will be able to access the EDGAR account on the EDGAR filing websites and submit filings on your behalf.
• The DFIN filing agent CIKs that you need to delegate to are: 0001193125 and 0000950130.
• Log into EDGAR Filer Management, choose the CIK you wish to view delegations for and then select “Manage Delegations and User Groups” - you will see the CIKs that have been delegated to file on your behalf under the “Delegations To” section. You should have TWO CIKs for DFIN. If you are only a User on the account, you will have a "View Delegations" section instead of a “Manage Delegations and User Groups” section.

API and API Tokens

Answers for what is API and how to use API Tokens.

• Application Programming Interface (API) means a software interface that allows computers or applications to communicate with each other. EDGAR offered 3 APIs with the proposed rule and offers 12 additional APIs with the final rule.

• A User API Token is a confidential alphanumeric string of text generated on the individual's dashboard. The token represents a security requirement that eliminates the need to manually enter individual account credentials and perform multifactor authentication each time a submission is made via an API.

  The User API token adheres to the capabilities of the Users roll. For example, the User API Token must be that of an Account Administrator of the CIK for which individuals are to be added when using the “Add individuals” API.

• Yes. The User API Token expires every 30 days. It can only be regenerated from the dashboard.
• A Filer API Token is a confidential alphanumeric string of text generated at the EDGAR account level on the dashboard by a Technical Account Administrator. It’s used to identify the filer or filing agent accessing the API.
• Yes. The Filer API Token expires yearly. It can only be regenerated from the dashboard.

• The email address used for creating your login.gov account is used for your account in EDGAR Filer Management. When you are added to an EDGAR account in EDGAR Filer Management, the email address used must match the login.gov email address. Also, that email address should be the same as what is recognized by DFIN applications.

  To fix this issue, please see our article Troubleshooting Login.gov and DFIN Email Logins. 

• If you delegate filing to DFIN then you will not need to manage your user and CIK filer tokens. However, if you are a self-filer, you will need to generate a new user token every 30 days and a filer token once a year on the EDGAR Filer Management site. The tokens will be uploaded to DFIN filer management to self-file using ActiveDisclosure or Arc Suite applications (i.e., ArcReporting and ArcRegulatory).
• If the individual is a user of the CIK's EDGAR account, and the CIK is delegated to DFIN, then they just need to generate a user token and upload it to DFIN filer management portal.
• No. The User and Filer API token are only needed when using APIs.

Co-registrant and Subject companies

Managing Co-registrants and Subject companies.

• EDGAR will not require role-based permissions for co-registrants at this time, and the addition of co-registrants to a filing will continue to be performed the same way it is currently performed (i.e., simply by listing the CIK and CCC of each co-registrant).
• Per the SEC, a subject company does not require role-based permissions because it does not require CIK/CCC confirmation. Addition of subject companies to a filing will continue to be performed the same way it is currently performed.

Annual confirmation

Information about confirming user's authorization annually.

• Each filer is required to perform an annual confirmation that all the filer’s Users, Account Administrators, Technical Administrators, and delegated entities are authorized by the filer to act on its behalf, and that all information related to the filer reflected on the filer’s dashboard is accurate. Account Administrators will act for the filer to carry out this function.
• EDGAR will allow Account Administrators to select one of four quarterly dates as the filer’s ongoing confirmation deadline: March 31, June 30, September 30, and December 31 (or the next business day if the date falls upon a weekend or holiday when EDGAR is not operating).
  If you enroll on March 24, 2025, and select March 31 as your confirmation date, annual confirmation will be due March 31, 2026 (one year from the current quarter). If you enroll on March 24, 2025, and choose June 30, September 30, or December 31, those will all be 2025 due dates.
  
  An Account Administrator need not wait until the deadline to confirm. Confirmation in an earlier quarter will result in a confirmation deadline one year after the end of the quarter in which the early confirmation occurred.
• Prior to the confirmation deadline, EDGAR will send notices six weeks, three weeks and each of the five business days leading up to the confirmation deadline.

• EDGAR allows for a three-month grace period during which filers will be able to continue to make submissions and take actions on EDGAR as usual, while Account Administrators will receive notices reminding them to complete annual confirmation by the end of the grace period.

  If the Account Administrator does not execute the annual confirmation by the end of the three-month grace period, EDGAR will deactivate the filer’s access, and the filer will be required to submit a new Form ID application to request access.

Power of Attorney (POA)

Questions regarding Power of Attorney, specifically submitting documents.

• When submitting a Form ID a power of attorney (“POA”) from an authorized individual of the filer is needed under the following circumstances:

  (1) The applicant is an individual or single-member company who seeks to authorize another individual as Account Administrator; or

  (2) The applicant is a company that seeks to authorize an individual who is not employed by the applicant or its affiliates as Account Administrator.

  In these circumstances, the applicant must submit a POA signed by an authorized individual of the filer permitting an Account Administrator to act on the applicant’s behalf to manage its EDGAR account, together with a Form ID. The signature of the authorized individual of the filer on the POA authorizing the Account Administrator in these circumstances must be notarized.

• Yes. The Form ID allows for multiple POA attachments.

Asset-Backed Entities

Information about how EDGAR manages Asset-Backed Entities.

• New serial companies can be created under “Manage ABS Issuer Activity”. New serial companies requested to be created via that process will automatically inherit all dashboard information (e.g., contact information, Account Administrators, Users, Technical Administrators, and delegations) associated with the ABS issuing entity that made the Asset-Backed Securities Issuing Entities Creation (“ABSCOMP”) submission.