User guide
User guide overview
Learn the main LinkSense entry points and a recommended workflow.
LinkSense is organized around tasks. A task keeps your conversation, files, and deliverables together while allowing you to select plugins, Skills, and knowledge bases.
Main areas
| Area | Purpose |
|---|---|
| New task | Submit a request and choose a model, Plan or Goal mode, and capabilities |
| Automations | Repeat work hourly, daily, weekly, or monthly in one fixed task |
| Plugin Center | Discover, install, update, and manage plugins, Skills, MCP, and applications |
| Resource library | Manage knowledge bases, browse task artifacts, and publish or maintain public sites |
| Settings | Manage language, profile, personalization, message channels, security, credentials, and MCP |
| Feedback and help | Submit feedback and open help for the current page |
The Resource library entry uses an icon showing several upright books. Knowledge bases manages searchable documents and sharing, Task artifacts brings together files generated by your tasks, and My sites manages public pages published from HTML deliverables.
Recommended first steps
- Sign in and confirm the interface language.
- Create a first task and review its execution status and result.
- Add files, plugins, Skills, or knowledge bases as needed, or ask LinkSense to generate an image.
- Use activity and the task overview to review progress, artifacts, and external sources.
- Continue refining the result. For long histories, review context-window usage and compact context when needed.
- Use Plan mode for complex work, or branch from a historical response to try a different direction.
- Create an automation for repeating work, or turn a stable workflow into a shared application.
Your data boundary
- You can only read your own tasks, messages, attachments, and deliverables.
- A shared knowledge base can be read and searched, but only its owner manages documents and sharing.
- Personal plugins, Skills, credentials, and MCP servers are only used for your tasks.
- Administrators govern accounts and platform capabilities, but the audit UI does not expose another user's task body or file contents.