> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fluorine.app/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Set Up Your Fluorine Workspace from Scratch

> Structure your Fluorine workspace from scratch — create projects, invite your team, configure task lists, and set communication norms.

A well-structured workspace is the difference between a team that stays aligned and one that loses work in scattered tools. Fluorine organizes everything around four levels: **Workspace → Projects → Task Lists → Tasks**. Set this up intentionally at the start and you won't be reorganizing it later.

## Workspace structure

<CardGroup cols={2}>
  <Card title="Workspace" icon="building">
    Your company's top-level space. Everyone on your team belongs to one workspace. Most teams only ever need one.
  </Card>

  <Card title="Projects" icon="folder">
    Major goals or initiatives — a client engagement, a product launch, a campaign. Organize by outcome, not by department.
  </Card>

  <Card title="Task lists" icon="list">
    Execution layers within a project. Break work into phases, workstreams, or deliverable groups.
  </Card>

  <Card title="Tasks" icon="circle-check">
    Individual units of work with assignees, due dates, priorities, and subtasks. Where work actually gets done.
  </Card>
</CardGroup>

## Create your workspace

<Steps>
  <Step title="Name your workspace">
    When you sign in for the first time, Fluorine prompts you to create a workspace. Use your company or studio name — keep it short and unambiguous. **Acme Studio** works. **Acme Studio Workspace 2024** doesn't.
  </Step>

  <Step title="Invite your team">
    Go to **Settings → Members → Invite** and enter your teammates' email addresses. On Pro and Business plans you can assign roles before sending invitations — Viewer, Member, Admin, or custom roles on Business.

    <Tip>
      Invite your team before creating projects. That way teammates are ready to be assigned tasks the moment you set things up.
    </Tip>
  </Step>

  <Step title="Create your first project">
    Click **+ New Project** in the left sidebar. Name it around an outcome, not a team. **Q3 Product Launch** works. **Design Team** doesn't — it tells you nothing about what success looks like.

    Add a short description so teammates understand the project's purpose immediately.
  </Step>

  <Step title="Set up task lists">
    Inside your project, create task lists to represent phases or workstreams. For a product launch you might use:

    * **Discovery & Research**
    * **Design & Prototyping**
    * **Development**
    * **QA & Review**
    * **Launch**

    Keep lists specific enough to be meaningful but broad enough to hold multiple related tasks.
  </Step>

  <Step title="Add your first tasks">
    Inside each list, click **+ Add Task**. At minimum, fill in:

    * **Name** — action-oriented, specific. "Write landing page copy" not "Copy"
    * **Assignee** — one owner per task, no ambiguity
    * **Due date** — even a rough target keeps work moving
    * **Priority** — Urgent, High, Normal, or Low

    Subtasks, dependencies, tags, and custom fields can come later as your workflow matures.
  </Step>

  <Step title="Set communication norms">
    Before your team starts working, decide where different types of communication happen. Misaligned norms are the most common reason context gets dropped.

    Decide upfront:

    * **Task comments** — questions and updates about a specific piece of work
    * **Project channels** — broader discussions, status updates, and decisions
    * **Direct messages** — urgent or personal matters that don't belong on a task

    Pin these norms in your shared channel so every new team member finds them on day one.
  </Step>
</Steps>

## Roles and permissions

<Tabs>
  <Tab title="Starter">
    All members share the same access level. Anyone in the workspace can create, edit, and complete tasks across all projects.
  </Tab>

  <Tab title="Pro">
    Role-based permissions per member — **Viewer** (read-only), **Member** (create and edit tasks), and **Admin** (full workspace settings).
  </Tab>

  <Tab title="Business">
    Full advanced roles with granular permissions. Create custom roles like a **Client Reviewer** with read access to specific projects only. Admins manage workspace settings, billing, and integrations.
  </Tab>
</Tabs>

<Warning>
  Only Admins can invite or remove members, change roles, and modify workspace settings. Assign the Admin role carefully.
</Warning>

## Naming conventions

Consistent naming prevents confusion as your workspace grows.

* **Projects** — outcome-first: "Rebrand 2025", "API v2 Launch", "Client Onboarding Overhaul"
* **Task lists** — phase or workstream: "Kickoff", "In Development", "Pending Review"
* **Tasks** — start with a verb: "Design homepage wireframe", "Review contract draft", "Fix checkout bug"

<Note>
  Fluorine's AI reads task names to generate summaries and smart suggestions. Action-oriented names improve the quality of AI-generated updates.
</Note>

## What's next

<CardGroup cols={2}>
  <Card title="Create and manage tasks" icon="circle-plus" href="/guides/managing-tasks">
    Task details, subtasks, dependencies, and views.
  </Card>

  <Card title="Collaborate with your team" icon="users" href="/guides/team-collaboration">
    Team messaging, file sharing, notifications, and async communication norms.
  </Card>
</CardGroup>