Skip to main content

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.

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

Workspace

Your company’s top-level space. Everyone on your team belongs to one workspace. Most teams only ever need one.

Projects

Major goals or initiatives — a client engagement, a product launch, a campaign. Organize by outcome, not by department.

Task lists

Execution layers within a project. Break work into phases, workstreams, or deliverable groups.

Tasks

Individual units of work with assignees, due dates, priorities, and subtasks. Where work actually gets done.

​
Create your workspace

1

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.
2

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.
Invite your team before creating projects. That way teammates are ready to be assigned tasks the moment you set things up.
3

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.
4

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.
5

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.
6

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.

​
Roles and permissions

All members share the same access level. Anyone in the workspace can create, edit, and complete tasks across all projects.
Only Admins can invite or remove members, change roles, and modify workspace settings. Assign the Admin role carefully.

​
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”
Fluorine’s AI reads task names to generate summaries and smart suggestions. Action-oriented names improve the quality of AI-generated updates.

​
What’s next

Create and manage tasks

Task details, subtasks, dependencies, and views.

Collaborate with your team

Team messaging, file sharing, notifications, and async communication norms.