Team

The Team page manages the people (and AI agents) working on your project.

Adding team members

Click "Add Member" from the Team page. Provide:

• Name — Display name
• Email — Used for invitations and identification
• Role — Their project role (see Projects: Roles and permissions)
• Skills — Relevant skill tags (e.g., "React", "Python", "UI/UX"). Used by Aira for intelligent task assignment.
• Capacity — Hours available per sprint. This feeds into sprint capacity calculations.
• Timezone — Their working timezone. Displayed on the Pulse page.

Roles and permissions

See Projects: Roles and permissions for the full role hierarchy: Owner, Admin, Product Manager, Team Member, Stakeholder, Viewer.

Capacity and load tracking

Each team member shows:

• Capacity — Configured hours per sprint
• Current load — Hours of tasks currently assigned to them
• Utilization — Load / capacity ratio

This information feeds into Aira's assignment suggestions. When you auto-plan a sprint, Aira considers each member's available capacity and skills to suggest task assignments.

Workload rebalancing

Aira includes a constrained rebalancing system that redistributes tasks when workloads become uneven — for example, when a team member goes on leave, capacity changes, or new tasks arrive mid-sprint.

How rebalancing works

Rebalancing follows a strict Decision Constitution — a deterministic ordering of priorities:

1. Safety and legal constraints — Mandatory escalation and blocks
2. Privacy and access constraints — Restricted evidence handling
3. Corroboration constraints — No assertions without objective support
4. Fairness floor constraints — Anti-overload and distribution requirements
5. Delivery optimization — Speed, quality, and wellbeing tradeoffs

Higher-tier constraints always override lower-tier optimizations. If no valid assignment exists under all constraints, the system abstains and routes to a human decision.

Multi-stage rebalancing pipeline

When workload imbalance is detected, rebalancing runs through a structured pipeline:

1. Proposal — Aira generates a rebalance proposal with proposed task reassignments
2. Decision — An LLM evaluates the proposal against the project's fairness policy
3. Candidate sets — Multiple redistribution strategies are enumerated
4. Shadow simulation — Each plan is simulated to predict delivery impact and risk
5. Challenge consensus — An adversarial review checks for strong negative impacts
6. Negotiation — The best candidate plan is selected
7. Human approval — The proposal is presented to you for approval or rejection
8. Application — Approved reassignments are executed

You can review the full reasoning behind each proposed move before approving.

Fairness policies

Each project has a versioned fairness policy that constrains how rebalancing works. Policies are auditable — you can see the active rules, review proposed changes, and roll back to previous versions.

Key policy mechanisms:

• Fairness floor — No member can exceed a configurable utilization ceiling
• Overflow handling — When all members with matching skills are at capacity, tasks enter a backlog overflow queue rather than being force-assigned
• Role-aware assignment — Task assignments respect member roles and skill requirements
• Growth distribution — Learning opportunities are distributed across seniority levels
• Provenance tracking — Every rebalance decision records which constraints were applied and why, creating a full audit trail

Triggering a rebalance

Rebalancing triggers automatically when:

• A team member is added or removed
• Member capacity changes
• Tasks are reassigned or unassigned
• Sprint composition changes

You can also preview a rebalance before applying it — Aira shows the proposed changes and the reasoning behind each move.

Collaboration network

Aira tracks collaboration patterns between team members based on joint task completion, PR reviews, and communication. This builds an affinity graph that the Assigner uses to:

• Suggest productive pairings — Members who work well together get paired more often
• Avoid poor pairings — Members with consistently poor collaboration outcomes are paired less
• Balance exposure — New team members get paired with different people to build cross-team knowledge

The collaboration network updates automatically from task events and PR activity. You don't configure it — Aira learns it.

Skills

Skills are freeform text tags attached to team members. Aira uses these during task assignment to match task requirements with team member capabilities.

For example, if a task involves "React frontend work," Aira will prefer assigning it to team members with a "React" skill tag.

Timezone support

Team members can have different timezones. The Pulse page displays a row of clocks showing each team member's local time, making it easy to coordinate across distributed teams.

The Pulse page

The Pulse page is a zen-mode overview of project health:

• Health card — Overall project status at a glance
• Attention items — Things that need your focus
• Zoomable calendar — Sprint and milestone timeline
• Team today — Who's working on what, with timezone clocks
• Live clock — Current time displayed prominently