Adding people to Spodus is a billing decision, so it is worth knowing the shape of it. Spodus is priced per seat: everyone you invite holds a login, and every login is a seat, whatever their role. What you do not get is a ladder — one flat rate per seat, the hundredth the same as the first, with no tier you outgrow as the team grows. The people who cost nothing are your customers, who use the support portal without an account at all.
Adding people
Invitations go out by email. You can send one from Settings → Team, or without leaving what you are doing: the share panel on any board has an Invite to workspace action that opens the same form over the page you are on. Pick the person's role as you invite them; they set their own password and sign in.
One limit worth knowing before you look for it: only an Owner can grant the Owner role. An admin sending an invitation will not see it in the picker, because offering a choice that would be refused is worse than not offering it.
Roles
Five roles ship with every workspace:
| Role | What it is for |
|---|---|
| Owner | Full access to everything, including billing and deleting the workspace. |
| Admin | Manage members, boards and settings. Cannot delete the workspace. |
| Member | Create and edit records across shared boards. The everyday role. |
| Billing manager | Plan, invoices and payment methods only — nothing else. |
| Guest | Read-only access to the records shared with them. |
Owner is a system role and cannot be edited or removed. Assign the least privilege that lets each person do their job; a Billing manager who never opens a record is a perfectly good use of a seat if that is genuinely all they need.
Permissions
A role carries a set of permissions, in two groups. Data: view records, create and edit, delete, and export to CSV. Admin: manage members, manage billing, API and webhooks, and manage automations.
Permissions are not only workspace-wide. Boards are shared individually, so someone can be a Member with full edit rights on the boards they work in and have no access at all to the ones they do not — which is what makes Guest useful for a client or contractor who should see one project and nothing else.
Removing and offboarding
When someone leaves, reassign their open deals first, then remove their access. Records and activity they created stay attributed to them, so your history does not develop holes where a person used to be.
Removing someone frees their seat, and the change follows on your next invoice.
Why this matters
On a single-purpose CRM, everything the CRM does not do becomes another subscription — and every one of those has its own per-seat bill. Spodus breaks that link a different way: one seat carries all five products, so giving someone access to support, invoicing and the CRM costs what giving them the CRM alone used to.
