Everything in Bloggable belongs to an account, and everyone you invite joins that account — sharing its blogs, its credit pool and its billing.
Roles
| Role | Can do |
|---|---|
| Owner | Everything, including billing and cancelling the plan |
| Admin | Settings, team, personas, archiving blogs, all content work |
| Member | Create and edit content, run AI actions, publish |
| Viewer | Read-only — can see the work and the analytics, change nothing |
Billing is owner-only. Team management and account settings are owner or admin. Permanent deletion of content is reserved for owners.
Joe respects exactly these boundaries. A viewer can ask Joe anything and get real answers, but Joe won't perform an action their role doesn't allow — the tools simply aren't offered to him. There's no route around the permission model through the assistant.
Inviting people
Owners and admins invite by email from Settings → Team. Your plan sets how many seats you have; Settings → Billing shows the live number for your account.
Two known limits worth planning around:
- Roles are account-wide. You can't currently scope a member to a single blog.
- A user belongs to exactly one account. There's no account switching, so someone who works with you and with another Bloggable customer needs separate logins.
Viewer seats and clients
Viewer is the seat to give a client or a stakeholder who wants to watch without touching. Note that ownership transfer isn't built yet — you can't hand a blog over to a client's own account, so agencies should plan to keep client blogs under their account.
Personas — bylines without seats
A persona is a virtual author: a name, a bio and a photo, with no login and no seat cost. Use them to byline posts under a pen name, a brand voice, or a subject-matter expert who doesn't need access to the tool.
Personas can be scoped to the account or to a single blog, and you can have as many as you like. Autopilot can use one as its default byline — and if you don't set a byline at all, it assigns a persona rather than publishing anonymously, because an article with a named author is treated better by both search and answer engines.
Creating a persona needs admin or owner.