Teamhood

The Data Protection Officer

Boards built on people fields give real assignments, and the scheduling page documents genuine dependencies, parent-child nesting and a shared view definition every teammate sees — a real shared workspace, not a personal list. We found no public information on comments, guest or client access, workload or capacity views, or cross-project planning, which keeps it below the solid-shared-projects mark. 1 2

Report an error

The Bootstrapper

The captured docs show genuine shared work: drag-and-drop boards with swimlanes, grouping and people fields, and a Gantt where the arrows are real dependencies backed by a dependency-scheduling page, with shared view settings everyone sees. That clears a personal task list by a mile. We found no public information on comments, guest or client access, workload or cross-project views, so I cannot credit first-class team-level planning beyond one solid shared timeline. 1 2

Report an error

The Enterprise Architect

Boards with people-field columns and swimlanes, a Gantt with real schedulable dependencies and parent roll-ups, and an explicitly shared view definition give a team a genuine shared planning surface. We found no public information on cross-project views, workload or capacity planning, comments, or guest and client access — exactly the gaps two hundred seats hit first. 1 2

Report an error

The UX Purist

The Gantt docs treat dependencies as first-class — an arrow is "a real dependency between the two items, not a drawing" — with parent rollups, shared view definitions, and a Timesheet and Schedule view named alongside. But the captured pages stop at per-board depth: we found no public information on cross-project views, workload or capacity planning, guest or client access, or comments. 1 2

Report an error

The Integrator

The Gantt documentation shows real dependencies and a shared view definition — date fields, filters, columns and grouping are changes everyone in the view sees — with people fields on the board, so shared planning is genuine. I found no public information on comments, guest or client access, cross-project views, or workload and capacity planning, which is what the next level up would need. 1 2

Report an error

The Skeptic

Real multi-person machinery is on the page: people fields as board columns, cards whose only person drops to No value when that user is deleted, dependencies that are "a real dependency between the two items, not a drawing", and shared view definitions where a change is "a change everyone sees". That clears shared projects with assignments, a shared timeline and dependencies; above that, we found no public information on comments, guest or client access, workload or capacity views, or any cross-project surface. 1 2

Report an error

The Data Protection Officer

The documented view list names Timesheet and Chart, so time and some visualization exist beyond staring at the board. We found no public information on filters, cross-project aggregation, budgets, utilization or any export path, so the answer to any real question stays inside one project view. 2

Report an error

The Bootstrapper

Timesheet and Chart views are documented by name, which suggests time and charting surfaces, but the captures show nothing about what they calculate, filters, budgets, utilization, or cross-project aggregation. We found no public information on any export path, so a buyer cannot see how to get an answer out of the tool. 2

Report an error

The Enterprise Architect

The documented view list includes Timesheet and Chart, which is more than staring at the board, but those are names only. We found no public information on filters, cross-project aggregation, budgets, utilization, or any export path, so I cannot verify the tool answers questions about the work at depth. 2

Report an error

The UX Purist

The help pages name a Chart view and a Timesheet view and say nothing further about either — no dashboards, no aggregation, no customization surface. We found no public information on exports, filters, budgets or utilization, so this sits at fixed named views. 2

Report an error

The Integrator

Timesheet and Chart views appear in the documented view list, but they read as fixed views: I found no public information on cross-project aggregation, budgets, utilization, or any export path — nothing on CSV and nothing on reporting via the API. Reporting that cannot get its answers out of the product stays at the basic level for me. 2

Report an error

The Skeptic

The Gantt page names a Timesheet view and a Chart view among the documented views, which is more than looking at a board — but only names. We found no public information on what those views compute, on filters, budgets, utilization, or on any export path. The evidence shows reporting surfaces exist; it shows nothing about whether they can answer a question or leave the building. 2

Report an error

The Data Protection Officer

The personal-token page shows a documented API with per-user permission scoping, last-used and expiry tracking, and clean individual revocation — exactly the governance I want around programmatic access — and webhooks have their own help page. We found no public information on native integrations such as calendar, chat or file storage, on automation platforms, or on import paths from competing tools. 3 4

Report an error

The Bootstrapper

There is a documented API reached through personal tokens — scoped to the creator's own permissions, individually revocable, with last-used and expiry tracking — plus a webhooks page in the help center, and that token design is saner than most. But we found no public information on native integrations such as calendar, chat or file storage, on automation platforms, or on import paths from other tools, which keeps this below the common set. 3 4

