What Team is for
Each project (your business in somo) has its own team. In Team you invite people, decide who is an admin, choose which apps members can use and whether they can change things there, and give dabl.dev access when you want help.
Everyone can open Team and see who's on the project. Inviting, removing and app access are for owners and admins: members don't see those parts.
The page has three tabs:
| Tab | What it's for |
|---|---|
| Members | Everyone on the project, their role, when they joined and their app access. |
| Pending Invites | Invites you've sent that haven't been used yet. Owners and admins only. |
| App Access | What members can do in each app by default. Owners and admins only. |
Owner, admins and members
| Role | Can |
|---|---|
| Owner | Everything. There's one owner: the person who made the project (or the person dabl.dev handed it to). Only the owner can invite or remove admins, and only the owner can delete the project. |
| Admin | Full access to every app, plus managing the team: invite and remove members, change roles and set app access. |
| Member | Uses the apps you give them access to, at the level you choose. |
Give admin to people you'd trust with everything, including Finance and the team itself. For everyone else, use Member and set their app access.
Inviting someone
- Press Invite Member.
- Type their email address.
- Pick their Role: Member or Admin. Only the owner sees Admin here.
- Pick how long the invite works: 7 days, 14 days or 30 days.
- Add a personal message if you like. It goes in the email.
- Press Send Invite.
They get an email with a link to join. If the email service refuses the address, Team says so straight away: check it, then use Resend. An email that bounces later doesn't show here, so if they say nothing arrived, check the address in Pending Invites. Inviting the same address again also sends a fresh email.
New members start with the project's default app access (see Defaults for the whole project). Set anything different for them once they've joined.
What the person you invite does
- They open the link in the email.
- New to somo: they press Create Account, sign up with the address the invite went to, and confirm their email. They join your project as soon as their email is confirmed.
- Already have an account: they sign in with the address the invite went to and press Accept Invite.
The invite only works for the address it was sent to, so if they'd rather use a different email, invite that one instead. Once they're in, your project is in their project list.
Pending invites
Pending Invites lists every invite with its status: Pending, Accepted, Revoked or Expired, when it was sent and when it runs out.
- Resend sends the email again with a new link.
- The ✕ revokes it: the link stops working.
- An expired invite can't be used. Invite the person again.
The members list
Members shows everyone on the project with their role and when they joined. Owners and admins also see Last active (their last action in the project, from Activity) and App access: "Full access" for owners and admins, "Project defaults" for a member with no changes, or how many apps are set differently for them.
Making someone an admin
Owners and admins can switch anyone except the owner between Member and Admin with the role drop-down on their row. You're asked to confirm.
- A new admin gets full access to every app and can manage the team.
- An admin made a member again gets the project's default app access.
Removing someone
Press the bin on their row and confirm. They lose access straight away. Their work stays: tasks, invoices, notes and so on aren't deleted, and Activity still shows what they did. Their own app access settings are cleared, so if you invite them again they start on the project defaults.
Admins can remove members. Only the owner can remove an admin. Nobody can remove the owner.
Leaving a project
Members and admins can leave with Leave on their own row. You lose access straight away, and you'd need a new invite to come back.
The owner can't leave. If the project isn't needed any more, the owner deletes it in Project Settings.
Access levels Admins
For each app, a member has one of these:
| Level | What they get |
|---|---|
| Read & write | Use the app fully: create, edit and delete. |
| Read only | See its data, but change nothing. |
| Visible only (locked) | The app shows in their list, locked. They can't open its data. |
| No access (hidden) | The app doesn't show for them at all. Only for one member, not as a default. |
Owners and admins always have full access. A few core apps are always available to everyone; the App Access tab lists them under the apps.
Access counts everywhere, not just on the app's own page. For example, somo AI only reads and changes what the person could in the app itself: a member with no access to Finance can't ask somo AI for the bank balance.
Defaults for the whole project Admins
- Open the App Access tab.
- For each installed app, pick what members get by default.
- Press Save defaults.
Every member without their own setting for an app follows the default, including people who join later. Changing a default changes it for all of them.
One member's access Admins
- On the Members tab, press Manage in their row.
- For each app, leave Project default or pick a level for just this person, including No access (hidden).
- Press Save.
"Project default" keeps following the default, so if you change the default later, they get the new one. A level you pick for them stays until you change it.
A common setup: everyone gets Read only by default, and the people who do the work in an app get Read & write there. Keep Finance at Visible only or No access for anyone who doesn't need it.
Letting dabl.dev help Admins
The dabl.dev support box under the members list lets you give the dabl.dev team access to your project, for example to set something up or look into a problem. We can't see your project unless you do this.
- Pick how long: 1 day, 7 days, 30 days or until you remove it.
- Press Give access.
While it's on:
- The box says who from dabl.dev has access and until when.
- They have full access to every app, like an admin, but aren't in your members list.
- Everything they do is in Activity, marked "dabl.dev support".
- Access ends by itself when the time runs out.
Change access gives it a new end, and Remove access ends it straight away.
When dabl.dev set up your project
If dabl.dev built your project for you, we invite you first and then hand it over: you become the owner, and we stay on as dabl.dev support for the time we agreed. You can remove us any time in the dabl.dev support box, as above.
Questions
The person I invited never got the email.
Ask them to look in spam or junk. Check the address in Pending Invites, then press Resend. If the address was wrong, revoke that invite and send a new one.
They signed up but can't see the project.
They need to use the address the invite went to and confirm their email. If they signed up with another address, invite that address instead.
A member says an app is locked.
Their access to it is Visible only. Press Manage on their row and give them Read only or Read & write, or change the default in App Access if everyone should have it.
Can I make someone else the owner?
Not yourself at the moment. Contact dabl.dev if you need to.
Does removing someone delete their work?
No. What they made stays in the project, and Activity keeps the record of what they did.