Settings & configuration
Administrators tune how Copilot behaves for their teams from a single settings screen. This section explains every control an administrator manages.
For administratorsThe underlying engine and capacity are managed for you as part of iVendNext. The controls below shape behaviour, access, and safety. They do not require any technical setup.
Identity & appearance
| Setting | What it controls |
|---|---|
| Assistant name | The name shown for Copilot across the chat panel and in its emails. Defaults to "iVendNext Copilot." |
| Accent colour | The primary colour of the chat interface and report emails, so Copilot matches your brand. |
| Assistant persona | An optional instruction set that shapes how Copilot introduces itself and frames answers, so it sounds like part of your team. |
Usage limits
| Setting | Default | What it controls |
|---|---|---|
| Requests per minute | 10 | How many questions a single user can send per minute. |
| Requests per day | 200 | How many questions a single user can send per day. |
| Actions per turn | 15 | How many steps Copilot may take to answer one question. |
| Multi-step helpers | On | Whether Copilot may hand complex tasks to a focused helper. |
| Helper depth | 2 | How many levels of helper hand-off are allowed. |
Safety & access
| Setting | Default | What it controls |
|---|---|---|
| Manipulation defence | On | Screens messages for attempts to make Copilot ignore its rules, and logs them. |
| Field-level access control | On | Enforces per-record-type rules on which fields Copilot may read and write. |
| Redact personal data in logs | On | Keeps personal information out of the audit trail. |
| Log full conversations | Off | Whether full conversation text is retained, for stricter audit needs. |
| Readable record types | All by role | An optional allowlist of record types Copilot may read. Empty means "whatever the user's role already allows." |
| Writable record types | Explicit list | An allowlist of record types Copilot may create or change. |
| Blocked record types | Sensitive types | Record types Copilot may never touch, on top of the built-in block list. |
| Blocked words | None | An optional list of terms Copilot will refuse to produce. |
Field whitelisting in detail
For any record type, an administrator can define precise field rules. This is how you let Copilot help with, say, customers, without ever exposing a field you would rather it not read or change.
| Control | Default | Effect |
|---|---|---|
| Readable fields | All | The fields Copilot may read. Empty means all readable fields. |
| Writable fields | None | The fields Copilot may write. Empty means none, so writing is denied by default. |
| Blocked fields | (none set) | Fields are always denied, regardless of the lists above. |
| Maximum list size | 100 | The most recorded Copilot may return at once for this type. |
| Allow create / submit / cancel | Off | Whether Copilot may create, finalise, or cancel records of this type. |
**
Last updated 8 hours ago
Was this helpful?