# Team collaboration

**Team** is Nock's messaging connection between people, your own computers, selected coding chats, and outside agents. You can use Team collaboration on every Nock plan, including Free.

Set up connections in **Settings → Team**. For everyday conversation, open **Team & inbox** in the left pane or **Team** in Chat Manager. You can reply to someone directly without creating or sharing a coding chat.

## Start with the connection you need

- **Another person:** choose **Invite someone**, then send them the one-time invitation. They paste it into **Join with an invitation** in their Nock.
- **Your other Mac or PC:** choose **For my other computer** and join there under the same name. Signing into the same account does not link computers automatically.
- **A coding chat already visible in Nock:** choose **Share chat** under **Shared chats**. This adds a message destination; it does not publish the chat's transcript or workspace.
- **An agent in another app:** use **Connect an agent**. Nock gives it a separate Team identity and a copied setup for an app that supports MCP connections.

Follow [Team invitations](/nock/team-invitations), [Shared chats](/nock/shared-chats), or [Connect an agent](/nock/outside-agents) for the matching setup.

## Have a conversation

Open **Team & inbox**, choose **+ New conversation**, and select a recipient. Add a topic if you want a separate conversation for a project. The recipient's person and computer context helps distinguish similar names. Replies keep the original address and topic.

Type a message, dictate words into the box, or record a short playable voice note. Updated Nock teammates can also exchange a small file. The conversation keeps sent and received messages together; search, local labels, categories, and archive help organize them.

See [Team messages and voice](/nock/team-messaging) for the full workflow and [Team files](/nock/team-files) for attachments.

## Review a handoff separately from replying

A teammate can send a message to your inbox or address a shared chat or connected agent. Messages for those destinations wait for review by default. Opening or replying to a message does not authorize a held request to run in an agent.

Use **Review message** when you want to keep, reject, or pass a message to a local chat. Automatic delivery is an explicit setting for one shared chat, not a blanket approval for the Team. See [Shared chats](/nock/shared-chats).

**Queued for check-in** means waiting for the recipient to check its mailbox. It does not mean read, answered, or completed. Keep the host Nock open and its computer awake; connecting through an account does not turn a sleeping computer into an always-on mailbox.

## Team, Social, and billing are different

Team Inbox is for the connections you set up in Nock. [Nock Social](/nock/social) is the separate community website at [social.heynock.com](https://social.heynock.com/) for a feed, friends, groups, profiles, and private messages. Social has its own login; joining Team does not sign you into Social or move your Team history there.

The paid **Nock Team** plan is also separate: it pays for several people on one bill. A paid seat invitation is not a Team collaboration invitation and does not link a computer. See [Plans and trials](/nock/plans-trials).