What Claude can and can't do here

A connected Claude can never do more than the person who connected it. It uses your role, your permissions, and it can only see what you can see.

When you connect, you choose one of two levels:

• Let Claude look at things. It can read anything you can see in the admin pages: households, invoices, schedules, and so on. It can't change anything.

• Let Claude look and do things. Everyday changes, notes, tasks, tags, schedules, happen right away. For anything more consequential, it has to ask you first, in your browser.

An admin decides, under Club → Staff & tools, whether "look and do" is available at all for your club. Until then, every connection is look-only, no matter which level the person connecting chooses.

Whether or not "look and do" is turned on, here's what Claude can look up on your behalf, grouped the way you'd think about it:

• Members & households: household records, membership status and renewal state, and waitlist position.

• Billing: invoices and balances, outstanding payables, aging and bond totals.

• Programs: camp weeks and rosters, lap swim templates and reservations, events, pool hours, and planned closures.

• Tasks & tickets, open and recent tasks, and support tickets.

• Settings, the club's current configuration (fee amounts, deadlines, and similar details. Configured in Settings, not hardcoded).

• Activity log: the audit trail of what's happened in the admin pages.

See Connecting Claude to your club for two ready-to-use prompts (Household 360 and Board packet) that put this to work today, look-only, whether or not "look and do" is on for your club.

Once an admin turns "look and do" on, changes fall into two kinds, and the consent screen tells the person connecting exactly which one they're agreeing to:

• Everyday changes happen right away. Notes, tags, tasks, non-contact household details, schedules and rosters, and a narrow, everyday class of small transactions like recording a check that arrived in the mail. Nothing at this level messages a member or moves money beyond that narrow class.

• Anything more consequential is queued for your approval instead of happening right away. See the next section for exactly which changes those are.

Four more ready-to-use prompts put the "look and do" level to work. A treasurer's month-end reconciliation, opening a renewal season, working the membership support inbox, and running a camp week. Each on Connecting Claude to your club. Every one of them is built the same way: everything consequential it proposes lands in a single approval you review once, not a string of separate confirmations.

Claude asks you to approve, in your browser, before it:

• sends anything to a member,

• moves money: recording a check you received in the mail is the one exception,

• or changes settings, roles, or how someone signs in.

You'll get an email with a link to review and approve. Nothing in that list happens from a chat conversation alone. A browser page showing exactly what Claude is about to do is the only approval that counts.

A short list of especially sensitive actions. Minting API keys, approving other connections, exporting the whole membership list, and a few others, isn't offered to Claude at all, no matter who's connected or what they've approved.

See Connecting Claude to your club to set one up, and Disconnecting a tool to turn one off.