Copilot Settings

Configure a copilot's name, logo, aliases, visibility, owner, GPT disclaimer, components, styles, and scripts on the Settings tab.

The Settings tab is where you configure a copilot's key information — its name, logo, and aliases (alternative names it may be known by) — and control its visibility and availability. This tab is also where you set a copilot-specific GPT disclaimer, configure components, upload a custom CSS style, and add custom scripts.

The Settings tab of a published copilot, showing its logo, name, status, visibility, owner, escalate task, and components.

A copilot's Settings tab

Copilot Details

By default the Settings tab is read-only. The summary lists the copilot's status, visibility, owner, and escalate task, and the Components panel lists its components.

  • Owner shows the user who owns the copilot, or Unowned. Click Change owner to change it.
  • To delete the copilot, click the red trash icon next to Edit.

To change the copilot's details, click Edit in the top-right corner. The Copilot Details section becomes a form with every field open for editing. Click Save to commit your changes or Cancel to discard them.

The Settings tab in edit mode, with the Copilot Details form open for the copilot logo, name, visibility, status, aliases, GPT disclaimer, and escalate task.

The Settings tab in edit mode

Copilot logo

Upload the image that serves as the copilot's display icon across both the portal and the app. A square image with a transparent background works best.

The Copilot Logo upload area in Copilot Details.

The Copilot Logo upload area

Name

Enter the designated name used to identify your copilot within both the portal and the app.

The Name field in Copilot Details.

The Name field

Visibility and status

The Status setting marks your copilot as Published or Unpublished. When set to Unpublished, the copilot does not appear in the app and does not influence InSkill GPT responses.

The Visible toggle controls whether the copilot is visible to users within the app. When it is off, the copilot is hidden from the app interface but remains active and influences InSkill GPT responses.

The Visible toggle and the Status list in Copilot Details.

The Visible toggle and the Status list

📘

Note

An unpublished copilot is not shown to users in the InSkill app unless a user has it specifically turned on in their user profile, usually for testing.

Aliases

Add alternative names for the copilot. Aliases help match a copilot's name during imports: if you import assets from another system that refers to a machine as 3d or Atlantis, entering those as aliases allows InSkill to match the right copilot. Type an alias and click Add.

The Aliases field and Add button in Copilot Details.

The Aliases field

GPT disclaimer/notice

Enter text to add to the disclaimer shown with InSkill GPT for this copilot. It is appended to the account-wide disclaimer set in Account Settings, so use it for notices that apply only to this copilot.

The GPT Disclaimer/Notice field, appended to the account disclaimer.

The GPT Disclaimer/Notice field

Escalate task

Select the task used to escalate issues internally. For how escalation works in the field, see Escalate.

The Escalate Task selector in Copilot Details.

The Escalate Task selector

Components

Add components to give your copilot access to other copilots. When you ask your copilot a question, it draws answers from its own resources as well as all of the resources of its component copilots. This is a way to nest knowledge and amplify the power of certain copilots.

This functionality is ideal for equipment that has multiple machines connected to one, equipment with add-ons, or general information shared across a line of asset-based copilots. See Components.

In edit mode, use Search to find a copilot to add. Each component can also carry a dependency: click + Add Dependency to choose a variable and value, and add conditions or groups for more complex rules — see Dependencies. Click Remove to remove a component.

The Components section in edit mode, with a component row showing the + Add Dependency field and the Remove button.

The Components section in edit mode

Copilot Styles

Import CSS files with custom styling for your copilots. Adding CSS styles customizes the way dynamic resources are presented to the user.

The Copilot Styles section, where a Copilot CSS file can be dropped, pasted, or browsed for.

The Copilot Styles section

Scripts

Input custom scripts for your copilot to perform custom functionality. Scripts are the way to add custom logic to the workflow of tasks. Choose when the script runs with Context Augmentation or Session Finished, and turn on Active to run it automatically. For developing, testing, and the scripting language and methods, see Scripts.

The Scripts section, with the Select Task from History, Test Script, Save Script, and Documentation controls, the Context Augmentation and Session Finished tabs, and the Active toggle.

The Scripts section