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
Background Routines — shared automations that run on the team itself, collectively owned (paid team plans)
Skills — best practices encoded once, used by every Townie on the team
Town in Slack — @Town for every member

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

New teams start on Team Free: sharing integrations, installable routines, and skills costs nothing, and members keep using their own plans. Anything that runs on the team itself — background routines — needs a paid team plan. See Team Billing & Credits.

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. Your new team is on Team Free; an Owner or Admin can pick a paid plan any time under the team’s Settings → Plan.

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.

Removing a member

An Owner or Admin can remove someone from the team at any time from the team’s members list. Removing a member takes them off the team right away — they lose access to team integrations, routines, and skills, and the seat frees up as a reusable slot (see Team Billing & Credits).

Removing someone from the team does not delete their personal Town account or stop their own routines. So if a teammate has left the company, you might still receive their routine summary emails or see mail still forwarding from their account — that’s their personal account, which the team can’t turn off. Fully offboarding a departed teammate — deleting their account and stopping those emails — isn’t self-serve today. Email support@corp.town.com and we’ll handle it.

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.

A team integration is shared. Whatever a team connection can reach in the tool through Town, every member with access to it can reach too. Most integrations connect with the account you sign in with, so use a regular-access account rather than an admin one.

If you’d rather everyone’s Townie only had access to what they can already see, use personal integrations instead.

What a connection can access

Workspace installs — Slack Bot installs into your workspace as an app, not as you. It can’t read your DMs, and it carries none of your personal access.
Account connections — Linear, Granola, GitHub, Asana, Dropbox and most others connect with your account, so the team inherits your access to that tool.
Notion is page-scoped — when you connect Notion you choose which pages and databases to share, and the team reaches only those. Notion only lets you share pages you have full access to.

Who can use it

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 the team’s own background routines can.

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

These settings control who can use an integration directly. Background routines run as the team itself, so they can still use it either way. If a tool shouldn’t be reachable by the team at all, don’t connect it at the team level.

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.

Background 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 Background 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.

A free team can’t run background routines. Background Routines run on the team and bill to the team’s plan, so they need a paid team plan. On Team Free, the team’s Routines tab shows this and Create routine is unavailable. An Owner or Admin can pick a paid plan under the team’s Settings → Plan; members should ask an owner or admin. Installable Routines aren’t affected — they run on each member’s own account and plan.

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.

Background Routines vs. Installable Routines

	Installable Routine	Background Routine
Where it runs	Each member’s account	The team itself
Who owns it	Each installer gets their own copy	One shared instance, owned by the team
Who pays	Each installer’s own plan	The team’s plan — paid team plan required
Best for	Personal work — like standup prep	Collective 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 within the Team menu and Powers .

Town in Slack

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

Every team member with a Town account can summon their own assistant by typing @Town. Same context, same memory — just inside Slack.

Billing & credits

New teams start on Team Free. A paid Team plan puts everyone on one bill and one shared pool of credits, and unlocks background routines. For how seats, pooled credits, consolidating individual plans, and ownership transfer work, see Team Billing & Credits.

That’s Town for Teams

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

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