> For the complete documentation index, see [llms.txt](https://polser.gitbook.io/polser-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polser.gitbook.io/polser-docs/admin/ways-to-set-up-your-team.md).
# Ways to set up your team
Polser is a highly adaptable tool that conforms to your team's current workflows, not imposing new ones. Here, we discuss some of the common configuration models we frequently encounter.
Before you invite anyone or assign a single number, it's worth deciding how your team will be organised around WhatsApp. That choice shapes everything that follows, so it's the first thing to think about.
Our customers usually go for one of three main setups that we present here. There’s no single “right” choice; it all comes down to what fits your team’s workflow. On this page, you’ll find a quick overview of each option, so you can choose what works best for you or even blend ideas from all three!
### One number, multiple users
A single WhatsApp number, shared by several users who between them handle everything that comes in. Work is divided using **conversation assignees** (deciding who takes which chat) and **labels** (to organise and find conversations), rather than by giving people separate numbers.
Because there's only one number, the number-visibility setting isn't the lever here: everyone is working the same line.
This is the setup for a small university admissions team, or a support team in a mid-size company, where a group of people share the load on one channel.
### Multi-number by department
Each department has its own WhatsApp number and its own team working it. For example: marketing on one, sales on another, technical support on a third. Users are grouped around the number their department owns.
In this setup it's usually fine for one department to see another's conversations (it can give them valuable context), so visibility is typically left open (all users see all numbers). It's also the setup where **transfer chat** earns its keep, handing a conversation from one department to another when an enquiry lands in the wrong place.
This suits larger organisations running Polser across several functions at once.
### Multi-number, one per user
Each user works from their own dedicated number. A sales team is the classic example, every rep on their own line, working their own contacts directly, but the model fits anyone who needs a personal number rather than a shared one.
Here it usually matters that each user sees only their own conversations, so visibility is set so that users see only their assigned numbers. Clean, private, and separated per person.
Each of these models maps to a choice in Polser's **Phones visibility** setting, and to how you assign numbers to people. Once you've decided which model fits, see **Users & Numbers** for how to set it up.
