Geta.Team v2.1.9 — A New Admin Settings Panel, and Two Bugs Fixed

What's new

A small but practical release. One new feature you'll see in the sidebar, two bugs squashed, and a tidier auth page.

New: Admin Settings — set your own daily email limit

Up to now, every Geta.Team instance was capped at 25 outbound emails per day per AI employee. A safe default, but rigid — if you needed more (or less) headroom, the only path was a code change and a redeploy.

That's gone.

You'll find a new Settings entry in the Admin sidebar (gear icon). Inside, there's an Email Limits section where you can set any value between 0 and 1,000 emails per day. Save it, and your AI employees pick up the new limit on their very next send — no restart, no rebuild, no waiting.

A few things worth knowing:

• Setting the limit to 0 blocks all outbound email instantly. Handy as a kill-switch during an incident, or if you want to pause your fleet without taking it offline.
• SMTP needs to be configured first — if it isn't, you'll see an amber banner and Save is disabled. A daily limit only matters if email is actually wired up.
• Existing instances are seeded with the old default of 25, so nothing changes until you decide to change it.
• Only admins and superadmins can adjust this setting.

This is also the first of what will become a proper Admin Settings panel. Future instance-wide toggles will land here rather than spawning a new sheet every time.

Fixed: Clone Employee now works everywhere

The Clone Employee feature shipped in v2.1.8 worked perfectly on our dev environment — and quietly failed on every other instance with a generic "Failed to clone employee" toast.

The root cause was a schema mismatch between our dev database and the one your instance ships with. Two leftover columns from an unfinished feature were being referenced during the clone, but didn't exist on your side. The cloning query crashed silently and the error never reached the logs (our production build strips most logging for performance).

It's fixed. Pull the latest image and Clone Employee will work as advertised.

If you tried to clone an employee since v2.1.8 and gave up — give it another go. No data was affected; the operation simply never completed.

Fixed: Widget security mode wording

In Widget Settings, the "Recommended for public websites" option used to say "Uses Claude API directly with restricted capabilities". The widget's restricted mode actually runs on Gemini, not Claude — a cheaper and better-suited model for public-facing embeds.

The label now correctly reads Gemini API. No behavior change, just accurate wording.

Refreshed: Forgot Password page

The Forgot Password page was visually inconsistent with the rest of the auth flow — older styling, no dark mode toggle, slightly off button sizing. It's been rebuilt to match the Login page exactly: same card layout, same inputs, same theme switcher (light / dark / system) at the bottom.

Same flow, same logic — it just looks like it belongs now.

Up next on the auth-page refresh: Reset Password, then a polish pass on MFA Verify and Invite Onboarding.