ECT CalBoard – Quick Start & User Guide

This page explains how to sign in, use the CalBoard during an outage, and what the Admin / Security tools do. If you’re not sure whether you should be changing something, you probably shouldn’t.


1. Roles & Access


2. Signing In

  1. Go to the Login page.
  2. In the Analyst box, start typing your name or analyst code.
    A list will appear; click your name to select it.
  3. Enter the current password:
    • Users: use the shared User password.
    • Admins: use the Admin password.
  4. Click Sign in.

If the message says you must use the Admin or User password, check which account you selected and try again.


3. CalBoard Layout

After logging in successfully, you will see the main CalBoard.

Status colors keep it obvious: green is complete; yellow is incomplete.


4. Everyday Use – Regular Users

It works just like every other CalBoard you’ve used. The checkboxes simply hide CALs completed by Resolution and/or hide VOID CALs.


5. Admin Menu – Managing Projects & Structure

If you are an Admin, you will see an Admin dropdown in the navigation bar with:

5.1 Projects Admin

The Projects page controls which projects appear on the CalBoard.

5.2 Components Admin

From the Projects page, each project has a Components… button that opens the Components Admin for that project.

5.3 Analysts Admin

Note: The Analysts page manages the global roster for all projects. Adding, editing, or removing an analyst affects every outage using this CalBoard, not just your current project.

The Analysts page controls who appears on the CalBoard and who has Admin access.


6. Security Settings – Super Admin Only

The Security page is restricted to Super Admin accounts. It controls the shared passwords used for all logins.

Changing any password takes effect immediately for all users. Make sure you communicate new User/Admin passwords to the right people before or immediately after changing them; otherwise no one will be able to log in.


7. Recommended Practices

CalBoard is designed to reflect the real work happening on site. Small, careful edits go a long way; large destructive changes should only happen when a project is truly finished.