Blog

Work that does not scatter

Tasks, access, the demo, and sprints. Applied notes with screenshots, not a brochure.

Ontra reports and growth dashboard
ReportsJuly 24, 20267 min read

Effort, repeat work, close speed, and delay from one record

When the report is a separate spreadsheet, you argue about numbers, not work. Ontra reports read the live task list so export becomes rare. Home health, the queue, late work, and team effort all derive from the same card. The meeting should end when the report opens.

Read post
Team members linked on the same work
SupportJuly 17, 20266 min read

Keep customer requests in a queue, not in a chat app

Support vanishes in Slack. In Ontra the request queue shares the workspace with tasks; assignment, status, and reply are tracked. A repeating ask becomes a feature. A closed ticket is archived, not deleted. A separate Zendesk is only needed when volume truly becomes a call center.

Read post
Work tools connected around the Ontra hub
OrganizationJuly 10, 20266 min read

Keep multiple companies in one panel; do not open a second workspace

In holdings and agencies, a tool per client means reports never merge. In Ontra companies stay scoped inside one panel. Members only see the company they are granted. Seats belong to the workspace; they do not multiply per company. Management totals are a separate view.

Read post
Work tools connected around the Ontra hub
IntegrationJuly 3, 20267 min read

A scoped API key is shown once, then hidden

A full-privilege key leak drops the whole workspace. Ontra keys are limited to task and project flows and copied once at creation. CI needs its own named, narrow key. A secret left as “test” will be running in production six months later.

Read post
Ontra project and task list
WorkflowJune 26, 20267 min read

If stock columns are not enough, write a custom task status

Not every team lives on “doing / done”. In Ontra statuses are per project; board columns and reports share the same vocabulary. Do not let “review” mean two things: internal review and client approval should be separate statuses, roles, and filters. A new column does not need a new tool.

Read post
Trigger, action, notify, and done flow
ProductivityJune 19, 20266 min read

Saved views and shortcuts shorten the morning

Rebuilding the same filter every morning is not work. In Ontra you save the view, pin a shortcut, and carry your own rhythm. A shared view is a team contract: “late items” means the same thing for everyone. Ten shortcuts are clutter again. Three are enough: today, late, waiting on approval.

Read post
Ontra project and task list
StructureJune 12, 20266 min read

Tag, folder, and list: three cuts, one task

Tagging everything kills tags. Folders hold ownership, lists hold flow, tags hold a cross-cut. Ontra keeps all three on the same card. You do not need a “copy over there” button. Nobody uses forty tags; reports earn their keep from three live cross-cuts.

Read post
Lock and corporate security shield
AgencyJune 5, 20266 min read

Do not leak client work inside an agency workspace

Rival brands can sit in the same studio. Ontra’s fine-grained access and company boundary keep an intern out of the wrong folder. A designer only sees the assigned brand. A manager report sees totals, not the file tree. A pitch shares with a password; a workspace invite is not required for every draft.

Read post