---
title: "Projects"
description: "A project is one piece of hiring work, such as filling a role. Tell its chat what you need: SourceGeek plans the work as tasks, runs them once you approve and reports back."
---

> Documentation Index
> Fetch the complete documentation index at: https://support.sourcegeek.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects

## How a project works

Every project has a **project chat**. Describe the work there in your own words, for example "find senior backend engineers in Berlin and build a shortlist". SourceGeek:

1. Plans the work as tasks, one per piece of work, and shows you the plan
2. Asks you to approve it
3. Starts every task after that one approval, each in a chat of its own
4. Reports back in the project chat when a task is ready for your review or fails

Quick questions are answered right in the project chat. Only real work, such as sourcing, a market map, a shortlist or outreach, becomes a task.

## Create a project

1. Click **Projects** in the left rail, then **+ New project**
2. Describe the work, or click a starter: **Plan the search**, **Source candidates**, **Market map** or **Outreach draft**
3. Choose who can see the project: **Personal** (only you) or **Shared** (everyone in the workspace)
4. Send. SourceGeek names the project from your message and starts planning

To start from a [project template](/project-templates), pick one under **+** → **Project templates** before you send.

Already working on something in a regular chat? Ask SourceGeek to turn it into a project. It creates the project with a brief, moves the chat into it and plans the tasks. Nothing runs until you start the plan.

## The brief

Each project has a **brief**: the role, must-haves, markets, salary band and hiring process. SourceGeek reads it in every chat of the project, so you don't have to repeat it. Edit it in the project's settings (ⓘ), or ask the project chat to update it.

## The plan and the approval

Nothing starts without your approval. After SourceGeek shows the plan, ask for changes in the chat ("drop the outreach", "add a pay benchmark") before you approve. One **Approve** starts the whole plan. See [Questions and approvals](/approvals).

Some tasks need another task's result first, for example a shortlist that builds on the sourcing. Those tasks show **Waiting** and start by themselves, with the earlier task's result, as soon as that task is ready for review.

A started task keeps working, over several runs if needed, until the "Done when" list in its description checks out.

## Tasks

Click **Tasks** at the top of the project to show its tasks, grouped by stage: **To Do**, **In Progress**, **In Review** and **Done**. Each task has a key such as SBE-3. Its status tells you where it is:

- **To do**: not started yet
- **Waiting**: approved, and starts once the tasks it waits on are ready for review
- **Working**: SourceGeek is working on it, with its progress, for example 3/6 steps
- **Needs input** or **Needs approval**: SourceGeek has a question or needs you to approve a step
- **Ready for review**: the result is ready for you to check
- **Failed**: SourceGeek couldn't finish
- **Done**: a person marked it done

Click a task to open its page and its chat: what SourceGeek did, what it produced and any questions it has. Answer or ask for changes right there.

- When the result is right, click **Complete**. Only people complete tasks
- If a task failed, click **Start over** to run it again in a new chat

### Add a task yourself

Click **New task** (or press C) in the task panel. On the task's page, add optional instructions and click **Start SourceGeek**.

### Task details

Click **Details** (ⓘ) on a task's page to see and change:

- **Title** and **Description**, with @mentions of teammates
- **Steps**: what SourceGeek is working through
- **Stage**, **Owner** and **Due date**
- **Repeats**: see [Repeating tasks](#repeating-tasks)
- **Credits**: what the task has used, in total and per run, and who started each run
- **Followers**: click **Follow** to get the task's updates in your inbox
- **Activity**: comments and changes. Write a comment and @mention someone to bring them in

At the bottom you can **Archive** or **Delete** the task. Only the task's creator, its owner or an admin can delete it; its chats stay in the project.

## Repeating tasks

A task can run again on a schedule: every few hours, daily or weekly, in a time zone you choose. Set it under **Repeats** in the task's details, or ask the project chat, for example "refresh the shortlist every Monday at 9:00".

Each run starts in a new chat with the previous run's result and reports back like any task. Setting the schedule is the approval, so runs don't ask again. A run is skipped while the previous one is still working or waiting on someone. To stop it, set **Repeats** to **Doesn't repeat**. Archiving the task stops it too.

## Knowing when something needs you

- The **Projects** icon in the left rail shows a count of tasks waiting on you: tasks you started or own that need input or approval, are ready for review or failed. Each project shows its own count
- The **Inbox** in the Projects panel lists mentions, comments and SourceGeek's updates on tasks you follow. Tasks you create, own, start, comment on or are mentioned on are followed automatically
- If you haven't seen it in the app within 10 minutes, SourceGeek emails you when you're mentioned, when a task you follow needs your input or approval, or when a task you started is ready for review or failed. Turn these emails off with **Task emails** in your [account settings](/profile#notifications)

## Credits

Messages in the project chat and every task run use your workspace's credits, like any chat. Each task's **Credits** section shows what it has used. See [Credits and usage](/workspace/usage).

## Project settings

Click ⓘ at the top of a project to:

- Rename it and edit its **brief**
- **Share with workspace**: only the project's creator can change who sees it
- Change the **Task prefix**, the letters in front of task keys (old keys keep working)
- See **Other chats** filed in the project, and unlink them
- Restore **Archived tasks**
- **Archive** the project, which makes it read-only, or **Delete** it

Deleting a project deletes its tasks; its chats stay in the workspace. Only the project's creator or an admin can delete it. Find archived projects in the Projects panel's filter under **Archived**.

Source: https://support.sourcegeek.com/projects/index.mdx