# Templates for community copy and the move-students email

Written by Geeta Thakker
Updated 2026-10-04

Describe your community by its topic, intended members, and next useful activity. When moving a class into it, use the optional personal note to explain the connection between the workshop and that activity.

## Name a learning space that can serve several cohorts

**Before:** “The Ultimate Exclusive Transformation Club.”

**After:** “AI at Work.”

```text
[Topic] for [audience]
[Topic] Practice
```

1. Choose a topic that fits the conversations you intend to support.
2. Use a name that will still make sense after this run ends; put run dates in the run name.
3. Keep the community **Name** within 80 characters.

For example, a Claude for Work cohort could continue in **AI** or **AI at Work** if the community supports that broader practice. See [Create your teacher community](/help/articles/create-teacher-community).

## Explain the community in its description field

**Before:** “Everything AI. Network, grow, and transform your future.”

**After:** “For professionals practicing AI-assisted work after class. Discuss prompt experiments, describe what you tested, and ask specific questions about checking the results.”

```text
For [audience] practicing [topic or method].
Use this community to [activity one] and [activity two].
Start by [one simple contribution].
```

The **Description** allows up to 500 characters and appears on community cards and at the top of the community. Describe activities you will actually support. Avoid promising daily feedback, regular events, or a response time unless you have committed to providing them.

1. Add the description when creating the community or update it in its settings.
2. Use **Pinned note for members** for starting instructions or posting rules.
3. If listing the community publicly, review [Publish a community profile and choose how people join](/help/articles/publish-community-profile). Keep the description consistent with the actual access setting.

## Add a personal note to the move email

**Before:** “You've been moved. Join now!”

**After:** “Thanks for practicing with us in Claude for Work. Continue in AI at Work by describing one prompt change you tested and how you checked the result. The link in this email opens the community.”

```text
Thanks for taking part in [workshop].
We practiced [specific task]; [community name] is where we will continue with [related activity].
Start by [one useful contribution, without private data].
Use the community link in this email to open it.
[Your name]
```

1. In [My classrooms](/classrooms), expand **Move students to a community or tag them** for the intended run.
2. Select your community and review **Email students a link**.
3. Paste the adapted note into **Note from you**, keeping within 1,000 characters.
4. Confirm the class and destination, then check the added and emailed counts.

This field adds a note to the standard email; it does not edit the subject or entire message. The email supplies the community link. The move adds membership before the email, so write an orientation to the destination rather than asking students to enroll again.

## Keep the note consistent with the move rules

Use a community you own or teach in. Paid communities cannot receive these moves; share their page for students to evaluate and join instead.

The first emailed move includes eligible roster students who are active destination members after the move, including people already there. Later emailed moves target newly added or re-added students. Unsubscribed recipients are skipped, and tagging without a destination sends no email. Avoid wording such as “everyone has received this.”

For membership rules, learning tags, suppressed recipients, and partial email results, follow [Move classroom students and save learning tags](/help/articles/move-classroom-students). Use the [post-class guide](/help/articles/keep-students-learning-after-class) to plan the handoff.