Skip to main content
For admins, Nova works across most of the platform. This page lists what you can hand over and what happens to the result, so you know whether a request needs publishing before customers feel it.
If you aren’t an admin, Nova works on tickets. It reads a ticket and its related tickets, runs the AI Agent’s lookups, and fills in an AI Agent action for you to review before it runs. It can also take you to a page in the platform. Everything else on this page needs the admin role.

​
Configuration

These requests change how the AI Agent behaves. Every one of them lands as a draft, so nothing reaches customers until you publish. See Reviewing and publishing Nova’s changes.
Handoff conditions are the hardest thing to write from an empty field. Asking Nova to draft them first, then editing what it proposes, is usually faster than starting alone.

​
Testing

Tests run against your latest drafts, so you can check a change Nova just made without publishing it first. See Simulator.

​
Analysis and reporting

These are read-only. Nova reads data and explains it, and changes nothing.
When Nova answers a product question, it reads the live public documentation rather than relying on what the model already knows, so answers track the current product.

​
Your workspace

​
What Nova won’t do

  • Publish. Nova prepares changes. A human always publishes them.
  • Reply to customers. That’s the AI Agent. Nova only configures it.
  • Take over a ticket. Handling a conversation stays with a Human Agent.
  • Submit feature requests. Bug reports only, for now.
  • Touch another user’s personal view. Nova can’t see or change it, even when you’re an admin.
  • Find a view that isn’t in your tabs. Nova sees the same views you do.
  • Reorder your tabs, or touch your unsaved changes. Both live in your browser, not in your account.