Skip to main content
GameDev.net gamedev.net

How Teams Work

A Team is a shared home for a group of people making something together — a hobby game, a jam entry, a class cohort, a studio. This page explains what teams are for, when to use one, and how they differ from a forum topic.

When should I create a Team?

Create a team whenever more than one person is collaborating on the same thing, or when you want a durable place that represents the group rather than a single thread. Common reasons:

  • You're recruiting collaborators on a hobby project and want a real page people can find, not a forum thread that disappears in a week.
  • You're running a game jam team and need a short-lived but focused space for the event.
  • You're a studio or company that publishes devlogs, manages multiple projects, and wants a verified presence.
  • You're an instructor running a class or cohort and need roster management and assignment tracking (coming soon).
  • You're a learning group or hobby club that meets regularly and wants shared resources.

Team vs. Forum post

Forums are for conversations. Teams are for groups. If you're looking to assemble people around a project, a forum post is the wrong tool — it scrolls away, has no member list, no application inbox, and no lasting identity. A team fixes all of that.

Forum topic

  • Good for asking a question or starting a conversation.
  • Scrolls off the front page in days.
  • No member list, no application tracking.
  • Hard to find again later.

Team

  • Dedicated profile page with logo, banner, and description.
  • Open-role recruitment posts with an application inbox.
  • Member roster with roles and titles.
  • Announcements, resources, milestones, optional private forum.
  • Durable identity that lasts beyond one conversation.

Team types

You pick a type when you create a team. The type tweaks the defaults and will unlock type-specific features over time (for example, school teams will get assignments and grading).

🎮
Project team
One focused game or tool; small group of collaborators.
Jam team
Time-limited collaboration around a specific jam or event.
🏢
Studio
Ongoing entity with multiple projects over time.
💼
Company
Professional entity; supports staff or domain verification.
📚
Learning group
Study together, share exercises, give each other feedback.
🎓
School / class
Instructor oversight, cohort management, and (soon) assignment grading.
🎲
Club / community
Hobby group, local meetup, or social community.

What comes with every team

Team profile

Logo, banner, tagline, description, external links, and tags.

Members & roles

Owner, admin, member, viewer, instructor, mentor, alumni — each with sensible default permissions.

Recruitment

Post open roles with commitment level and experience expectations. Applications land in your team inbox.

Announcements

Pinned team updates that reach every member.

Resources

Share files, links, docs, tools, and reference material with your team.

Milestones

Track goals and deadlines across projects.

Verification

Staff verification or email-domain verification for credibility.

Visibility controls

Public, invite-only, or fully private — pick what fits your group.

Visibility options

Visibility In listings? Profile viewable? Accepts applications?
Public Yes Anyone Yes
Invite only Yes Anyone Invitation only
Private Members only Members only Invitation only

For educators

Running a class this semester? School teams default to private visibility and add assignments, grading, and bulk-invite tools. Verified .edu teams get a priority review.

Read the educator guide →

Ready to start one?

Creating a team takes less than a minute. Pick a type, give it a name, and you can invite people right after.

Questions or feedback about teams? Get in touch.