Approving an action

When a connected tool needs approval, open the approval request and review the proposed action before allowing it. Approvals are for connected tools such as Claude. An API key can't make these requests at all: see API keys and the public API.

Open Approvals (the card on Home when something is waiting, or search for it). It lists the requests your connected tool is waiting on you to approve; you see only your own, and nobody else can approve them for you. Select a request to open Review and approve: each proposed action is listed with what it will do, and you tick Approve or Deny for each one, then select Approve / deny checked. Nothing runs until you approve it.

Check what will change, which household or record is affected, and any amount, message, or deadline involved. Approve the action only when it matches club policy. Reject it when the details are wrong or you need to handle it another way.

A request to send a portal notice by email says "Also posted on the club's public news page" when the email will also appear on your club website, where anyone can read it. A portal notice sent by email is members only unless the request says that line, so if it appears and the message is for members only, reject the request and ask the tool to send it without posting it on the news page.

A request to show a sent email on the news page again needs your approval too, because anyone can read it there. Taking one off the news page does not need approval, since that only makes less public.

An approval does not give the tool unlimited access. Each request is reviewed separately and the completed action is recorded. See What Claude can and can't do here.

The link you get by email is for one batch of requests. It stays good for two hours. Requests that come in within 10 minutes of that email join the same batch without a new email, and the link you already have covers them. If the tool sends the email again because more requests came in later, use the newest email: the older link stops working.

Some requests also ask you to type a six-digit code, which you get by email or text. That happens for larger amounts, for anything that changes how someone signs in, and for changes to a camper's emergency contact, medical notes or authorized pickup. You have five tries. Send me a code gives you a new one, but only a few times in a row: if you see "Too many code requests", wait a few minutes.

Opening a link only unlocks the batch it came with. If you have more than one tool connected, each one's requests need their own link or code.

Sometimes a tool asks for the same thing twice, usually because its first request timed out and it tried again. If you approve both, the second one is marked skipped with a note saying it was already done. Nothing ran twice. There is nothing for you to fix.

A report export requested by a connected tool is prepared after you approve it. Approve one report download at a time. The approval page then offers the CSV and calculation details directly to you. Download them before leaving or reloading: the files are not kept online, and the connected tool cannot retrieve them later from approval history. Other pending requests remain available for a separate approval.