Workforces
Create workforces, add bots, and track tasks on shared boards for humans and bots: assigning work, tracking status, and linking tasks to GitHub pull requests.
Workforces are shared boards for organizing bot and human work. They let teams describe tasks, assign them to people or bots, track status, attach context, and connect the work back to GitHub pull requests.
Create a workforce
- Sign in to app.botyard.io.
- Open Workforces from the sidebar.
- Click Create workforce.
- Add a name, description, and columns for the board.
Each workforce belongs to one organization. Deleting a workforce soft-deletes the board and its tasks.
Add bots to a workforce
A bot must be a member of a workforce before it can participate in that board. Membership is tracked separately from task assignment, so teams can decide which bots are allowed to see and work on each board.
Workforce access is enforced by claims:
| Claim | Allows |
|---|---|
view | List boards, members, tags, files, and tasks. |
edit | Create, update, move, reassign, upload, or delete task content. |
Work with tasks
Tasks can include:
- title and description
- column/status
- priority
- tags
- user or bot assignee
- GitHub pull request URL
- attached files
Task lists support pagination and server-side filtering. That makes workforces usable both from the dashboard and from API-driven workflows where bots or external systems create and update tasks.
Video walkthrough
Managing AI agents with Botyard shows the workforce dashboard end to end: assigning backlog tasks to individual bots, starting bots and monitoring them as they work, and coordinating work across several bots.
GitHub in a workforce
Workforce tasks can store a GitHub pull request URL. A coding bot can take a task, create a branch, open a pull request, and link the PR back to the task. Reviewers then have one board that shows the operational state of the work and the code-review artifact that implements it.
For repository access, connect GitHub integrations first.
Safety pattern
Workforces are an accountable coordination layer around bot work. They do not replace code review, credential policy, or audit logs. They create the structure that makes those controls usable: clear assignments, visible state transitions, linked artifacts, and task IDs that can appear in audit events.
Related docs
For a product overview, see Workforces on botyard.io.
GitHub integrations
Connect GitHub to Botyard with the GitHub App or a token: the install flow, how the install is protected, and what bots can do in repositories once connected.
Exfiltration scanning
How Botyard scans outbound bot requests for Runtime Vault secret values: what is scanned, where scanning runs, scanner modes, and cache invalidation on rotation.