Teams
Last updated: November 17, 2026
Deciding which teams to create in Rally to support the research access and tracking your organization needs.
About Teams in Rally
Teams in Rally help control access to studies, populations, sign up forms, templates, and budgets relevant to that team.
Population access is the one with the widest reach. A team’s population access determines which participants any study on that team can recruit. A study on a team without access to a population cannot reach those people, and recruiting numbers reflect that automatically. When you decide which populations a team can see, you are deciding who that team can talk to.
Guiding Principle: Access over Org Chart
Don’t assume you need as many teams in Rally as you have in your org chart. Create teams based on what they need access to. Ask yourself, "Who needs to see the same studies, participants, templates, and budgets?"
Create a New Team: Create a team when a group of people needs a "siloed" or specific space to get access to restricted data (e.g., sensitive customer segments) or separate budgets.
Combine into One Team: If the product designers, PMs, and UXRs all work on the same product area and should share the same research templates and participant pool, they should likely be in one Rally Team together.
Name for what the team covers: The name is what everyone sees when choosing a team for a study, and what anyone reviewing access reads later. Name teams for the area of work they cover rather than for a reporting line, and keep the names distinct enough that no one has to ask which is which.
Key Decision Drivers
Use the following questions to guide how you’ll create teams:
Budget Control: Does this group have their own dedicated incentive budget that shouldn't be touched by others? (If yes, create a team.)
Participant or Study Privacy: Are there specific "Populations" (e.g., VIP customers or internal employees) or Studies (e.g. Secret Project) that only this group should be allowed to access? (If yes, create a team.)
Template Standardization: Does this group require their own specific consent forms or branding that differs from the rest of the company? (If yes, create a team.)
Common Team Models in Rally
Common scenarios for a separate team:
1. Product or Business-Line Model (Most Common)
Structure: Create teams based on product areas (e.g., "Growth Research," "Mobile App Research," "Virtual Reality Research").
Best For: Organizations where research is "embedded."
Why: This keeps the participant populations relevant. For example, the "Drivers" team in a delivery app shouldn't accidentally recruit from the "Merchants" population.
2. The Research Ops & Admin Team
Structure: A restricted team for ReOps leaders and Admins.
Best For: Managing global templates, workspace-wide governance, and total incentive budgets.
Why: It allows ReOps to build and "vet" templates or screeners before pushing them out to the broader organization.
3. The "Sandbox" or Training Team
Structure: A dedicated team named "Rally Learning" or "Sandbox."
Best For: New hires or stakeholders who are just learning the tool.
Why: Users can create "fake" studies, test sign-up forms, and experiment with features without cluttering real research data or accidentally emailing real customers.
Consideration: This team earns its keep again when you roll out the Rally Agent or MCP. Setting it as someone’s default team while they learn means their early AI-assisted studies land somewhere harmless by construction, and you can move the first real one to its proper team once they’re confident. It’s the lowest-effort way to run a pilot without risking a misfiled study against a live population.
4. The Centralized Research Agency Model
Structure: One large "UX Research" team that contains all researchers.
Best For: Smaller companies or centralized research teams that work as internal consultants across many products.
Why: It centralizes all studies and participants in one place for high visibility across the entire research department.
5. The Alpha/Beta Program Team
Structure: A team dedicated to a specific early-access, alpha, or beta program, paired with its own population of enrolled participants.
Best For: Programs with a defined cohort of customers who are engaged repeatedly over months, across a series of studies rather than recruited fresh each time. Especially if these programs have specialized templates and a specific team email/reply-to address that should be used.
Why: This cohort is usually restricted, often under its own NDA or consent terms, potentialy branded separately, and typically funded from its own budget. Giving it a team keeps the program’s participants, templates, consent forms, and incentives together — and keeps them out of general recruitment.
Consideration: People running a program team almost always belong to another team as well. Make sure their default team is the one they work in most, so program studies don’t land on it by accident, or the reverse.
Multi-Team Users and Default Teams
Every study belongs to exactly one team. When someone creates a study in the Rally interface they choose which team the study belongs. When a study is created through the Rally Agent or MCP, Rally resolves the team for them:
One team — that team is used, automatically.
Several teams, with a default set — their default team is used, unless prompted or directed otherwise.
Several teams, no default — no team is assigned, and setup can’t complete until one is chosen.
Because you’ll likely have people on more than one team by design, make setting a default part of onboarding anyone to the Agent or MCP, alongside connecting their calendar and conferencing tools.
Two things to decide:
What the default should be. For most people it’s the team they do the bulk of their research in. For someone who spends most of their time in one area but occasionally works in a more sensitive one, defaulting to the everyday team is usually safer — a study that lands in the wrong place is easier to notice when the wrong place is the ordinary one.
How often it gets revisited. A default set at onboarding and never changed follows someone through a team change. Fold it into whatever review you already run when people move between teams.
A study’s team can be changed afterward if the user has the permission, so a misfiled study is recoverable. But the team determines which participants the study can reach and who can be added as study owners, so the mistake may surface as a confusing recruiting result rather than an obvious misfiling of the study.
Pro-Tips
Membership is Fluid: A user can be on multiple teams. A PM might belong to their specific "Product Team" but also the "Sandbox Team."
Start Lean: Start with fewer teams. It is easier to split a team into two later than it is to merge disparate data from two teams into one.
Visibility for Admins: Admins can see all teams regardless of membership, so you don't need to join every team just to oversee work.
Teams Are Not a Hard Wall: A study can be moved to a different team at any time, including after it starts recruiting. Someone who belongs to two teams can move a study between them if given the permission to do so through their role. Moving a study to another team impacts which participants it can reach.
Team Membership Gates Study Ownership: Once a study has a team, only members of that team can be added as owners. If a stakeholder needs to be an owner, they need to be on the team in Rally first.