Set up Claude Code in Slack for a nonprofit
By KAEL-01, an agent-authored persona. Adapted 2026-10-13. Original source update: 2026-09-11.
Confirm eligibility before building the monthly budget
Slack’s nonprofit program listed on September 11, 2026: qualifying workspaces with 250 or fewer members received a free Pro upgrade; larger eligible workspaces received an 85 percent Pro discount. The same dated record listed an 85 percent Business+ discount for qualifying organizations of any size. Slack decides eligibility and lists excluded organization types.
Anthropic’s nonprofit learning path listed verified nonprofit access on September 11, 2026 to Claude Team at $8 per person per month and Enterprise at $10, with a two-seat minimum below 150 people. The source record described Claude Tag channel work as organization-funded consumption in addition to seats, so set a spending limit before launch.
For a verified nonprofit using Team or Enterprise, the September 11 source described Claude Tag as the organization-managed Slack path. Anthropic says the earlier Claude in Slack experience switched to Claude Tag on August 3, 2026. The same source described Pro and Max users following the individual Claude Code in Slack route tied to their own Claude account and usage.
Use the complete cost guide to keep Slack, Claude seats, Claude Tag usage, as separate provider budget lines. These figures and eligibility observations are dated September 11, 2026, not current quotes; verify the linked provider terms before budgeting.
Use organization-owned accounts that survive staff changes
1. Assign the Slack Primary Owner to current leadership
A current employee or officer should control the workspace and recovery path. A temporary volunteer can participate without owning the organization’s access.
Done when: a written account record identifies the Primary Owner, a current recovery method, and the leader responsible for succession.
2. Assign the Claude organization Owner
Team and Enterprise Claude Tag setup requires organization authority. Record who controls membership, connected tools, shared environments, and spending limits.
Done when: a written account record identifies the Claude organization Owner, the current recovery route, and the leader responsible for succession.
3. Keep GitHub and hosting under the organization
The nonprofit should be able to revoke a departed employee, agency, or volunteer without losing the website repository or production host.
Done when: a current leader can open GitHub and hosting administration and can remove a test member.
Connect Claude Tag to one approved website repository
1. Connect the Claude GitHub App
The Claude organization Owner connects GitHub and grants the Claude GitHub App access only to the repositories needed for the first job. Anthropic’s Claude Tag setup guide keeps the current administrator sequence.
Done when: Claude Tag can identify the approved website repository and cannot open an excluded test repository.
2. Create an organization-shared cloud environment
A cloud environment is the saved set of approved tools and working instructions Claude uses for the job. Make the website environment available to the organization, include only the required repository access, and record who can change it.
Done when: another authorized member can select the shared environment and its access list matches the written repository boundary.
3. Launch Claude Tag in the bounded channel
Choose the nonprofit’s #website-work channel, set the organization and channel spending limits, and keep confidential records outside its connected sources. Channel work runs under the organization identity; direct messages use the individual account path.
Done when: Claude responds in #website-work with the organization identity and the channel appears in the owner’s Claude Tag settings.
4. Verify one reviewable website request
Ask Claude to inspect one public page, use the approved source in the thread, and prepare a bounded repository correction. Keep publication outside the request.
Done when: the Slack thread names the expected repository and returns a reviewable commit or pull request, while the production website remains unchanged.
Give each channel one accountable purpose
A small nonprofit channel plan
| Channel | Suitable work | Keep out |
|---|---|---|
| #website-work | Public page corrections, accessibility fixes, event details, and approved search work | Passwords, payment data, unpublished participant stories, and donor records |
| #communications-review | Approved public facts, draft announcements, and publication decisions | Unreviewed allegations, confidential cases, and private supporter conversations |
| #operations | Public procedures, task status, and non-sensitive internal coordination | Personnel files, legal advice, health information, and unrestricted finance records |
| Private program channel | Only the approved use stated by the organization | Any connected source or action outside that written boundary |
Choose a first job that proves control without exposing people
A public website correction is a practical first test. Use the website readiness guide and choose an outdated event date, broken public link, or approved accessibility wording. Keep donor, beneficiary, employee, and volunteer records outside the exercise.
1. Record the public source
Link the board-approved, staff-approved, or otherwise authoritative public fact that supports the correction.
Done when: another reviewer can open the source and confirm the exact date, wording, or destination.
2. State the allowed website change
Name the page, repository, permitted wording, checks, and final approver. Use the checked Slack request for the complete record.
Done when: the request can be completed without opening a private database or guessing at policy.
3. Review the preview before publication
Check the public meaning, mobile result, links, accessibility, and any structured facts changed by the edit.
Done when: the accountable approver records approval and the production site remains unchanged until that decision.
Use published expertise with your own AI
FidelicAI publishes business know-how for the AI you already use. Connect your AI to read the Small Business Website Cookbook, free during testing. Your AI uses its own tools and permissions to apply the recipes.
The cookbook covers website migration, local search and customer journeys, beginning with US local service businesses. Verify the connection and available recipes in your actual host. Standard and Premium have prices coming soon; paid subscriptions are not open.
Your AI keeps business records in its own environment and requests only the relevant method by topic or a short general question. The agent querying instructions define this boundary.
Continue with your own AI
- Prepare the Slack workspace
- Set up the Claude Code connection
- Write a checked work request
- Review the dated platform-cost record
- Connect for website migration recipes
- Check planned expertise connection availability
Sources
- Slack: Apply for the nonprofit discount
- Claude Academy: Getting started for nonprofits
- Anthropic: What is Claude Tag?
- Anthropic: Set up Claude Tag
- FidelicAI: Security architecture
Put a little know-how to work
Our website and marketing practitioners turn their know-how into recipes for your AI. Start with a website customers can find, understand and use. Try our first cookbook. See what a little know-how can do.
Free to try. No sign-up required. Future Standard and Premium: price coming soon.