Manage seats and account roles
When to use this
Use this page when you are inviting teammates, reviewing permissions, or checking whether account access matches your plan.
Seats and workspace access
The subscription includes a defined number of seats. Those seats matter because they determine how many people can actively belong to the account.
When every seat is taken, the Invite Member button in Settings tells you what to do next. On Core, it offers the Studio plan, which raises the limit from 2 seats to 5. On Studio, which already has the highest seat count, the button is disabled and the page explains that removing a member frees a seat for someone new.
Roles inside the account
BloomBoard supports role-based access so different teammates can have different levels of control.
- Owners have the highest level of control, including billing-sensitive actions. Only the owner can see saved payment methods and billing history. The owner is the person who created the account; ownership cannot currently be transferred.
- Admins can manage most team operations and the subscription itself, but not payment methods or billing history.
- Staff can work in the account without owning billing or membership management.
When you invite a teammate from Settings, you choose between admin and staff.
Why this matters
Access issues are often not bugs. They are usually one of three things:
- the person is not a member of the account
- the person is in the wrong account context
- the role does not allow the action they expected
Review both seat availability and role level before assuming an invitation or permission flow is broken.