comunica.in
PT

Operation

Tasks

The Tasks area organizes the communication team's work into pipes (kanban boards): each pipe has steps, tasks with responsible parties, deadlines, checklist, comments with mentions, links with announcements/campaigns — and a audience request form that automatically transforms responses into tasks.

Concepts and terms

Term (as it appears on screen)What does it mean
PipeA process/workboard, with its own name, color, icon and visibility. `/tarefas` shows the pipe grid.
StepKanban column, with name, color and category (Not started / In progress / Completed). A new pipe is born with To Do / In Progress / Done.
TaskThe card (`#123`): title, description, Responsible, Dates (Start → Deadline), Priority (Urgent/High/Medium/Low), Tags, checklist, attachments, activity.
Form (tab)The audience pipe form (one per pipe): questions, appearance, and the `/f/<slug>` link. Each answer creates a task in the chosen initial phase.
LinksTask links with Announcements and Campaigns (they also appear in reverse, on the announcement/campaign screen).
VisibilityBy pipe: Global (everyone with access to Tasks) or Restricted (teams/users; no selection, only the owner).
ActivityTask feed mixing events (step change, assignment…) and comments.
ArchivePipes and tasks are archived (recoverable), never permanently deleted by the interface.

What can you do

  • Create pipes (name, description, color, emoji and visibility), edit, archive/reactivate
  • Manage steps: add, rename, color, categorize, reorder and delete (migrating tasks to another step)
  • Create tasks and move them by drag and drop (or by the Status field in the detail), with optimistic updating
  • In detail: edit inline title, responsible parties, dates, priority, tags, rich description, checklist with progress, attachments (5 MB per file), comments with attachment, link and mentions (@ for announcements, @@ campaigns, @@@ employees, @@@@ users)
  • Link tasks to announcements/campaigns — and see "Linked Tasks" on their screen
  • Search by title and filter the table by priority, deadline (late, due today, this week, no deadline, interval), tags, responsible and archived
  • Create the audience form: 6 question types (Short/long text, Single/multiple selection, Date, Date and time), mandatory, custom slug, appearance (logo, background, primary color, success message), attachments, publication and link
  • Monitor Responses: visits, responses, conversion rate, table with search and Export CSV
  • Configure personal notifications (Email / Inbox) and labels via pipe

Step by step

Create a pipe and assemble the board

  1. 1.In the side menu, click on Tasks → card Create pipe. Give name, color, icon and define Visibility (Global or Restricted by teams/users).
  2. 2.The painting is born with To Do / In Progress / Done. Use Add step and the menu (⋯) for each column to rename, change color/category, move and delete.
  3. 3.When deleting a step with tasks, choose the destination step ("Delete and move"); If the published form pointed to it, also choose the form's new destination.

Work with tasks

  1. 1.+ Add task in the column: title (required), responsible, dates, priority, tags and description.
  2. 2.Drag the cards between steps (also works via keyboard). Click on the card to open the detail.
  3. 3.In the detail, use the right column to comment — type `@` to mention announcements (repeat @ to switch between Campaigns, Employees and Users). Only the author edits/deletes the comment itself.
  4. 4.Links connects the task to communications/campaigns; the reverse path exists in the announcement details ("Linked Tasks").
  5. 5.Finished? Archive (the "Show archived" filter displays the Archived column, with unarchive).

Publish a request form

  1. 1.In the pipe, Form tab: give the title, adjust the slug (`/f/…` — the screen warns you if it is already in use) and assemble the questions (6 types, with "Mandatory" per question).
  2. 2.In Appearance, define the Initial Phase ("Submissions create a task in this phase" — mandatory to publish), who to notify with each submission, whether allows attachments (up to 10 MB in total) and the visual identity (logo, background, primary color, success message).
  3. 3.Save and Publish — copy the audience Link and distribute. Unpublish takes the form offline (the link now shows "This form is unavailable").
  4. 4.Whoever responds (without login) fills in Your details (Name, Email and Department — mandatory) + the questions; each submission becomes a task in the initial phase, with the respondent's data, answers and attachments on the card (title = name of the requester).
  5. 5.Follow the Responses sub-tab: Visits, Responses, Conversion rate; table with detail by sending and Export CSV.

Pipe settings

  • Settings tab: name/color/icon, Visibility (only the owner of the pipe changes; restrict warns if someone will lose access — tasks unassigned and notifications removed), My notifications in this pipe (Email / Inbox), Tags (create/edit/delete with color) and Archive.

Limits and rules

RuleValue
AvailabilityIt has Demands Portal + task role in the profile (the "Inbox" role is separate)
Pipe visibilityOnly the owner changes it; anyone who doesn't see the pipe won't find it anywhere (names of third parties appear as "Restricted")
Assign responsible / mention usersRequires settings permission; with team, only people from the same team
StepsMinimum 1 per pipe; delete requires destination for the tasks (and for the published form, if it pointed to it)
Task Attachments5 MB per file; PDF, Office, text/CSV and images; attachments coming from forms cannot be deleted
FormOne per pipe; publishing requires Initial phase; sending attachments: total 10 MB, up to 20 files
audience formNo login; anti-robot protection (reCAPTCHA) and limit of submissions per minute
Frame SearchBy task title (up to 255 characters)
ExclusionsPipes and tasks are archived (retrievable); tags and comments follow their own rules (comment: only the author)

What tends to confuse

  • Really delete does not exist: pipes and tasks are archived and can be restored ("Show archived").
  • Visibility belongs to the owner: if you can't change who sees the pipe, it's because you didn't create it.
  • Invisible pipe "does not exist": anyone who is out of visibility cannot see the pipe even through the link — there is no "no permission" screen.
  • The board search only searches the title — not the description or comments.
  • The form is one per pipe — for another form, create another pipe.
  • Form answers save a photo of the questions from the time — editing the form later does not change old answers.
  • Notifications: task events arrive in Inbox and/or by email, configurable by pipe; whoever does the action does not self-notify.

Related Features

Documentation · Comunica.In