Personal settings

Settings are grouped by purpose below. Check their scope before changing them, and read the relevant guidance before changing passwords, resetting memory, or permanently deleting content.

General settings

Open the account menu and choose Settings → General.

Interface language

LinkSense supports Simplified Chinese and English. The interface changes immediately and the preference is saved for Web and Teams.

The help center has its own language menu. A help link opened from LinkSense uses the current interface language automatically.

Messages sent during execution

Choose the default for a message sent while a turn is running:

• Steer current execution adds a text-only clarification to the running turn.
• Queue as the next request starts after the current turn reaches a final state.

A request with an attachment or an explicit plugin, Skill, or knowledge-base selection is queued regardless of the default.

If saving fails, LinkSense restores the previous value and shows an error. Retry after connectivity returns.

Browser notifications

Browser notifications are off by default. When you turn on Enable browser notifications, the browser asks for permission if it has not already been granted. Notifications are enabled only after you allow the permission. LinkSense immediately sends a test notification after enabling; you can also select Send test notification at any time.

If notifications are not effectively enabled in the current browser, and the browser supports notifications without a permanently denied permission, LinkSense shows a notification prompt in the lower-left corner. Enable runs the same complete activation and test flow as Settings. Not now hides the prompt only for the current browser session, so it can appear again after you reopen the browser. When permission is blocked, LinkSense does not show an unusable prompt; allow notifications in the site's browser permissions first.

The setting applies only to the current signed-in user and the current browser. It does not sync to other browsers or devices. A LinkSense page must remain open. Notifications can appear while the page is in the background, but not after the page or browser is closed. LinkSense does not use Web Push or a Service Worker for background delivery.

When enabled, LinkSense sends a notification when a regular task or automation reaches a terminal state. The notification reflects the actual outcome:

• Succeeded: the task completed successfully; an automation must also have produced a result you can view.
• Failed: the task failed, or an automation ended without producing a result you can view.
• Interrupted: the task or automation was interrupted.

The first time you enable the setting, LinkSense starts from the current terminal position and does not send notifications for earlier work.

LinkSense sends the system notification even when you are already viewing the task. The notification title shows the task name. Its body identifies a regular task or automation and shows the actual Succeeded, Failed, or Interrupted status. The task name is visible to the browser and operating system, but the notification does not include input, answers, error details, attachments, or artifact names. Clicking the notification focuses LinkSense and opens the corresponding task directly.

If the browser does not support notifications, cannot save the setting, cannot reach the task-completion notification service, or permission has been denied, the settings page explains the issue. The switch is saved as enabled only after permission, the test notification, and the completion-listener baseline are all ready. If the browser resets an existing grant to Ask, select Grant permission and send test. After denying permission, allow notifications for the LinkSense site in your browser settings before turning the switch on again. If LinkSense reports that the test was sent but no system notification appears, check whether the operating system allows this browser to send notifications and whether Do Not Disturb or Focus is enabled.

Install on a desktop or home screen

LinkSense publishes web-app installation metadata. In a supported browser, use Install app, Add to Home Screen, or the equivalent browser menu command to open LinkSense in a standalone window. The command name depends on the browser and operating system.

Installation does not enable offline use; LinkSense still needs a connection to the deployment. Launching from the installed icon returns to the application entry point and uses the login session stored by that browser. Always sign out normally after using a shared device.

Profile and personal usage

Open Settings → Profile to manage visible account information and usage insights.

Display name

Edit and save the name shown in the sidebar, administrator user lists, and other safe identity displays. It does not change the login email.

Avatar

Upload a supported image from the avatar area. LinkSense validates its type and size. Replacing an avatar changes display only and never changes task ownership.

Personal usage

The profile can show total tokens, tasks, turns, model calls, active days, average tokens per turn, a 365-day activity heatmap, and current or longest streaks.

These values are insights, not usage settings, billing, or execution controls. Minimal activity and usage facts may remain after task deletion without restoring task content.

Update failures

Correct inputs that violate visible limits and retry. A disabled account loses its active session and cannot continue profile changes.

Quota and usage analytics

Open Settings → Quota to view your own quota and usage. Self-registered users and organization members use the same page.

Overview

View credits used, credits remaining, your weekly limit and the next reset time. Unlimited accounts still show actual consumption. Weekly quotas reset every Monday in the system time zone. After an administrator resets your quota, the overview counts usage since that reset; analytics retain historical charges.

Credits are rounded to the nearest integer for display. Actual charges keep their fractional precision. Usage below half a credit may display as 0 but still contributes to totals.

