The two-type model
Every team member in your workspace belongs to one of exactly two account types. The type decides who owns their Solavel account, what workspace-wide capabilities they can ever have, and how much of their profile you can manage.
| Type | Owner of the account | Workspace-wide capabilities | Per-organization role | Typical example |
|---|---|---|---|---|
| Company | Your workspace | Optional Workspace builder | Yes | An employee at name@acme.com |
| Independent | The user themselves | Never | Yes | A contractor at name@gmail.com, an external accountant at name@theirfirm.com |
There is no third type. Everything reduces to one question: do you own their account, or do they?
When to choose Company
Pick Company when:
- The user has an email at your company's domain
- They're an employee — on payroll, part of your org chart
- You want them able to receive Workspace builder rights
- You want their account to live entirely inside your workspace
Effects of Company:
- They show up on your Team page as a Company employee
- Workspace owners can grant them the Workspace builder toggle (see Workspace builder)
- You can manage their workspace-side details (such as display name) from the Team page
When to choose Independent
Pick Independent when:
- The user has their own email at their own domain
- They're a contractor, accountant, freelancer, partner, or external consultant
- They might be working with other workspaces too — their account shouldn't be tied to yours
Effects of Independent:
- They show up on your Team page as Independent
- You cannot grant them Workspace builder or any other workspace-wide capability
- Giving them a role in one of your organizations affects that organization only — their account stays their own
- They can leave your workspace and join another without losing their account
What stays the same
Regardless of type, both share the same per-organization capabilities:
- Per-organization role (Owner, Manager or Member) — same options for both
- What each role can do (manage team, manage settings, manage billing) — driven by the role, identical for both
- Project access inside organizations — controlled per project, same rules
So if you just want someone to "use SolaBooks in Org A as a Member", the type barely matters. Pick Company if you own their email domain, Independent if you don't.
How the type is set
- At invitation time. When you invite someone from the Team page, Solavel detects the type from the invitee's email domain: if it matches one of your workspace domains (see Workspace Settings), the invitation defaults to Company. You can review it before sending.
- It's locked after acceptance. Once the user accepts and creates their account, the type is fixed. You don't toggle it later.
What you can manage
| On a Company user | On an Independent user |
|---|---|
| Workspace builder toggle | (Workspace builder is never available) |
| Role in any organization you own | Role in any organization you own |
| Project access in any organization you own | Project access in any organization you own |
| Display name (workspace-side) | — |
You can never manage an Independent user's:
- Email or password (it's their account)
- Display name on their personal account
- Membership in other workspaces
See also
- How Solavel works
- Workspace builder
- Workspace Settings — where you set your company domains
- Account types and roles