Tasks across the suite and the knowledge graph
VNCtask is one product in a suite that shares a common knowledge layer. Two things follow from that for you: tasks are findable beyond the tasks app, and they show up in your Timeline.
Findable across the suite
Section titled “Findable across the suite”A published task is added to the suite’s shared search, so a search for its subject can surface it from elsewhere in VNClagoon — not only when you are inside VNCtask. The suite’s assistant can use the same shared knowledge to answer a question with task information, the way it can with other content you can access.
Everything respects access: content is indexed under your identity, so the suite only ever returns tasks you are allowed to see. A task that is private to you does not become visible to others by being indexed.
The knowledge graph
Section titled “The knowledge graph”Behind the shared search is the platform’s knowledge graph: when a task is written, VNCtask contributes it — its subject, its actors and the records around it — as graph entries. That lets a question be answered over task evidence across the estate, and lets related work be connected.
A few properties are deliberate:
- Best effort, never blocking. Contributing to the graph happens quietly. If it is ever unavailable, your task write is unaffected — you never wait on it.
- Access-scoped. The graph is read under your identity, so it answers with what you can access.
- Bounded. Only a short, capped snippet of a task ever travels, never the whole record unbounded.
Your Timeline
Section titled “Your Timeline”The shared person Timeline is one person’s activity lens across the suite. When you complete work in VNCtask, it appears there alongside your other suite activity. Each Timeline row opens its source object in the product that owns it — so a task line opens the task in VNCtask.
The Timeline is useful when you (or a colleague who is allowed to) want a chronological view of what a person has been doing, without hopping between apps.