Teams
This guide explains how to split your practice into teams so each business unit has its own clients, templates and settings, with billing on the parent.
You need the Owner or Manager role on the parent practice to create teams and assign people. Moving clients between teams requires the Owner role.
Overview
A large practice often runs as several internal businesses, such as wealth, insurance or aged care. Teams keep one subscription and one people list, and give each business unit its own practice. The parent practice stays a real practice with its own clients and templates. Each team sits under that parent.
Once teams are enabled for your practice, a Teams tab appears at Settings → Team. Contact Claras to enable it.
How it works
Each team has its own clients, meetings, file notes, documents, templates, branding and knowledge base. When you work in a team, you see that team's work. Switch teams from the name in the header.
Billing, SSO and API keys stay on the parent. Someone can belong to more than one team, with a different role in each. Their default team is where they land, and it is the role that billing uses. Each person is counted once.
A new team starts empty. After you create it, add people and share the templates that team should use.
Creating a team
Stay on the parent practice, then go to Settings → Team and open the "Teams" tab. Click Create team.
Choose a colour or logo, then name the team. Claras builds the team's URL from the parent URL plus the name. You can edit the last part before you save.
Click Create team. Billing stays on the parent.
Optionally add people who should access the team. You can skip this and add them later.
Optionally share meeting and document templates the team should use. Sharing is covered in Sharing Templates Across Teams.
You can also create a team from the header switcher when you are on the parent practice.
Switching teams
The header shows the practice or team you are in. Open it and pick another team you belong to. Parent owners can open every active team.
Lists, templates and settings then come from the team you switched to. Entity pages (a specific meeting or client) take you back to that team's list, because those records belong to one team.
People
See Invite your Team for roles, MFA and editing a person's details. When teams are on, the invite can also assign them to one or more teams at the same time.
Every person has one default team. That is their home. Additional teams are extra access. Use Change default team from the member's row menu when they should land somewhere else. Their previous default team becomes additional access.
Owners always keep access to the parent practice, including when their default team is a child team. Other roles can leave the parent after their default team is a child team.
Change someone's default team once their clients on the current team have moved. You can also use Move clients and save in the same dialog.
Clients
On a team, the clients list shows that team's clients. On the parent, the list includes clients from every team you can access, with a team column and filter.
To move clients, stay on the parent, select them, and click Move to team.... This is an owner action. Meetings, file notes and documents travel with the client. Add the client's adviser to the destination team first.
Archiving a team
Open the team's row menu on the "Teams" tab and choose Archive. Pick where members whose default team is that team, and all of its clients, should move. Extra access to the archived team is removed.
The switcher shows active teams. Include "Archived" in the filters on the Teams tab to see archived teams, then restore if you need the team again.
Frequently asked questions
What templates does a new team start with?
A new team starts with an empty template library. Share the templates it should use, or build new ones on that team. See Sharing Templates Across Teams.
How are seats billed across teams?
Billing counts each person once, using the role on their default team. Practice managers remain free. See Billing.
How are teams organised?
Teams sit directly under the parent practice.
Where do SSO and API keys live?
On the parent. Connect SSO and create API keys from the parent practice. People whose default team is a child team sign in with the parent's SSO when the parent holds the domain.
Last updated 29th September 2026 by Connor