My AI assistant won't connect or lost access — what do I do?

Most connection problems come down to one of four things: the sign-in didn't finish, the plan doesn't support connectors, a workspace was blocked, or the connection expired. Here's how to spot and fix each.

It won't connect at all

1. Use the exact URL from the page

   Copy the connection URL fresh from Settings → AI Access → Connection URL. A trimmed or hand-typed URL won't connect.

2. Finish the browser sign-in

   The first connection opens a Decisa sign-in in your browser. If nothing opens, make sure you're already signed in to Decisa in that same browser, then try again.

3. Check the client's plan

   On Claude.ai, custom connectors require a Claude Pro, Team, or Enterprise plan. Claude Code, Claude Desktop, Cursor, and VS Code work on any plan.

It connected, but sees no tools (or fewer than expected)

This is almost always one of:

• A module isn't active. Attribution tools only appear once Attribution is turned on; campaign tools once Campaign Management is on. The "What an AI client can do here" panel shows what's available — anything greyed out with "Not activated" is waiting on that module.
• Your role is limited. The assistant only gets your permissions. If your role can't see a section, the assistant can't either.
• The workspace is blocked for this connection. Check Connected apps → Workspace access and make sure the workspace isn't marked "Blocked". If it is, click Allow. See Manage and revoke AI access.

It used to work and now it's refused

• The connection expired. Each connected app shows an expiry. An expired assistant just needs to sign in again — nothing was lost.
• It (or you) was revoked. If the connection was revoked, it must complete the Decisa sign-in again to come back.
• A workspace was blocked. If only one workspace stopped working, it was probably blocked for that connection — Allow it again under "Workspace access".

The assistant says it "needs to confirm the workspace"

That's expected, not an error. Before changing anything, an assistant must name the exact workspace it's about to change. If it didn't, Decisa asks it to confirm — just let it resend the request naming the right workspace. This guardrail keeps a change from landing in the wrong workspace.

A change didn't go through

If you asked for something that spends money or alters campaigns and "nothing happened", it most likely became a draft awaiting your approval — that's by design. Open the changes/review area to approve or discard it. See Review and apply changes.

Still stuck?