Skip to Content
Teams

Teams

Town now works for the whole team.

Auto-install integrations, routines, and skills on every team member’s Town account — so the whole team benefits from what’s been built.

What Teams gives you

  • Team Integrations — connect a tool once at the team level, and everyone’s Townie can use it
  • Installable Routines — reusable blueprints that each member can install on their own account
  • Group Routines — shared automations that run on the team itself, collectively owned
  • Skills — best practices encoded once, used by every Townie on the team
  • Town in Slack — @Town for every member, plus a shared anonymous assistant

Your personal assistant stays personal. Teams just gives it more to work with.

Getting started

Create a team in three steps:

  • Click your avatar in the bottom-left.
  • Hover Teams and choose Create a team.
  • Invite members by email.

Once your team exists, the team menu becomes home base — manage members, routines, skills, integrations, and rules from a single sidebar.

Roles

Every team member has one of three roles. Roles set the default permissions — you can refine them with Access Rules.

  • Owner — Full control. Top-level authority over the team: billing, deletion, and every admin action.
  • Admin — Operate the team. Invite members, manage integrations, publish routines, and control access rules.
  • Member — Use the team. Install team routines, use shared integrations, and benefit from team skills day-to-day.

Access rules

For each action on the team, the admin can select the level of permissions. Tighten things down for sensitive actions, or open them up so anyone can contribute.

Default settings:

  • Manage integrations → All members
  • Create installable routines → Admins & owners
  • Invite members → Admins & owners
  • Create skills → Admins & owners

Your admin sets the guardrails. Your team moves within them.

Team Integrations

Install integrations once at the team level, and have them ready on every member’s account.

Connect Slack, Gong, Linear, Notion, and more from the team’s Integrations page. Once connected, the integration is available to every member by default — no individual setup needed.

For each integration, choose who can use it:

  • All members — Every team member can use this integration.
  • Restricted to specific members — Only the people you select can use it.
  • Only Team Routines / Assistant — Members can’t use it directly — only team-owned routines and the team assistant can.

Keep Gong scoped to sales. Limit sensitive systems to team routines only. Open productivity tools up to everyone.

One thing to know: whichever account is used to sign into a team integration is what gets shared with everyone. Use a regular-access account, not an admin one.

Installable Routines

Reusable blueprints. Each member can install them onto their own account — running uniquely with their identity, on their data.

Turn any routine into a blueprint:

  • Open a routine that already works on your account.
  • Click Create Installable Routine.
  • Decide: auto-install for the whole team, or let members add on their own.

Town starts an assistant session that walks you through publishing it — including whether it should auto-install for everyone.

For routines that don’t auto-install, members can find them under the Explore tab in Routines or in Team. One click installs — and it runs on their personal account, with their unique data.

Same logic. Personalized output. No one has to build it from scratch.

Group Routines

Routines that run on the Town team itself — not on any single member’s account. One shared instance that everyone can edit and improve over time.

Use a Group Routine when you want a single routine the whole team can update and improve together — like a ticket triager or a routine that pulls materials together before a recurring meeting.

Examples:

  • Ticket triager — Auto-categorize incoming tickets, route to the right owner, and keep a shared backlog tidy.
  • Meeting prep — Gather docs, agenda items, and customer context for a recurring team meeting.

Group Routines vs. Installable Routines

Installable RoutineGroup Routine
Where it runsEach member’s accountThe team itself
Who owns itEach installer gets their own copyOne shared instance, owned by the team
Best forPersonal work — like standup prepCollective work the whole team benefits from

Skills

Reusable capabilities every team member’s assistant and routines can draw on — without explicit triggers.

Unlike routines, skills don’t have triggers. Your assistant decides when to use them. They’re perfect for capturing how your team writes docs, builds decks, or talks to customers — once, then everywhere.

Great candidates for a skill:

  • How to write docs — Voice, structure, length, what to include — so every doc the team produces feels consistent.
  • How to make decks — Brand guidelines, slide patterns, the tone you use with customers vs. internal audiences.
  • How to talk to users — The right voice for support replies, sales outreach, or follow-ups — encoded once.

Skills are available from the team menu and at town.com/routines/skills.

Town in Slack

Connect Slack and bring Town directly into the channels where your team already works.

Two ways to use it:

  • Personal — Every team member with a Town account can summon their own assistant by typing @Town. Same context, same memory — just inside Slack.
  • A shared anonymous assistant (new) — Anyone in your Slack workspace can use @Town as a team-wide assistant — with access to the integrations you choose.

Configuring the anonymous assistant

The anonymous Slack assistant inherits whatever you let it access. Use the same integration access controls:

  • Open it up — Let the team Slack assistant use Notion, Google Drive, Linear — anything safe for everyone to query.
  • Lock it down — Keep sensitive integrations restricted to admin members — the anonymous assistant won’t see them.
  • Expose just to the assistant — Use “Only Team Routines / Assistant” when you want @Town in Slack to query something members can’t touch directly.

That’s Town for Teams

  • Integrations — one connection, the whole team.
  • Installable Routines — reusable blueprints, each member’s own.
  • Group Routines — shared automations, collectively owned.
  • Skills — best practices encoded once, used everywhere.
  • Slack — @Town for every member, plus a shared assistant.

Teams lives at town.com/teams. If you’re already on a team, it shows up in your side nav automatically.

Last updated on