Your photo shows on the Leadership & Reps page. A clear, square headshot works best.

Two-factor authentication

When on, we email you a 6-digit code each time you sign in with your password — so a stolen password alone isn't enough to get in.

Email signature

Drop this into any email with the composer's Signature block. Add your name, title, and contact info.

Positions

Leadership titles shown on the Leadership & Reps page and used when routing requests. Change them year to year here — Senior Leadership and Site Admins can manage these.

Add position

Approve new sign-ups, set roles, assign positions, and choose who's on the messaging hub. You can only grant roles below your own tier — only a Site Admin can create Senior Leadership or other admins.

Branding & logos

Upload your logos and graphics — they appear across the site for everyone. PNGs with a transparent background look best, especially the header logo (it sits on the dark bar).

Header & footer

The association name and tagline in the top bar, and the footer line on the sign-in screen. These show to everyone, including signed-out visitors. The header logo is set under Branding & logos.

Header title Header tagline Footer text

Login screen

What signed-out visitors see on the sign-in screen. The logo here uses your header logo.

Heading Subtext

Welcome screen

An optional splash that flashes a graphic to the member right after they sign in, then fades into the dashboard. Two independent versions — a one-time greeting for brand-new members, and a lighter one for returning daily logins. Each uses its own uploaded image (separate from your dashboard branding) and only plays once an image is set. Off by default.

Dashboard shortcuts

The big buttons on everyone's home dashboard. Point each one at an in-app page or an external link, give it a label, and set an icon — click the icon swatch to upload an image, or type any emoji (or groupme for the GroupMe logo).

Calendar sources

Choose which Google Calendars feed the dashboard and the Calendar page. Each calendar must be set to public in Google Calendar.

A calendar ID looks like an email address — e.g. name@gmail.com or …@group.calendar.google.com. Find it in Google Calendar → that calendar's Settings → Integrate calendar → Calendar ID. Make sure "Make available to public" is on.

Request types & routing

The categories members pick when submitting a request, and who each one is automatically assigned to. Edits apply to new submissions.

Add type

Contract chatbot

Paste your collective bargaining agreement here. The dashboard's Contract Chatbot searches it and shows members the exact relevant sections — no outside AI service, no guessing, just your real contract wording.

Contract title (optional) Contract text Upload your contract PDF and we'll pull the text out automatically. (Scanned/image-only PDFs can't be read — for those, paste the text.) You can also paste text or upload a .txt file.

DCEA email signature

A shared signature anyone on leadership can drop into an email blast — the composer's Signature → DCEA (shared) block. This is separate from your personal signature in My Profile.

Tip: keep it short — name, title, and a link. It's inserted at the bottom of the email.

Google Sign-In

Point the site at your organization's own Google OAuth client, so members sign in through your Google project. Changes take effect immediately.

Client ID

Client Secret

Advanced: App URL

Base URL used to build the redirect URI. Set this to your deployed domain in production.

Save credentials Revert to .env

How to create a Google OAuth client

1. Go to console.cloud.google.com and pick (or create) a project owned by your org.
2. APIs & Services → OAuth consent screen → configure (External).
3. Credentials → Create Credentials → OAuth client ID → Web application.
4. Under Authorized redirect URIs, add the URI shown above.
5. Copy the Client ID and Secret into the fields above, then Save.

System email (SMTP)

Used for system emails — account verification, password resets, and 2-factor codes. Paste credentials from a provider like Brevo or Resend.

SMTP host

Port

Username

Password / API key

From address

Save Send test email

Port 465 uses SSL; 587 uses STARTTLS. The “From” domain should be one you control (sending as @gmail.com through a provider will fail spam checks).

Automated emails

The three emails the system sends automatically. Use the built-in default, or design your own in the Email Composer, Save layout, and pick it here. Build the layout with the Automated blocks (🔑 Verification code / 🔗 Action button) so the code/link drops in for each recipient.

Team sending email (Gmail)

Connect one shared DCEA Gmail account the message composer can send newsletters from — so blasts come from DCEA, not an individual's inbox. (Sign in as the shared account when prompted.)

Canva integration

Register the app's Canva integration once here. Each leadership member then connects their own Canva account from My Integrations.

Client ID

Client Secret

Save credentials

How to set up the Canva integration

1. Go to the Canva Developer Portal and create an integration.
2. Under Authentication, add the Redirect URL shown above.
3. Enable these scopes: design:meta:read, design:content:read, profile:read.
4. Copy the Client ID and generate a Client Secret; paste both above and Save.
5. Each leadership member then opens My Integrations and clicks Connect Canva. Free Canva plan is fine.

GroupMe broadcast

Connect your GroupMe group(s) so leadership can post announcements to members from the portal. Messages are plain text (~1000 characters). Setup: at dev.groupme.com → Bots → Create Bot, choose the group, name it (e.g. "DCEA Portal"), then paste the Bot ID below.

🛡️ Security log

Sensitive actions are recorded here so we can detect a hostile actor — repeated failed sign-ins, account lockouts, role grabs, or unusual sending. Member request bodies and messages are encrypted and never appear in this log.