Where to ask for help, report a problem or send feedback.
This site has no support address set yet. The CPUC sets it for each site (the CEDARS_SUPPORT_EMAIL setting); until then, ask your organization's CEDARS administrator.
Before you write
- For a filing that will not pass its checks, download its findings (each version's page has a findings file): each finding names the line, record, field and rule, and says how to fix it. The validation rules explain every rule.
- For access to an organization's filings, ask that organization's administrators from your account page; they decide, not the CPUC. Access to personal information also needs a CPUC data steward's approval.
- For a field's meaning or unit, see the data dictionary.
- For a lost second factor, use one of your recovery codes to sign in, then set up a new factor. Without them, write to support.
What to include
- The page's address (copy it from the browser), and the organization you were acting for.
- What you did, what you expected and what happened instead, with any message the page showed.
- Never a password, a recovery code, an API token or personal information about customers.
Accessibility barriers
If a page cannot be used with your keyboard, screen reader, magnifier or other assistive technology, tell us which page and what got in the way. CEDARS is built to meet WCAG 2.2 Level AA, and a barrier is a defect we fix. See keyboard and screen reader use.