Teams
Understand how teams work in Fluent — what they scope, what they don't, and how to use them to organize your operation.
At a glance
- Teams segment your data. Appointments, reports, and the people who can edit interpreter and team member profiles are scoped to teams.
- Teams don’t isolate everything. Any team can assign any interpreter to an appointment, and customers (on the agency side) can be served by any team.
- Users can belong to multiple teams. A scheduler can cover two offices; a manager can be locked to one.
- Teams work the same way for agencies and organizations.
What teams are
A team in Fluent is a way to segment your data and control what your users can access. The most common reasons to use teams:
- You operate in multiple locations and want each location’s schedulers and managers to focus on their own work.
- You handle sensitive information (HIPAA, 42 CFR Part 2, court records) and need to limit who can see which appointments.
- You run distinct lines of business and want to keep their data separate.
You name your teams whatever makes sense for your operation. An agency with two regional offices might create teams called “Milwaukee” and “Denver.” A health system might create teams for each of its hospitals or for sensitive departments like behavioral health. There’s no required structure — teams are just the container you use to scope work.
Teams work the same way for agencies and organizations. The examples later in this article are split out by account type, but the underlying concept is identical.
What teams scope and what they don’t
This is the part that trips people up. Teams aren’t a wall around everything — they’re a wall around some things and a sorting mechanism for others. Here’s the breakdown:
Teams strictly scope:
- Appointments. If you’re on the “Milwaukee” team, you only see appointments assigned to that team. “Denver” appointments don’t appear anywhere — not in lists, not in search, not in notifications.
- Reports. Reporting follows appointment visibility. You can only run reports on the appointments you can see.
- Notifications. You only get notified about appointments your team is assigned to.
- Editing interpreter profiles. You can only edit profiles for interpreters on your team.
- Editing team member profiles. Same rule — managing users is scoped to the teams you’re on.
Teams don’t restrict:
- Assigning interpreters across teams. Any team can assign any interpreter to an appointment, regardless of which team the interpreter belongs to. This reflects how interpreting actually works — a remote interpreter doesn’t need to be local to take a video or phone appointment.
- Customers (agency side). Customers are organized by team, but any team can take a request from any customer. The team association is for organization, not access control.
- Vendors (organization side). Vendors are managed at the organization level, not the team level. Any team can submit a request to any vendor the organization works with.
A useful way to think about it: teams scope the work and the workforce management, not the resources you draw on to do the work.
Multi-team users
A user can belong to more than one team. When they do, they see the union of everything those teams have access to — appointments, interpreters, team members, reports.
Common patterns:
- A central scheduling team that covers every regional office. Schedulers belong to all teams and see everything.
- A regional manager who only belongs to their region’s team and is locked to that scope.
- An admin who belongs to all teams for full visibility, while individual schedulers and managers below them are scoped down.
Assigning users to teams
There are a few places to assign a user (interpreter or team member) to one or more teams:
- During the invite process. When you invite a new interpreter or team member, you select which team(s) they belong to as part of the invite.
- From the user’s profile. Open the profile edit modal from the Interpreters or Team members page and update their team assignments there.
- From the row in a list. On the Interpreters or Team members tables, there’s an ellipsis (•••) menu at the end of each row. If you have permission to edit teams, you can assign teams from that menu without opening the full profile.
These work the same way on the agency and organization sides.
Filtering by team
Teams aren’t just an access control — they’re also a way to focus your view. Two ways to filter:
- Per-page filters. Most pages in Fluent (Appointments, Interpreters, Team members, Reports, and others) have a team filter you can apply to narrow what’s shown.
- The team switcher in the top nav. A high-level team switcher at the top right of the Fluent web app lets you scope the entire app to a single team at once. Every screen you visit while the switcher is set will show only that team’s data, without you having to apply per-page filters.
The team switcher is the fastest way to focus on one team’s work for a stretch — useful when you’re operating as a regional manager or working a specific contract.
When agencies use teams
Agencies use teams to organize operations that have natural boundaries. The most common patterns:
- Geographic offices. Milwaukee, Denver, Phoenix — each with its own schedulers and local customer base. The cleanest case for teams.
- In-person vs. remote desks. A team for in-person work (which is geographically constrained) and a separate team for VRI/OPI (which can be staffed from anywhere). This isolates on-site coordination from the remote desk.
- Major contracts. A dedicated team for one large hospital system or court contract that has its own SLAs, dedicated schedulers, and a defined interpreter pool — separated from the general-pool work.
- Service specialties. Some agencies run distinct practices and prefer to manage them as separate teams. A legal practice and a medical practice, for example, might have different schedulers, different certifications, and different rate structures.
Teams give agencies the flexibility to model their actual operation. There’s no required way to slice it — pick the structure that matches how you already work.
When organizations use teams
Organizations use teams when they’re large enough that a single shared view of all interpreter activity stops being appropriate — usually for compliance reasons, sometimes for operational ones.
Healthcare
- Geographic regions or facilities. A health system with hospitals in multiple states or cities: each facility (or region) is a team, so a scheduler at one hospital only sees that hospital’s interpreter activity. HIPAA’s minimum necessary principle is the driver.
- Departments or service lines. Within a single hospital, a separate team for Behavioral Health, since those appointments carry additional sensitivity under 42 CFR Part 2 in addition to HIPAA. Same logic can apply to other sensitive specialties.
- Program type. A health system that runs both clinic visits and community home visits — different schedulers, different interpreter requirements, different workflows.
Schools
- By school or school cluster. Each school is a team, so each school’s IEP coordinators and front office only see their students’ meetings.
- By level. Elementary, middle, and high school as separate teams in larger districts.
Courts
- By division. Family court, civil court, and criminal court as separate teams. Sensitive criminal matters stay scoped to the people who need to handle them.
Government and social services
- By function. A county social services agency with separate teams for child welfare, adult protective services, and benefits administration. Different caseworkers, different sensitivities, different interpreter usage patterns.
As with agencies, there’s no prescribed way to organize. Teams are flexible — set them up to match your existing structure and the access boundaries you need.
When you don’t need teams
If you’re a small single-office agency or a single-site organization where everyone needs to see everything, you don’t need to set up multiple teams. Fluent works just fine with a single team — that’s the default.
Teams become useful when:
- You have more than one location, department, or program that should be operationally separate.
- You have compliance requirements that limit who should see which appointments.
- You have users who should be scoped to part of your operation, not all of it.
If none of those apply, leave it as one team and revisit when your operation grows.