Analytics

Choose the last 7 or 30 days. Dates use your browser's time zone. The 30-day range is an analytics window, not a monthly quota.

• Credit history: daily charges by workload or model, based on recorded charges at the time of consumption.
• Task ranking: expand model and workload details or open a task. Other usage and deleted tasks are grouped separately.
• Plugin and MCP calls: finished calls in retained tasks, including failures. Activity counts are not charge counts.
• Skills: the same skill counts once per turn.
• Messages: user messages in task turns, grouped by model. Excludes AI replies, queued messages and history copied into forks.

Charts show up to five categories, grouping smaller categories as Other. Independently rounded category values may not add up exactly to the displayed total.

Personalization, instructions, and memory

Open Settings → Personalization for preferences that apply to future tasks.

Custom instructions

Use custom instructions for stable preferences:

• Answer in English by default.
• Run relevant unit tests after code changes.
• Put report conclusions before supporting evidence.

Saved instructions apply from future turns. Platform rules, safety boundaries, and administrator governance remain higher priority. Never store passwords or tokens here.

Automatic task naming

Choose when task names update. Changes are saved automatically:

• First message (default): name a task when you first send a message, then keep its name.
• Every message: update the name with each new message, using the latest request and recent context.

Manually edited task names stay unchanged. This preference applies to future messages in both new and existing tasks; changing it does not rename historical tasks in bulk. Naming runs independently of task execution and keeps the current name if generation fails.

Show reasoning

Show reasoning is on by default, and existing saved preferences are preserved. When enabled, it displays the full reasoning text provided by the model during tasks and in task history. Some models provide only summaries or no full text; no full reasoning body is shown in those cases. Changes are saved per user and affect only the display, not reasoning effort. Existing brief reasoning summaries and tool calls are unaffected by this switch.

During a task, hover over Thinking and click the arrow on the right to expand that stage's tool calls. Click again to collapse them. The arrow is absent when there are no tool calls. After completion, you can revisit the records in the activity history.

Memory

Memory is off by default, and you can enable it when needed. When enabled, LinkSense may derive personal memory from eligible tasks and use it in future work. Tasks involving external tools or web context do not create memory.

Disabling memory stops creating and using memory but does not automatically erase saved entries.

Reset

Resetting permanently deletes all personal memory and cannot be undone. It does not delete tasks, custom instructions, plugins, Skills, knowledge bases, or other settings.

Confirm that you want Reset, rather than simply turning memory off.

Appearance and text size

Open Settings → Appearance for display preferences.

Theme

• System follows the operating system or host WebView and responds to changes.
• Light always uses the light interface.
• Dark always uses the dark interface.

Theme changes do not affect task content, files, or execution.

UI font size

Adjust the base size within the page's allowed range. Navigation, forms, controls, settings, and task UI scale together while preserving hierarchy.

Document, Markdown, Office, or PDF preview content may have its own viewer zoom.

Across environments

The appearance preference is applied in Web and Teams for the current browser environment. System mode can resolve differently on different devices.

Use a document viewer's zoom if only preview content is crowded instead of reducing the entire LinkSense UI.

Security and password changes

Settings → Security changes a local login password. An SSO-only account may not need this operation.

Change the password

1. Enter the current password.
2. Enter a new password that passes the page rules.
3. Confirm the new password.
4. Submit.

After success, LinkSense revokes all sessions and requires sign-in again, including on other devices.

Password quality

Follow live validation. Avoid organization names, email addresses, common phrases, and passwords reused in another system.

Forgotten password

Return to the login page and request a one-time reset link. If authentication email is not configured or unavailable, ask an administrator to restore that capability.

Safety

• Administrators never need your password.
• Do not place it in a task, credential name, MCP description, or custom instruction.
• For suspicious sign-in behavior, change the password and give an administrator only the time and non-sensitive symptoms for audit review.

Archived tasks

Open Settings → Archived tasks.

Restore

Unarchiving returns a task to the recent list using its latest activity order. It does not rerun a historical turn.

Delete one task

Permanent deletion requires confirmation and cannot restore the task body, attachments, messages, or accessible deliverables.

Clear all archived tasks

This action affects only your archived tasks, not unarchived work. Download anything important first because the operation cannot be undone.

Retained facts

Minimal audit, security, resource cleanup, and usage facts may remain after hard deletion. They can include task or turn counts and token or cost snapshots, but not recoverable titles, message bodies, file content, or tool arguments.