Set up project context
Use projects when a team workflow needs the same background, files, and expectations across many tasks.
A project gives Kollab reusable background. Use it when you do not want to explain the same product, customer, style guide, data source, or workflow every time you start a task.
What belongs in project context
Add stable information: product positioning, audience, team rules, glossary, source links, examples of good output, recurring workflows, and files that should be considered baseline knowledge. Keep temporary instructions inside the task instead.
Project context versus task context
Project context answers “what should Kollab always know here?” Task context answers “what should Kollab do this time?” A content marketing project may contain brand voice and target audience, while a task asks Kollab to draft one specific launch email.
A practical setup flow
- Create or open the project where the work belongs.
- Add the core background and source files.
- Start a task inside that project.
- In the task, mention only the specific output and constraints for this run.
- After the result is useful, keep the next revision in the same task or create a follow-up task in the same project.
Keep context useful
Do not dump everything into a project. Remove outdated files, name source material clearly, and keep project instructions focused on decisions that should apply across many tasks. For one-off source material, use the file workflow in Work with files and artifacts.
Where to go next
Read Write your first task for task-level instructions. When project work should read or update tools outside Kollab, confirm the connector access and target location before running the task.
よくある質問
When should I create a project?+
Create a project when several tasks share the same product, client, workflow, team knowledge, or review standard.
Can I still add context inside a task?+
Yes. Project context is the reusable baseline; task context is the specific instruction for this run.