Teams and visibility in TatvaCRM

Updated 31 May 2026·5 min read

How to set up teams in TatvaCRM and use them with visibility scopes. Single-team and multi-team users, team-based visibility, and how to design teams for your sales structure.

Teams in TatvaCRM group your users together for visibility purposes. They’re what makes the team visibility scope work. This page covers how to set up teams, how multi-team users work, and how to design your teams to match your sales structure.

Why teams exist

Without teams, only two visibility scopes work: own (only my records) and everything (all records). Teams enable the middle layer — team (records owned by my teammates).

How to create a team

Go to Settings → Teams
Click + New team
Name the team (e.g. “North Zone Sales”, “Closers”, “Inside Sales”)
Optionally pick a team lead (used for reporting hierarchies)
Add members from the team-member picker
Save

How team-based visibility works

When a user has team visibility on a module (set via their role), they see every record owned by anyone in any team they belong to. Examples:

Sneha is in the West Borrowers team. She has team visibility on contacts. She sees contacts owned by her, plus contacts owned by other West Borrowers team members. She doesn’t see contacts owned by the East Borrowers team.
Karthik is in both West Borrowers and Banker Relationships. He sees contacts owned by anyone in either team.

How to design teams for your sales structure

By geography

Most B2B sales orgs split by zone or region. North, West, South, East — or Mumbai, Pune, Delhi, Bangalore. Useful when each rep’s book of business is geography-specific.

By role

Hunters (SDRs) vs Closers (AEs) vs Customer Success. Useful when each role manages a different lifecycle phase. SDRs see leads; AEs see deals; CS sees customers.

By customer segment

SMB, Mid-Market, Enterprise. Useful when sales reps specialise in account size.

By product line

For multi-product businesses. Each rep specialises in one product family.

Multi-team users

A user can belong to multiple teams. Their team visibility is the union — they see records owned by any member of any of their teams.

This is useful for: people in dual roles (a senior rep who also helps coach juniors), regional managers (who belong to all the teams they oversee), and people who span two product lines.

Teams ≠ permissions

Membership in a team only affects visibility (whose records the user sees). It doesn’t change what permissions the user has (read, edit, delete). Permissions come from the user’s role. A Member in any team is still a Member — they can’t delete records just because their teammates can.

Reassigning a record’s owner

When you reassign a contact’s owner from User A to User B, the contact’s visibility immediately follows User B’s team membership. This is the normal way to “move” a contact from one team to another — just change the owner.

Common questions

“Do I need teams if my company has 4 people?”

Usually no. For small teams, give everyone everything visibility — they all see all the records, and the simplicity is worth more than the access control. Set up teams when you have 8+ sales people or when there’s a clear reason to limit visibility.

“What happens when I remove someone from a team?”

They lose visibility to records owned by other team members. Records they personally own stay theirs and stay visible to them (just not via the team scope). Their teammates lose visibility to records the removed person owns, unless they share another team.

“Does the team lead see more than other members?”

Not automatically. Team lead is just a label. To give them broader visibility, either upgrade their role (e.g. from Member to Manager) or add them to multiple teams.