To manage multiple teams in one workspace, give each team a clear membership, one named owner, a role that sets its access, and its own projects, then agree a short set of rules for work that crosses teams. The teams keep their independence. Managers keep one overall picture, because everything still lives in one system.
Why does growth make teamwork harder?
A company of fifteen people can live without much structure. Everyone sits in the same chat. Everyone knows who handles what.
Then a second office opens, or sales gets its own lead, or a delivery team splits into two. Each group starts to organise itself. One keeps tasks on a board, another in a spreadsheet, a third in email threads. Nobody planned it. It simply happened, team by team.
The result is a set of islands. Each team works well inside its own borders. The trouble starts at the borders: a handover from sales to delivery, a request from HR to IT, a project that needs people from three departments at once.
The manager now faces two goals that pull in different directions. Teams need room to run their own processes. The company needs to see the whole, without asking each lead for a status report every Friday.
What goes wrong when several teams share work?
The problems look different in every company, but the same five come up again and again.
- Each department has its own tasks and processes. Delivery works in sprints, sales follows a pipeline, HR runs requests with deadlines. Forcing one process on all of them breaks at least two.
- People sit in several projects at once. A designer supports two client projects and an internal one. Without one system, nobody sees the full load on that person.
- Not everyone needs access to everything. Salary data, client contracts and draft plans should stay with the people who own them. When the only choice is "all or nothing", teams either overshare or move work into private files.
- Ownership is unclear. Ask "who is responsible for onboarding?" and three people answer. Or nobody does.
- Managers become routers. Every request between teams passes through a lead, who forwards it, chases it and reports back. The lead’s week fills with coordination instead of work.
None of these is a people problem. They are structure problems, and structure can be set up.
How do you split work without losing the overall picture?
The order matters. Each step depends on the one before it. A team without an owner cannot decide its access, and access without teams has to be set person by person.
| Step | What to decide | Who decides |
|---|---|---|
| 1. Form teams | By function (sales, HR) or by direction (client A, product B) | Company leadership |
| 2. Define membership | Who belongs, and who sits in more than one team | Team owner |
| 3. Name an owner | One person per team, with authority to accept work | Leadership |
| 4. Set access | Which apps and data the team can see, edit or manage | Owner with the system administrator |
| 5. Link teams to projects | Which projects, boards and workspaces each team works in | Project leads |
| 6. Agree rules between teams | How requests cross borders, where they are logged, who replies | All owners together |
Form teams by function or by direction
Function-based teams mirror the org chart: sales, delivery, finance, HR. Direction-based teams form around a client, a product or a region. Many companies use both. A developer belongs to the delivery team and also to the team for one large client.
That overlap is normal. The system has to support it, not fight it.
Name one owner for each team
An owner is the person who answers for the team’s work and decides who joins it. Two co-owners sound fair. In practice they create the same confusion the structure was meant to remove.
Set access by team, not by person
Access set person by person drifts quickly. Someone joins, gets a copy of a colleague’s rights, then changes role and keeps everything. Before long, nobody can say who sees what.
Access set at team level stays readable. A new hire joins the team and inherits its access. When they move, they leave one team and join another. The detail of how roles and permissions work is covered in our article on roles and access.
Agree how work crosses team borders
This is the step most companies skip. Write down three things: where a request to another team is created, who on that team picks it up, and how the requester sees progress. A shared project for cross-team requests often works better than a direct message to a lead.
When are teams in one system most useful?
Teams in one system pay off in four situations:
- Several departments work side by side. Sales, delivery and finance touch the same clients and need the same facts.
- Projects are large. A project with twenty people from four disciplines needs groups inside it, not one long list of members.
- The company is distributed. Offices in different cities or fully remote staff lose the corridor conversations. The structure has to carry that information instead.
- People work in several directions at once. When most staff split their week between two or three projects, only one system shows their real load.
For a team of eight in one room, all of this is overhead. The structure earns its keep once the company stops fitting in one chat.
A worked example: delivery, sales and HR in one system
Take a service company of a few dozen people with three departments. Delivery runs client projects. Sales brings in new clients and hands them over. HR hires and onboards.
First, each department becomes a team with one owner. Delivery is large, so it also has two client teams inside it. Two senior developers belong to both.
Next comes access. Sales sees its own pipeline and the delivery projects it handed over, but cannot edit them. HR has its own workspace for hiring and onboarding documents, closed to everyone else. Delivery leads can see the load of every delivery member across both client teams.
Then the rules. A signed deal becomes a task in a shared handover project, assigned to the delivery owner. A new hire becomes an HR task with a checklist, and IT and the hiring manager are added as watchers.
Nothing here is exotic. The gain is that every request has a home and every person has a place.
How does Weenvo handle teams?
In Weenvo, the Teams app groups users who work together across one or more projects. A team has its own code, icon and colour, and can be linked to a company and business unit. Members can hold a team role: Member, or Time Manager, who sees and approves the time logged by everyone in the team.
A whole team can be added to a project, a board, a workspace or a role in one step. This is where structure starts saving time: access granted to the team reaches every member, and a new member gets it on joining. The Roles app sets what a team can do in each Weenvo app: Full Access, User, Observer or No Access. The Weenvo wiki on Teams describes each setting.
Each team also has its own permissions, View, Edit or Full Access, so not every member can change the team itself. Hidden Members keeps some members out of sight of the rest of the team where that matters.
Projects and tasks live in project and task management, and each department can have its own workspace in the digital workplace portal. Every Weenvo app sits behind one login, so a person who works in three teams still has one account.
Inside a team, each member holds one team role. A person who needs to approve time for one group and simply work in another belongs to two teams rather than holding two roles in one.
For a company in the middle range, the Weenvo page for medium-sized businesses shows how the same structure scales. The Free plan covers up to 10 users, which is enough to set up two teams and test the model. Start free and build the first team structure.
FAQ
Should different departments use one workspace or several?
One system with several workspaces usually works best. Each department gets its own area for documents and news, while projects, tasks and people stay in one shared system. Separate tools per department bring back the islands this structure is meant to remove.
How do you give a team access only to its own projects?
Add the team to its projects as a member and give it a role with the access it needs. People who are not in the team do not see those projects unless they are added separately. Reviewing access then means reviewing teams, not individual accounts.
How can managers see who owns each area?
Keep one owner per team and record it in the team itself, not in a separate document. When ownership changes, update the team. Everyone looking at a project then sees which team holds it and who leads that team.
Can one employee work in several teams?
Yes, and in a growing company most people will. Membership in several teams means the person inherits the access of each. Their tasks from all projects still appear in one place, so their real workload stays visible.