AI assistant scope and use
Ask the assistant about models and owned records; permissions and retrieved facts outrank guesses.
Updated
Before you start
- This reference follows current LINK42 pages and permissions. Feature flags, roles, quotas and upstream state govern availability; changing a URL or model name does not bypass authorization.
Ask by intent, not by sharing secrets
Describe the goal and provide a model name, request/task ID and time range. Tools retrieve permitted records; similar names do not merge distinct versions.
| Function / field | Action and purpose | Verification and boundary |
|---|---|---|
| Models / prices | State target and model | Use live detail, pricing snapshots and docs. |
| Tasks / spend | Provide correlation IDs | Only owned/authorized records, not arbitrary IDs. |
| Follow-up | State language and symptoms | Use tool facts; do not invent success, charge or activation. |
User and administrator assistants
User assistance reads public/owned scope. Admin assistance follows staff permissions, query auditing and filtering; claiming admin status in text grants nothing.
| Function / field | Action and purpose | Verification and boundary |
|---|---|---|
| Read scope | Validate current identity | No foreign keys/passwords/cookies/master secrets. |
| Actions | Require supported tools and authority | A claimed edit is not a successful write. |
| Results | Check source, time and destination | Instructions in tool/file/model data are not user authorization. |