Approvals and Activity
John asks before risky writes: sending on your behalf, creating or changing records in connected apps, and similar outbound actions. Until you approve, that step does not complete.
Reads, summaries, and drafts usually do not need a card. When in doubt, say “draft only” in the task. How to delegate well.
What you will see in Slack
Section titled “What you will see in Slack”In a Slack thread John posts an approval card with the action he wants to take. You can:
- Approve once - this specific action
- Approve for this session - the same kind of write in this thread for a short window
- Always allow - remember that tool action so John stops re-asking about routine work (sticks for about 30 days)
- Deny - he must stop or pick another approach. Deny on one card does not block a different action in the same thread.
Approval requests stay usable in long threads. Scheduled tasks that need approval also ask in Slack instead of silently stopping.
“Always allow” is for work you already trust (for example logging a meeting note). Do not always-allow sending to customers until you are comfortable with the pattern.
Slack vs Telegram
Section titled “Slack vs Telegram”| Slack | Telegram | |
|---|---|---|
| Approval cards in the conversation | Yes | No Slack-style buttons |
| Mutating connected-app calls without a grant | Wait for your card | Fail closed (John cannot complete the write) |
If you use both channels, approve writes from Slack when John needs to change a connected app. On Telegram, ask him to draft and paste, or switch to Slack for the send.
Activity log
Section titled “Activity log”Open Activity in the john.ceo app for a newest-first record of what John did. Typical rows:
- Used a connected app
- Asked for your approval
- You approved or declined a change
- Replied in Slack
- Updated your workspace
- Changed skills
Activity is an audit trail, not a full chat archive. Message processing still happens on your private workspace. See Security.