What Claude can and cannot do
Claude works as you, inside your role and plan, sends only after your yes, and every change is recorded under your name.
Claude in Terry has your hands, not extra powers. It can only do what you could do in the dashboard, with your role and on your plan, and Terry checks every action the same way it checks a click. This page explains the limits so you can use Claude with confidence.
Nothing sends without your yes
Claude can approve a draft, send a reply, send a text, answer someone on WhatsApp, Instagram or Telegram who wrote to you first, reply to an Instagram comment, or accept or decline a LinkedIn invitation. Each one needs two things first:
- You have seen the exact subject and words. Claude shows them in the chat, or gives you a link to open the draft in Terry.
- You have said send (or accept, or decline) in the conversation.
Terry refuses any send from Claude that does not carry that confirmation. Every Terry tool also tells your Claude app what kind of tool it is, so the app knows when to ask you:
- Reads that cost nothing, such as your desk, your people or a flow, run without asking.
- Anything that spends, such as Ask Terry, Terry's read of a conversation, research, or a LinkedIn or Instagram search that uses up a daily allowance, asks you first. You can tell Claude to always allow one.
- Changes, such as a note, a draft or a rule, ask you first, and you can allow one for good.
- Sends and other changes that cannot be taken back, such as publishing a flow, enrolling people or archiving a person, ask you every time.
Drafts that Claude or Terry's agent write wait for approval like any other draft.
The usual checks still apply
Every message Claude sends passes the same checks as one you send from Terry:
- Consent rules. CASL for Canada and CAN-SPAM for the United States decide who may be written to.
- Caps. The daily limit for each mailbox, and the limit on how often one person is contacted.
- Send hours. Automated messages wait for the send hours. A reply you approve in the chat goes out at once, as it would from the Inbox, so Claude offers to wait if it is late where they are.
- Draft checks. A draft can be held for a person to read, for example when it claims an earlier conversation or touches money.
None of these can be switched off from Claude.
Claude never starts a chat
On WhatsApp, Instagram and Telegram, Claude can only answer people who wrote to that account first. It never opens a new chat. Where your workspace allows a first message at all, Terry writes it and a person sends it from the app.
Consent is your statement, never Claude's guess
When you import a list through Claude, Claude asks you where the list came from and whether you confirm the basis. It repeats back what it will record and only records it after you say yes. It never invents a basis. Recording a consent status for a person stays an admin's job, as in the dashboard.
Your role decides what Claude sees
| Members | Admins | |
|---|---|---|
| Import, research, score and update people | Yes | Yes |
| Work the inbox, draft, and send after your yes | Yes | Yes |
| Enrol people in published flows | Yes | Yes |
| Create agents, rules, templates and flows | No | Yes |
| Publish, pause or resume a flow | No | Yes |
| Step through or test a flow | No | Yes |
| Add knowledge, record consent, archive people | No | Yes |
A member's Claude is never shown the admin tools. Before a flow's first real enrolment, or one of more than 25 people, the flow needs a test. If it has none, Claude tells you so and enrols only after you say go ahead. Plan limits apply too: on Settings, Claude, Details lists what a connection can reach on your plan, and Terry checks the plan again on every call.
Everything is recorded under your name
Every change Claude makes is logged as yours. The Activity log on Settings, Claude lists each change, newest first, including the ones Terry refused or held. When the list is long, press See the full log. Your connections are listed under Details. Reads are not listed, except a check of the mailboxes and a coaching read that spends AI. Admins see the activity for the whole workspace.
Claude never sees your mailbox passwords, your connected account keys or other secrets.
What it costs
- When Claude reads, plans and writes in the chat, it runs on your Claude plan and costs no Terry credits.
- Terry's own AI is used when you ask Terry's agent to write, research or score, and always for flows. That uses your workspace's AI credits, as it would in the dashboard.
Controls for admins
On Settings, Claude, admins see a Workspace rules card. Press Change to open a short guide:
- Who may connect: Everyone the plan and Team allow, Admins only, or Off for this workspace. A change refuses the next call at once. Nothing is deleted.
- Sending from Claude: On (standard) or Off. Off stops Claude from sending and from writing or checking messages to send. Claude can still read, research, work with people and flows, and edit or reject drafts already waiting for approval. Sending then happens in Terry.
On the top card, Who connected shows how many people have connected. Press the number to see each connection, and Revoke to remove one. To disconnect everyone, open the Connection menu and choose Disconnect everyone.
A member also needs Browser extension set to Allowed under Settings, Team and seats before they can connect.
Related
In Classic
- The page is Settings, Claude Desktop. The card at the top lists what a connection can reach on your plan.
- The card What Claude has done here lists your connections and each change.
- Admins use the Who is connected card: Who may connect, Sending from Claude (On (default) or Off), a remove button for each connection, and Disconnect everyone.
- A member needs the Extension tick under Team.