Report an error

The Enterprise Architect

Personal tokens give scripts a documented, permission-scoped, individually revocable route into the API with last-used and expiry tracking, and webhooks have a page in the integration documentation — respectable plumbing with real token governance. We found no public information on native integrations with calendar, chat or file storage, on automation platforms, or on import paths from competing tools, so I will not assume the common set exists. 3 4

Report an error

The UX Purist

There is a real, documented API surface: personal tokens with per-user permissions, individual revocation, expiry and last-used tracking, and a webhooks page in the help center — token hygiene documented down to "treat it like a password". What we found no public information on is the native side: calendar, chat, file storage, automation platforms and import paths. 3 4

Report an error

The Integrator

This is where the engineering care shows: a documented API reachable through personal tokens with real hygiene — value shown once, per-token revocation, last-used and expiry dates, permissions scoped to the creator and to a single organization — plus a dedicated Webhooks page under Integrations. But the captured pages stop there: I found no public information on native integrations such as calendar, Slack or Teams, file storage, automation platforms, or import and export paths, so the catalogue side is entirely unevidenced. 4 3

Report an error

The Skeptic

Two connective tissues are documented plainly: webhooks, and personal tokens that "can do exactly what you can do, in the organization where you created the token, and nothing more", with per-token revocation, last-used and expiry dates, and even the failure mode disclosed — tokens stop answering if the subscription lapses. Everything else a buyer needs here is dark: we found no public information on calendar, chat or file-storage integrations, automation-platform coverage, import paths from competitors, or how much of the product the API reaches beyond authentication. 3 4

Report an error

The Data Protection Officer

The one bright spot is that the help pages are current and walk a newcomer through board basics in plain language. We found no public information on self-serve signup, trial terms, payment details, guided setup or templates, so the signup-to-first-project journey cannot be judged from the captured pages and I score low accordingly. 1

Report an error

The Bootstrapper

We found no public information on a self-serve signup, a trial, payment-card requirements, templates, or importers — nothing that shows how a three-person team gets from signup to a first project. The only onboarding-relevant material is the help documentation itself, which is current and detailed enough that a determined self-server could DIY, but that is not a path I can verify. 1

Report an error

The Enterprise Architect

The help documentation is current and task-shaped — press C to add a card, drag between columns, fold a column — which reads like a tool a team can start using without an implementation project. But we found no public information on the signup path, trial terms, payment details, templates or importers, so the true signup-to-value friction cannot be verified from the captured pages. 1 2

Report an error

The UX Purist

Everything runs through a field model — a board "groups items by one field, the Column field in the Layout panel" — so a first project asks schema judgments (which field is the column, which is the swimlane) before the board means anything. The docs are precise and current and teach shortcuts like C, but we found no public information on signup flow, trial terms, templates or importers, so time-to-first-value cannot be verified beyond the written help. 1 2

Report an error

The Integrator

The captured pages are mechanics how-tos for boards and Gantt; I found no public information on the signup flow, trial terms or payment details, templates, or guided setup. Current, precise docs help a self-serve start, but nothing here evidences how quickly a team reaches a working first project. 1 2

Report an error

The Skeptic

We found no public information on signup, trial terms or payment details, guided setup, templates, or importers — nothing on the path from signup to first value was captured. The help center exists and carries a Sep 28, 2026 update stamp, which serves a team that already signed up, not one deciding whether it can start. 1

Report an error

The Data Protection Officer

I read the data processing agreement before the feature list, and here I found no public information on data residency, a processing agreement, subprocessors, or where the vendor legally sits — nothing answers where the data lives. An unverifiable posture sits in the bottom band; I hold a single point of grace only because the captured pages are silent on hosting and applicable law rather than showing US infrastructure under US law. 1 2 3 4

Report an error

The Bootstrapper

No sovereignty attributes are on record, and none of the captured pages address the vendor's legal location, data residency, a data processing agreement, or subprocessors. From this public material, nothing about where the company or the data sits can be verified either way. 1 2 4

Report an error

The Enterprise Architect

No sovereignty attributes are on record: we found no public information on the legal entity, ownership, data residency, hosting jurisdiction, DPA, subprocessors or certifications in any captured material. That is an unverified state rather than a confirmed bad one, but for a two-hundred-seat procurement an unverified state is still unbuyable as it stands. 1 2 4

Report an error

The UX Purist

