Projects basics

What projects are A project is a container for related tasks — “Summer campaign”, “Tower B launch”, “Listing data cleanup”. Projects give tasks shared context, deadlines, and a board view for coordinated work. Open Work → Projects to browse existing projects or create new ones. When to create a project Use a project when: Multiple tasks share one outcome Multiple people collaborate across days or weeks Status at a glance matters to a lead Skip projects for one-off personal todos — a standalone task suffices. Creating a project Click New project . Typical fields: Name — specific (“Niavaran tower – phase 1 listings”) Description — goal, stakeholders, definition of done Start / target end dates — anchor planning Members or watchers — who sees the board (permission dependent) Board stages — columns on the board (backlog, doing, review, done) when customizable Save to open the project detail or board. Project board Each project exposes a board — columns represent stages; cards are tasks. Board steps Drag tasks between columns to update status Add task inline in a column during planning meetings Open card for comments, assignee changes, due dates The board is the project’s single source of truth for progress — prefer updating cards over side chat threads. Opening from tasks list Tasks list filters often include project picker — select a project to see only its tasks in list or board mode without visiting project home. Conversely, project page links back to filtered task lists for power users. Templates Teams on eligible plans may define work templates — prefilled task bundles for recurring playbooks (“New agent onboarding”, “Listing photography pipeline”). Apply a template when creating a project to spawn standard tasks automatically. Customize names before assigning. Templates live under Work → Templates for managers. Roles on projects Common patterns: Project lead — edits stages, reassigns work Contributor — moves own tasks, comments Viewer — read-only for stakeholders Exact permissions follow team roles — not every agent creates projects. Linking to listing work Projects are operational, not client records. Reference customers or listings in task titles/descriptions rather than expecting automatic linking unless your form includes entity pickers. Example task: “Post IG for Property #1042” with link pasted in description. Reporting Advanced plans add performance reports and targets under Work — managers compare completed tasks to goals. Day-to-day agents focus on board movement; leads review reports weekly. Lifecycle Archive or complete projects when initiative ends — stale boards clutter project list. Open tasks should be completed or moved before archive. Example: new development launch 1. Create project with target end = opening week 2. Template tasks: photography, price sheet, owner approvals, portal syndication (external) 3. Assign columns by function — marketing vs listings 4. Daily standup on board; blockers visible in Doing column Projects turn ad hoc chatter into tracked delivery — especially when listings depend on backstage prep finishing first.