Workspace, Project, Blog

Three levels of structure, what belongs at each one, and why pricing sits in the middle rather than at the top.

Blogged has three levels, and almost every question about billing, limits and access is answered by knowing which level something belongs to.

Workspace            your account, your team, one subscription
  └── Project        one product, one strategy, one plan
        └── Blog     the public site readers see

Workspace#

The account. It holds your team, and it holds exactly one subscription no matter how many Projects you run.

What lives here: members and their roles, the payment method, and invoices. The multi Project discount is not held here: it is worked out per Project, from that Project's position in the workspace, and applied to that Project's own line.

Project#

One product with one blog. Everything editorial belongs to a Project: its strategy, Content Directions, topics, posts, knowledge, assets, theme, domain, analytics and settings.

The plan is attached here, not to the workspace. Two Projects in one workspace can be on different plans, billed on one subscription. This is the detail that surprises people most often, and it is deliberate: a mature product and a new side product do not need the same allowance.

Blog#

The public site. One per Project. It has an address (a blogged.dev subdomain until you connect your own domain), a theme, navigation, reader search and its own analytics.

What this means in practice#

Adding a product

Add a Project, not a workspace. A second workspace splits your team and your billing for no benefit.

Adding a teammate

Invite them to the workspace. Roles are held at workspace level and apply across the Projects in it.

Changing what you pay

Change the plan on the Project. See changing a plan.

Stopping work on one product

Archive that Project. The rest of the workspace is unaffected. See pausing and archiving.