From Advisor to Co-Worker
Until now, the setup assistant could read your database — it understood your fields, formulas, views, forms, triggers, and actions — and answer questions about how things were configured. That was genuinely useful for troubleshooting and learning. But you still had to go make the changes yourself.
Not anymore. The assistant can now make configuration changes directly in your database. You describe what you want, and the AI does the work.
What This Looks Like in Practice
Imagine you’re building a project tracker and you realize you need a new status field, a calculated “days overdue” formula, and a filtered view for the operations team. Normally that’s fifteen minutes of setup across three different menus.
Now you can write something like: “Add a Status field with options: Not Started, In Progress, Blocked, Done. Then create a formula field called Days Overdue that counts business days past the Due Date when Status isn’t Done. Finally, create a view called Ops Dashboard that filters for records assigned to the Operations team”.
The assistant reads your request, understands your existing configuration, and applies the changes — respecting what’s already there.
What the Assistant Can Work With
The expanded assistant has full context over your database setup, including fields and data types, with the ability to create, modify, and understand relationships between them; formulas, both reading existing calculations and writing new ones tailored to your schema; views, building filtered, sorted, and grouped perspectives on your data; forms, adjusting layouts and field visibility for data entry; and triggers and actions, understanding automation logic that’s already in place.
Because the assistant sees your actual configuration rather than a generic template, its suggestions and changes fit your database — not some hypothetical one.
A Real-World Use Case: Archiving Records
Most tables eventually fill up with records nobody needs to act on anymore — closed deals, completed projects, former clients. Keeping them around for reference makes sense, but they shouldn’t clutter the view your team uses every day. Building that kind of “soft archive” usually means stitching together a few different pieces: a way to mark something as archived, a way to act on that mark with one click, a separate place to find archived records later, and a change to the existing view so archived items disappear from daily use.
Instead of doing that piece by piece, you could write something like: “I want to configure the process of archiving completed tasks”.
The assistant reviews your current setup, analyzes if necessary fields or other components exist, and suggests a solution.

The assistant doesn’t just execute what you describe — it analyzes your request, suggests the best way to achieve it, and may recommend a better approach before making any changes.

Before making any changes, the assistant walks you through exactly what it plans to do, step by step. If you decide to proceed, it follows up with a full summary of everything that was applied — so you stay in control and have complete visibility into how your database was configured.

Why This Matters
Database configuration tends to be the part of a project that slows teams down. It requires either dedicated technical knowledge or a lot of trial and error. By letting you describe your intent in plain language, we’re removing that bottleneck.
This doesn’t replace understanding your data — knowing what you want your system to do still matters. But it lowers the barrier between having an idea and having it implemented.
Getting Started
The assistant is available directly on your TeamDesk setup pages. Just open any setup section, click “Ask a Question,” and describe what you’d like to change or create. The assistant will confirm what it’s about to do before making changes, so you stay in control.
As always, we’d love to hear how you’re using it — and what you’d like it to do next.
Have feedback or questions about the new assistant? Reach out to our support team or drop a message in the community forum.


