Organizations and projects

Organizations

Separate teams/companies and centralize settings (members, permissions, integrations, and governance). Create another Organization when you need to isolate data and access for different clients or businesses.

Projects

They organize work by brand, unit, product, or client — and define B4ker's context. Good structures:

• 1 project per brand/client;
• by unit (e.g., "SP Store", "RJ Store");
• by goal (e.g., "Acquisition", "Retention") when audiences and assets change a lot.

Checklist to create a project

1. Name it clearly (brand + goal/channel).
2. Add the minimum context in Assets/Knowledge: positioning, offer, differentiators, proof, restrictions, and links.
3. Register personas/ICP and examples of "good" content.

Day-to-day management

• Switch projects when changing client/brand before creating conversations or campaigns.
• Update the context when product, price, branding, or goal changes.
• If a theme grows too big, create a new project to keep history and analysis clean.

Permissions

Use Organization members and roles to control who can view and edit projects, integrations, and billing. If someone can't find a project, it's almost always a permission issue or the wrong Organization.