Cleotic

Projects

Projects are the workspaces within a Cleotic organisation. Brands, segments, prompts, responses, analytics, sources, opportunities, and reports all belong to a project.

Creating a project

Cleotic supports three setup paths:

  1. Guided wizard: the recommended path for configuring the primary brand, first segment, models, prompts, and competitors yourself.
  2. Automated agent: an experimental shortcut that starts from a website URL and lets Cleotic propose the initial brands, competitors, segment, and prompts.
  3. Empty project: create the project shell first, then add brands, segments, prompts, and tracking later.

See Quick start for the full setup walkthrough.

Project status

Projects are either active or paused:

  • Active projects can run monitoring on schedule.
  • Paused projects keep their existing data, but scheduled monitoring stops.

Paused projects do not count towards active-project plan limits.

The project workflow

A project is organised around the work a customer does:

  • Performance. The project summary and next action
  • Opportunities. The prioritised action inbox
  • Content Studio. Answer gaps, briefs, and drafts
  • Answers. The primary-brand Mentions feed, prompts, and response evidence
  • Perception. Sentiment, brand language, and competitor positioning
  • Sources. Citation evidence, owned-domain tracking, crawlers, and AI referrals
  • Site Readiness. Website scans and page findings
  • Reports. Shareable project snapshots
  • Project Settings. Brand setup, segment management, Content Studio defaults, perception settings, access, tracking setup, and project configuration

Use analytics details for deeper metric comparisons. Citations and AI traffic live under Sources; sentiment and brand language live under Perception.

Project access

Organisation membership does not grant access to every project.

  • Owners and admins can access all projects.
  • The project owner/creator can manage access for that project.
  • Access can be shared with specific people or teams from the project's Project Settings page.

Project lists also show access context such as owner, shared access, or admin-only access.

Change ownership or move a project

Owners and admins can open Project Settings -> Project access and use Change beside the project owner to assign another organisation member.

To move a project between organisations, use Move project and choose the destination. You must be an owner or admin in both organisations. Review the move before confirming: the project ID and history move with it, existing project shares are removed, and you become its owner in the destination.

After a successful move, review access in the destination and share the project again as needed. If the move succeeds but the destination does not open, use Open in destination or the organisation switcher. Do not repeat the move.

Managing projects

From the projects page and Project Settings, you can:

  • Search projects
  • Switch between list layouts
  • Rename a project
  • Pause or resume a project
  • Delete a project
  • Manage project-level access
  • Manage brand setup and segments

Plan limits

Active-project capacity is shared across the organisation. See Plans and usage for limits and trial behaviour.