Marketing planning
Store function id: marketing-planning. Price and full description: Marketing planning in the store catalog.
What it is for
Section titled “What it is for”One worker that plans marketing from approved product facts: target groups, positioning, messages, channels, campaigns and a content calendar. It never posts or sends anything.
Who can do this
Section titled “Who can do this”- The administrator subscribes, answers the install questions and allows the permissions.
- Administrators and members give the workers tasks in Chat.
Before you start
Section titled “Before you start”- The box is enrolled with the store and the function is subscribed. See Store.
- In Owner policy, allow the permissions marked “Tick it” or with a value below. Permissions with an install question are allowed by your answer. See Owner policy.
Facts on this page come from the packages’ published definitions (checked on 8 October 2026). Your box shows the same facts before Install, under Permissions.
The worker
Section titled “The worker”Package id faivr.agent.marketing-planner, version 1.0.0.
Turns approved facts about your product into target groups, positioning, a ranking of messages, the choice of channels, campaigns and a content calendar. It hands each piece of channel work over as a campaign brief. It never posts or sends anything.
Permissions in plain words
| Permission | Install question | In Owner policy |
|---|---|---|
| Read files in its own workspace | None | Tick it |
| Create and change files in its own workspace | None | Tick it |
| Read one product’s knowledge | “Which product’s knowledge may it read for context?” (optional) | Allowed by your answer |
| Read the workboard | None | Tick it |
| Change the workboard | None | Tick it |
| Run in one model lane: Standard | None | Run in one model lane: choose standard and press Allow |
Install questions
- “Which product’s knowledge may it read for context?” Optional: Skip (the permission is declined) is offered. You choose a product of the box.
Hand-offs: during a task it may hand part of the work to these workers, if they are installed: Cora, Gideon. The other worker works with its own permissions only. In Owner policy, allow Hand work to one other installed package with the package id of each one, for example faivr.agent.pricing-models. See Hand-offs between workers.
Default autonomy levels
Shown and changed under Administration, Packages, panel Autonomy levels. It has no protected actions, so it never asks for an approval unless you raise a level to “Asks you first”.
| Kind of action | Default level | You can raise it to |
|---|---|---|
| Reads its own workspace | Runs on its own | cannot be raised (Fixed) |
| Writes files in its own workspace | Runs on its own | Tells you after, Waits for your check |
| Reads company knowledge | Runs on its own | cannot be raised (Fixed) |
| Reads the workboard | Runs on its own | cannot be raised (Fixed) |
| Changes the workboard | Tells you after | Waits for your check, Asks you first, Always asks, with a reason |
| Hands work to other packages | Runs on its own | Tells you after, Waits for your check, Asks you first, Always asks, with a reason |
What every worker can never do
Section titled “What every worker can never do”- Work outside its own closed workspace on the box.
- Reach hosts, repositories or products it was not given.
- Merge on GitHub, push to the default branch, or create tags or releases.
- Read a stored key or password.
Example tasks
Section titled “Example tasks”Write these in Chat after choosing the worker. Change the details to your company.
- “From the product knowledge, write the target groups and a ranking of our three key messages.”
- “Plan a campaign for the product launch in March with a content calendar for four weeks.”
- “Write a campaign brief for a LinkedIn series of three posts.”