Service Accounts

Each thread created under a service account can be viewed by other members of the workspace. These threads are multiplayer too, so workspace members can send messages in them.

Since anyone in the workspace can drive a service account's threads, make sure to only assign credentials to it that you would be happy bestowing on all workspace members .

When to Use Service Accounts

Service accounts fit any work that belongs to the team rather than to one person. For example, threads with automations that workspace members want to have access to, even if the person who set them up is on vacation.

We've found two patterns where service accounts work especially well.

Codebase Review and Maintenance

Reviewing every pull request or keeping docs accurate is work that belongs to the team, not to a single user. When a service account owns that work, anyone on the team can step into its threads and steer them.

Here are some example prompts for setting that up via Puck:

Announced

03 Nov 2026

First seen by forck

03 Nov 2026 15:24 UTC