Audience: owners, managers Difficulty: new user
What this covers
How to add a colleague to your organization in two places: the parent app (Solavel workspace, where they get access to your organization at all) and the finance app (where you assign their role inside your accounting books).
You usually need to do both for a new hire to be productive.
Step 1 — Add them to the parent organization
This grants the basic right to enter your workspace.
- Sign in to Solavel.
- Go to Portal > Organizations.
- Click your organization, then Members.
- Click Invite Member.
- Fill in:
- Email — your colleague's email address.
- Name — display name.
- Role — pick one:
- Client Owner — full control over the organization (settings, billing, all members).
- Client Manager — most controls, but cannot assign roles or change subscriptions.
- Client Member — view-only on the workspace.
- Click Send Invite.
Solavel emails the colleague an invitation with a signed setup link. The link is valid for the standard window — they should accept within a few hours. If they don't see the email, ask them to check spam, then resend from the same screen.
When they accept, they choose a password and land on your workspace.
Step 2 — Decide their finance role
The parent role above governs workspace access. Their finance permissions are a separate thing. Decide which finance role they need:
| Solabooks role | Who | What they can do |
|---|---|---|
| Owner | Founder, finance director | Everything, including settings, period unlock, account deletes |
| Manager | Day-to-day controller | Most things, except system settings, period unlock, hard deletes |
| Member (Accountant) | Bookkeeper | Sales, purchases, payments, journals, reports — no settings, no deletes |
| Approver | External reviewer | View + approve fixed-asset workflows only |
If they only need to look at reports, Member is the right starting point. You can layer extra permissions on top per user.
Step 3 — Assign their finance role
- Open Solabooks (Launch Solabooks).
- Go to Settings > Users (requires
users.manage). - Click the colleague's row.
- Pick the Solabooks Role from the drop-down.
- (Optional) Tick or untick individual permissions to override the
role's defaults — e.g. give a Member the
reports.exportpermission. - Click Save.
The change takes effect on their next page load. They do not have to sign out and back in.
Step 4 — Project access (optional)
If your plan includes Projects (tracker.manage_projects) and you
want the colleague to see only certain projects:
- Open the Project the user should see.
- Click Members > Add.
- Pick the user.
- Set their Project Role (Lead / Member / Viewer).
A user with no project membership but with the Member finance role will still see the AR/AP screens and the books — they just won't see project-level dashboards.
Common scenarios
"My new accountant only needs to enter bills and invoices." Parent role: Client Member. Solabooks role: Member. No extra permissions.
"My business partner is a co-owner." Parent role: Client Owner. Solabooks role: Owner.
"My external auditor needs read-only access for one month."
Parent role: Client Member. Solabooks role: Member. Then untick everything
except reports.view, reports.export, and the *.view permissions.
Remove them from the workspace when the audit is over.
"My junior should not be able to delete anything."
Parent role: Client Member. Solabooks role: Member. The Member role
already excludes hard-delete permissions; do not grant journals.delete_hard,
transactions.delete_hard, or any *.delete_permanently.
Removing a team member
- Portal > Organizations > [Org] > Members.
- Click the row > Remove from Organization.
- Confirm.
The user loses access to your workspace immediately. Any documents they created stay attributed to them — Solavel does not rewrite history.