Spaces and Teams
Spaces group work by function, such as Marketing or Design. Teams sit inside Spaces, nest inside other Teams, and are granted access to specific Brands, inherited by sub-teams unless overridden. Space roles run Space Admin, Contributor and Viewer; Team roles run Admin, Editor and Viewer. So a product line's Team sees its own Brand, and a shared design Team is granted several.
- Create a Space per function, and Teams inside it for each product line.
- Grant a Team access to the Brands it works on, and let sub-teams inherit it.
- Override an inherited grant where one Team should see less.
Several Brands in one Workspace
A Workspace holds one or more Brands, each with its own identity, voice, written guidelines and connected accounts. The Brand switcher in the top bar sets the active context across the whole app, so the calendar, the Media Library and the composer all follow the Brand you are working on. Nothing in the product is visible until at least one Brand exists.
- Add a Brand per product line, region or sub-brand.
- Switch Brand from the top bar and keep the same people and the same process.
Multi-stage approvals
An Approval Workflow is an ordered chain of review steps, each with a required role and a deadline in hours. Set one per Brand or a Workspace-wide default, and add auto-approve rules for named roles. Anything past its deadline escalates on its own. Comments carry mentions, change requests and the full history, and posts, media assets and Campaign Content Slots all pass through it.
- Build the chain your legal, design and leadership reviewers already follow.
- Set the hours each stage has, and let late stages escalate without a chaser.
- Work the queue in bulk when a launch produces many items at once.
The systems you already run
Jira syncs both ways, so tasks stay correct whichever side they are edited on, and epics link to Campaigns. Confluence syncs both ways, so a page edited there and a Campaign edited here stay in step. Notion pages and databases are created and updated the same way. Slack carries notifications, approvals and content updates into the channels a team already watches.
- Connect Jira and map its workflow onto Collabre task statuses.
- Point a Campaign at a Confluence space and let the two keep each other current.
- Send approvals into a Slack channel instead of an inbox.
Goals
Goals support three frameworks: OKR, SMART and 4DX. They nest, carry key results and tracked metrics, and update from Campaign performance. A metric comes from a connected analytics source, from Jira, or from a number a person enters, and a goal can link to a Jira epic, so the marketing plan and the delivery board describe the same work.
- Create the quarter's goals in the framework your leadership already uses.
- Point a key result at an analytics metric, a Jira issue, or a manual number.
