Team Setup

Get your team configured in a few minutes.

Billing and seats

An organization owner or admin manages the trial, subscription, and cancellation in Billing. Active developers and pending invitations count as seats. Checkout confirms the team total and first charge date before you subscribe.

Creating a team

Teams are the central unit in Tenpace. Everything — channels, members, webhooks, reminders — belongs to a team. When you first sign up, a team is created for you automatically.

You can create additional teams (e.g., for separate business units or clients) from the team switcher in the navigation bar.

Inviting team members

Invite members from the Organization → Members page. Each invitation sends an email with a link to accept and join the team.

Organization owners and admins manage membership and billing. Team members have two roles:

Role	Permissions
Member	View dashboards, receive notifications, link their accounts
Admin	Everything above, plus manage channels, webhooks, and team settings

Linking GitHub accounts

For Slack @mentions and personalized digests to work, each team member needs to link their GitHub account. They do this once from their Profile page.

After linking:

• When they're requested as a reviewer, they get @mentioned in Slack.
• When they submit a review, the PR author is notified.
• They receive the daily digest (if enabled).

Members who haven't linked yet still appear in PR messages by their GitHub username, but without Slack @mentions.

Linking Slack accounts

Linking Slack happens separately from GitHub. Members go to their Profile → Connections page and click Connect Slack. This identifies their Slack user ID so Tenpace can DM them directly.

If your team uses multiple Slack workspaces, members can link a different Slack identity per workspace.

Configuring notification channels

Adding a channel

Go to Channels and add a Slack channel. During setup:

1. Choose the Slack channel to post to.
2. Select repositories to watch (or leave blank to watch all).
3. Configure optional filters (GitHub labels, file paths).
4. Set the reviewer mention policy.

Multiple channels

You can configure multiple channels for different purposes:

• #prs-frontend — only the acme/frontend repo
• #prs-backend — only the acme/backend repo
• #prs-all — all repos, no filters (catch-all)

Daily review summaries

Personal briefings use each member’s Profile → Timezone and arrive around 9 AM on weekdays when there is work that needs attention.

For a shared channel summary, open Channels → your channel → Daily Review Digest. Choose the delivery time, timezone, stale-after-days threshold, and which PR states to include.

Team switcher

If you're a member of multiple teams, use the team switcher in the top navigation to switch context. All settings, channels, and webhooks are scoped to the active team.