> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sitevisit.app/llms.txt
> Use this file to discover all available pages before exploring further.
# Team workspaces
> How Enterprise team accounts work in SiteVisit — invites, roles, billing, and switching between team and personal context.
A **team workspace** is a shared SiteVisit account where multiple people can record visits, view reports, and edit action items against the same set of properties. Workspaces are the Enterprise plan — one Stripe subscription covers the whole team. Solo users on Free or Pro plans don't need a workspace; they own their data directly.
This page covers how to set up and run a workspace. For pricing, see the [pricing section on sitevisit.app](https://sitevisit.app/#pricing).
## Set up your workspace
Anyone can create a workspace by picking the **Enterprise** plan at signup:
1. Go to [sitevisit.app/start](https://sitevisit.app/start) (or hit **Subscribe** from Settings → Plan if you already have an account).
2. Choose **Enterprise** and complete checkout.
3. You become the first **admin** of the workspace — invite the rest of your team from **Settings → Team**.
The base plan includes **5 seats at $499/month**. Additional seats are **$79/seat/month**. Annual saves about 16%.
## Invite teammates
From **Settings → Team**, enter the teammate's email, pick a role, and send. They get an email with a one-click join link.
* If they already have a SiteVisit account, accepting the invite adds the workspace to their account alongside any solo properties they already had.
* If they don't have an account yet, the link takes them through signup and auto-joins them — they never see a "join later" step.
Pending invites show up on the same Team page so you can resend or revoke them at any time.
When an invited teammate first joins, any sample property still sitting on their personal account is removed to avoid duplicate "Happy Apartments" entries. Their real personal data, if any, is untouched.
## Roles
Three roles, set per teammate when inviting (and editable later):
| Role | Can do | Cannot do |
| ----------- | ------------------------------------------------------------------------------------------------ | ------------------------------------------------- |
| **Admin** | Everything — invite & remove teammates, change roles, manage billing, edit any property or visit | — |
| **Manager** | Invite members, edit any property or visit | Manage billing, remove admins, change admin roles |
| **Member** | Record visits, edit their own work | Invite, change settings, see billing |
The person who first subscribed to Enterprise starts as an admin. You can have multiple admins per workspace — recommended, so billing doesn't get stuck behind one person.
## Switch between team and personal view
If you belong to one or more workspaces, a small **context chip** appears in the app header. Tap it to scope the dashboard to:
* A specific workspace — everything under that team
* **Personal** — your solo-owned properties only (anything you created outside a workspace)
* **All teams** *(default)* — everything you have access to across every workspace plus personal data
The active context filters every list and detail view (properties, visits, action items) and decides where any **new** property you create lands. Solo users on Free or Pro don't see the chip — it appears once you accept your first team invitation.
## Manage billing
Billing is at the workspace level — one Stripe subscription, not one per seat. Any admin can open the Stripe customer portal from **Settings → Team → Manage team billing** to:
* Update the card on file
* Download past invoices
* Adjust seat count
* Cancel the subscription
Seat changes prorate automatically through Stripe.
## Rename your workspace
Admins can rename the workspace from **Settings → Team**. Click the pencil next to the workspace name to open a typeahead picker.
The picker searches a curated directory of multifamily operators (Smart Apartment Data + our CRM). Picking a row links the workspace to that **company record**, which lets us show portfolio context (active properties, units, HQ state) in your dashboard in future releases. If your team isn't in the directory, type your preferred name and choose **Use this as a custom name** — it sets the workspace name without a directory link.
## Data ownership
Properties and site visits inside a workspace are accessible to every member of that workspace, subject to their role. When a member is removed (or leaves), the data stays with the workspace — not with the individual. Personal (solo-owned) properties stay attached to the user who created them and are never visible to teammates.
The API mirrors this model: requests using an API key issued by a workspace admin see the workspace's data; requests using a personal user's key see only that user's data. See the [Authentication guide](/authentication) for how keys are scoped.
## Next steps
Free, Pro, and Enterprise side by side.
How API keys are scoped to a user or workspace.