Solavel Solavel Docs

How Solavel works

The three-layer model

Solavel runs on a simple three-layer mental model. Every page, every permission and every menu entry in the portal sits on exactly one of these layers, and changes on one layer never silently leak into another.

Layer Name What it controls
1 Personal Account Your name, email, password, profile
2 Workspace The whole company account: workspace name, contact details, email domains, owners, team
3 Organization One company / branch / business unit inside the workspace: members, billing, apps, settings

Whenever you click something in the portal, ask yourself which of these three layers you're on. The sidebar sections mirror them exactly (see "Where things live" below).

Layer 1 — Personal Account

Your account is just you — your login. You own it. Things tied to your account:

  • Name, email, phone, password
  • Email-change verification
  • Account deletion

You manage all of this at Account Settings in the sidebar. The only things you do here are personal — workspace and organization edits live on the other layers.

If you sign out and a colleague signs in with their own login, your personal account is untouched.

Layer 2 — Workspace

A workspace is your company's container. One workspace holds:

  • A workspace name (your company name)
  • Workspace email domains (e.g. acme.com, acme.io)
  • One or more organizations (branches / business units)
  • One or more workspace owners
  • Your team — everyone with access to anything inside the workspace
  • Billing and subscriptions

A workspace is created automatically the first time you sign up. Other team members join your workspace by accepting an invitation you send from the Team page.

Workspace owners manage the workspace at Workspace Settings in the sidebar. Only workspace owners can edit this page.

Layer 3 — Organization

An organization is one specific company, branch or business unit inside your workspace. Each organization has:

  • Its own profile (name, type, registered address, logo, website)
  • Its own member roster with per-organization roles (Owner / Manager / Member)
  • Its own enabled apps — any mix of SolaBooks, SolaProjects, SolaHR, SolaFone and SolaStock
  • Its own subscriptions and billing
  • Its own settings

You can have one organization or many. Most accounts have one. Multi-entity businesses use several — each legal entity is an organization. For example, a trading company might run SolaBooks and SolaStock in its main organization, while its service branch runs SolaBooks and SolaProjects in a second one — each with its own books, its own stock and its own plan.

The sidebar's Organization section reflects whichever organization you've selected in the sidebar switcher.

The two account types

A team member belongs to your workspace in one of two ways. This is the account type model — Solavel detects the right one from the invitee's email domain when you invite someone.

Company account

For employees using your company email. Their account belongs to your workspace:

  • They were invited with a company-domain email (name@acme.com)
  • Workspace owners can manage their Workspace builder capability (see Workspace builder)
  • They use your workspace as their primary home

Independent account

For contractors, accountants, freelancers, partners — anyone using their own email at their own domain. They own their own account, not you. You only manage:

  • Their role inside organizations you've added them to
  • Their project access inside those organizations

You can't touch their personal account or anything outside the organizations you've explicitly given them access to.

See Account types for a deeper dive.

Organization roles vs workspace capabilities

This is the most common confusion point. There are two separate ideas:

Per-organization role

What someone can do inside one specific organization. Set when you invite them or on the team page:

  • Owner in Org A → manages everything in Org A only
  • Manager in Org B → manages team and apps in Org B only
  • Member in Org C → uses Org C, no management rights

Roles are per organization. The same person can be Owner in Org A and Member in Org B — they get full Owner rights in A and only day-to-day access in B.

Workspace builder (account-level)

What a Company employee can do across the whole workspace — specifically, whether they can create new organizations under it. There is exactly one toggle: Workspace builder. Independent accounts never get this toggle.

See Workspace builder.

Where things live

The portal sidebar mirrors the three-layer model:

WORKSPACE
  Home                  ← the app launcher (greeting + app tiles)
  Organizations         ← list of organizations in your workspace
  Team                  ← everyone in the workspace; invitations happen here
  Workspace Settings    ← workspace-level details (owners only)

ORGANIZATION  (when an organization is selected)
  Overview
  Members
  Projects              ← the apps this organization subscribes to
  Billing               ← Overview · Subscriptions · Payment Methods · Invoices · Transactions

ACCOUNT
  Account Settings      ← your personal profile
  Reports
  Documentation         ← these docs

The Workspace section is workspace-scoped — those links never depend on which organization you've selected. The Organization section only appears once an organization is selected in the sidebar switcher, and those links do depend on that selection.

What this means for security

The three layers are enforced everywhere:

  • Personal: only you can change your own name, email and password.
  • Workspace: only workspace owners can edit Workspace Settings, including the workspace name and company domains.
  • Organization: every organization-level action (manage team, settings, billing) checks your role in that specific organization.

A Manager in Org A who is just a Member in Org B sees the team-management options in A and not in B — automatically.

Where to go next

← All documentation