Handling Capacity in BigPicture Resources for Users in Multiple Teams
This page is a support reference for handling customer questions about capacity and remaining capacity in BigPicture Resources when one person belongs to multiple teams and their combined availability exceeds 100%.
Use this article for similar cases where customers report that individual capacity looks doubled, inflated, or inconsistent when the same person appears in more than one team.
Issue summary
Customers may report that a person assigned to multiple teams appears to have higher-than-expected capacity in the Resources module. The most common example is a user who belongs to two teams with 100% availability in each, resulting in an individual capacity of 200%.
This usually becomes visible in aggregated views, such as monthly capacity, where remaining capacity also appears incorrect because it is calculated from the aggregated availability.
This is not necessarily a bug. Based on prior support and product confirmation, this behaviour is designed behaviour in the current BigPicture Resources experience.
What is happening
BigPicture does not validate availability across different teams to ensure the total stays at 100% for a single person. As a result, if one user is assigned to multiple teams, the total availability across those teams can exceed 100%.
When this happens:
Individual capacity may be aggregated across team memberships.
Remaining capacity may also appear inflated or misleading.
This is especially noticeable in views that show the person outside of a team-specific grouping context.
Important behaviour change to remember
Older customer observations may differ from current behavior.
Historically, some customers relied on filtering by team to effectively view capacity recalculated only for that team. However, support investigation confirmed that in the new Resources view, filters no longer change individual capacity in the same way. This is tied to a product change implemented earlier and confirmed by Product and Development.
If a customer says, “This used to work when we filtered by team,” acknowledge that their earlier experience may have been different, but clarify that the current behaviour is intentional in the new Resources view.
Current expected behavior
Scenario | Expected result | Support interpretation |
|---|---|---|
User belongs to multiple teams and total availability exceeds 100% | Individual capacity is aggregated from all team assignments | Works as designed |
User is viewed without team-specific grouping | Capacity and remaining capacity may look inflated | Expected if combined availability is above 100% |
User is filtered by team in the new Resources view | Filtering alone may not recalculate individual capacity | Expected current behaviour |
User is shown with Teams/Individuals grouping | Capacity can be interpreted in the context of a single team row | Recommended workaround/view configuration |
Recommended support response
Use the following guidance when replying to customers:
Confirm the symptom: the same user belongs to more than one team and total availability exceeds 100%.
Explain that BigPicture currently allows total availability across teams to exceed 100%, so capacity may be aggregated accordingly.
Clarify that in the new Resources view, filtering alone no longer recalculates individual capacity as some customers may remember from older behaviour.
Recommend using grouping + filtering, especially the Teams/Individuals grouping, to get a team-context view.
Advise the customer to adjust team availability values so the user’s total availability across all teams sums to 100% if they want standard capacity calculations.
Best practice: when a person participates in multiple teams, distribute their availability across those teams so the combined total remains at or below 100%.
Suggested customer-facing wording
This behaviour is expected in the current BigPicture Resources view. If a user belongs to multiple teams, their total availability across those teams can exceed 100%, and their individual capacity is then aggregated accordingly. In the newer Resources experience, filtering alone no longer recalculates individual capacity the way it may have in older behaviour. To get a team-specific planning view, we recommend using the Teams/Individuals grouping together with filters. If needed, please also adjust the user’s availability across teams so that the total sums to 100%.
Troubleshooting checklist for support
When to escalate
Do not escalate if the case matches the known pattern below:
The user belongs to multiple teams.
Total availability is above 100%.
The complaint is that filtering no longer recalculates individual capacity.
The behaviour matches the current Resources view design.
Consider escalation only if:
The customer shows evidence that capacity is incorrect even within the recommended Teams/Individuals grouping context.
The calculation is inconsistent for users whose total availability does not exceed 100%.
The behaviour differs from the currently confirmed design in a reproducible way.
Known resolution path: explain designed behaviour, recommend grouping plus filtering, and advise balancing team availability so the total equals 100%.
Internal notes for future cases
The change affecting filter behaviour in the new Resources view was linked internally to a completed product task.
For customer communication, focus on what the product does now and the practical workaround, rather than debating historical behaviour.