Every workspace includes one user at no extra cost, with all core modules available. The owner occupies that included seat. No payment method is required while your team stays within its included allowance.
Open Settings → Billing to review the selected workspace’s allowance, occupied and billable seats, payment status, billing cycle, storage, add-ons and invoices. Billing changes and invoice access require the workspace owner or protected Account Manager role.
One included user, then pay for additional users
Each additional billable user costs €79 per month or €790 per year with annual billing. Annual billing is charged yearly. Optional add-ons, applicable taxes, discounts and prorated adjustments are separate.
CSFaaS may grant a workspace additional users at no extra cost. These explicit grants are added to the one standard included user before calculating paid seats:
Billable seats = max(0, occupied seats − (1 standard user + additional granted users)).
| Occupied seats | Additional granted users | Included users | Billable seats | Monthly seat total | Annual seat total |
|---|---|---|---|---|---|
| 1 | 0 | 1 | 0 | €0 | €0 |
| 2 | 0 | 1 | 1 | €79 | €790 |
| 5 | 0 | 1 | 4 | €316 | €3,160 |
| 5 | 2 | 3 | 2 | €158 | €1,580 |
The examples cover seats before discounts, taxes and add-ons. A promotion discounts eligible charges; it does not increase the included-user allowance. Use the current checkout and invoice for your workspace’s actual amount.
Understand occupied seats
Occupied seats include undeleted, unsuspended members and unexpired pending invitations. A member placed On hold loses workspace access but still occupies a seat. Expired or declined invitations and billing-suspended members do not occupy billed seats. A reserved seat is billable only when it exceeds the full included allowance.
Use Open Members to review the people and invitations behind the count. Cancelling an unused invitation or permanently removing an eligible membership releases its seat; temporarily placing someone on hold does not.
Inviting a second user requires billing unless an additional grant covers that user. Seat changes update the subscription quantity and can create prorated adjustments. Changing the billing cycle can generate an immediate invoice. Confirm payment when required, then verify the resulting status in Billing; closing checkout does not prove that payment succeeded.
Storage and activity history
Every workspace includes 5 GB of storage and access to its last 7 days of activity history. Additional storage costs €0.20 per GB per month.
Full activity history costs €19 per member per month, or €190 per member per year. This add-on counts current unsuspended members, including users covered by the included allowance and members on hold; pending invitations do not count. Review the server quote and total before confirming.
Connecting your own assistant through MCP is included and is managed through the workspace’s API and MCP access settings.
Invoices, discounts and billing email
Invoices retain the quantities, periods, discounts and adjustments that applied when they were issued. Older invoices can reflect a previous included-user allowance. Today’s membership or pricing cannot reconstruct a historical invoice.
Use the invoice actions to view an invoice or download its PDF. A payment-due invoice can provide an action to settle it. A paid invoice can have a zero total after a discount or credit; it does not necessarily mean money was collected.
Edit Billing email to update where billing correspondence is sent. An unavailable billing source is different from having no invoices; resolve loading errors before relying on missing information.
Payment failures and access
A failed payment can enter a retry period while existing access is retained; operations that increase costs are blocked. If payment ultimately lapses, members beyond the included allowance can be suspended. The owner retains access and workspace data is preserved. Payment recovery restores eligible suspended memberships automatically, but a separate administrative hold can still block access.
Workspace object limits
Record limits are separate from seats, storage and activity history. Adding a paid user does not change a workspace’s framework, policy, system or other object limits. When a create action reaches a limit, contact support with the workspace, object type and required capacity.