We found no public information on the vendor's legal entity, ownership, data residency, DPA or subprocessors — the captured help pages say nothing about jurisdiction at all. Nothing here is verifiable rather than asserted, which puts this near the floor of the scale. 1

Report an error

The Integrator

No company domicile, data residency, DPA or subprocessor information appears in any of the captured pages, so none of it can be verified by a buyer. I treat complete silence on where the company and the data actually sit as scoring near the bottom of this criterion. 1 2 3 4

Report an error

The Skeptic

No sovereignty attributes are on record: we found no public information on where Eylean Board is incorporated, who controls it, where customer data is hosted, on a DPA, or on any subprocessor. Sovereignty a buyer cannot verify is sovereignty a buyer cannot rely on. 1

Report an error

The Data Protection Officer

The help center is genuinely current — the board page carries a late-September 2026 update date — and its plain-language coverage of views and API tokens is above thin. We found no public information on support channels, their availability per plan, response times or a changelog, which caps this below a help center paired with reachable support on all plans. 1 2 4

Report an error

The Bootstrapper

The help center is real and current — the board page is marked last updated Sep 28, 2026 — and the docs explain precise behavior like drag cancellation, deleted-user handling and token permissions instead of marketing fluff. We found no public information on support channels, response times, plan-gated support, or a changelog, so the human help side is unproven. 1 2 4

Report an error

The Enterprise Architect

The help center goes deep on core product — deleted-user edge cases on boards, drag cancellation, parent-bar fallback dates on the Gantt — and carries a September 2026 update stamp, which is genuinely current. We found no public information on support channels, response times per plan, a changelog or any SLA, and that silence is the part a large deployment cannot accept on faith. 1 2 4

Report an error

The UX Purist

The help center is genuinely good: the board page was last updated Sep 28, 2026, and the pages teach edge cases — Esc cancels a drag, deleted users drop to "No value", tokens stop answering when a subscription lapses — instead of marketing prose. But we found no public information on support channels, response times, plan gating, community or a changelog. 1 2 4

Report an error

The Integrator

The help center is real, current and precise — the board page is marked last updated Sep 28, 2026, with detail down to keyboard shortcuts, Esc cancelling a drag and Ctrl-Z undo, and the token guide is genuinely practical. I found no public information on support channels, response times, plan-based gating or a changelog, so only the documentation half of this criterion is evidenced. 1 2 4

Report an error

The Skeptic

The help surface is demonstrably alive: the board page carries a "Last updated: Sep 28, 2026" stamp days before capture, and the Gantt and token pages explain mechanics with unusual precision — Esc cancels a drag, Ctrl-Z puts the values back, the token value is shown only at creation. We found no public information on support channels, response times, plan gating for help, SLAs, or a changelog, so whether a stuck user gets unstuck rests entirely on documentation. 1 2 4

Report an error

The Data Protection Officer

No price, tier or billing figure appears anywhere in what was captured. The only pricing-adjacent fact is that subscriptions exist, because a lapsed one stops personal tokens from answering — a buyer can determine no payable number before talking to the vendor. 4

Report an error

The Bootstrapper

I pay with my own card and the captured public material shows not a single number: we found no public information on tier prices, a free tier, seat minimums, billing periods or tax treatment. Working from this evidence, a buyer cannot determine what three seats or thirty cost before talking to the vendor. 1 2 4

Report an error

The Enterprise Architect

We found no public information on pricing at all — no tiers, seat costs, billing periods or tax treatment appear in the captured material. The only pricing-adjacent fact is that personal tokens stop answering when a subscription lapses, which confirms subscriptions exist but tells a buyer nothing about what one costs; no payable number can be determined before talking to the vendor. 4

Report an error

The UX Purist

We found no public pricing of any kind — no tiers, seat prices, billing periods or tax treatment appear in the captured pages, and the only pricing-adjacent fact anywhere is that personal tokens stop working when a subscription lapses. A buyer cannot determine cost from this evidence. 4

Report an error

The Integrator

I found no public information on pricing in the captured pages — nothing on tiers, seat prices, billing periods or tax treatment. The only pricing-adjacent fact is that personal tokens stop working when an organization's subscription lapses, which tells a buyer a bill exists but not what it costs. 4

Report an error

The Skeptic

The only pricing-adjacent fact in the captured material is that an organization runs on a subscription which can lapse. We found no public information on tiers, seat prices, billing periods, tax treatment or trial terms, so the real payable cost cannot be determined from anything published. 4

Report an error