Connectors for a Coworker

Connectors are built by Coworkers, together with a Supervisor, to reach your organization's own systems. See Connecting a Coworker to one of your systems. Every Coworker can find every connector, but a Coworker can use one only after it is enabled for that Coworker. The Coworker that built a connector has it enabled from the start.

Connected systems such as GitHub#

Your administrator can also connect outside systems such as GitHub for your organization. They appear in the same Connectors section, as cards with a Connected system label, ahead of the connectors built for your organization. Each card shows how many functions are on.

Nothing is on by default. A Coworker can use a connected system, and read its access token, only after you select Enable on its card. Select Turn off and confirm to take it away again. A Coworker the system is not enabled for is told it is not enabled and that its Supervisor can enable it. It uses each person's own account on the system, as set up in Connecting your accounts.

How a Coworker uses a connected system is set by your administrator. For a system such as Microsoft, Linear, Slack, Google or Atlassian it can be limited to the system's functions, so every use follows the person's Allow, Ask or Block and scripts cannot read anyone's sign-in.

Only the Coworker's Supervisor sees these controls. Administrators who do not supervise the Coworker manage the connection itself, and the Coworkers it is enabled for, in Settings.

What happens when a Coworker uses a connector#

Every function of a connected system, and every connector built for your organization, is either a Read (it only looks things up) or a Write (it can create, change, delete or send something in another system). Reads run without any prompt. For a write, your administrator sets where it starts, and each person can only make it stricter for themselves:

Setting	What happens
Allow	The Coworker does it without asking.
Review	The Coworker does it without asking unless an automatic check finds it risky, for example a message to someone outside the company or personal or confidential information going out. A risky one waits for the person's approval, and the request shows the reason. Ordinary writes go straight through.
Ask	The person is asked before each use.
Block	The Coworker cannot use it.

Review works only when an administrator has turned on Review risky writes. If it is off, or the check cannot be completed, an action set to Review asks for approval instead. Nothing runs unchecked.

When a run has nobody to ask, such as a scheduled run or a workflow, a function that would need approval is not run, and the Coworker is told it could not ask.

Routine actions a Coworker takes at your request, such as sharing a file, publishing an artifact, saving a memory or editing a document, run without a prompt. A connector built for your organization starts on Review if it changes things in other systems and on Allow if it only reads. The Coworker that builds one declares which it is, and your administrator sees and can change that in Settings > Connectors. A Coworker can later mark a connector as changing things, but only an administrator can mark it as read-only.

Who can enable a connector#

A Coworker's own Supervisor can enable and disable connectors for it. Anyone else who needs a connector is told by the Coworker that its Supervisor must enable it.

You can enable a connector in two places: from a card in chat, or from the Coworker's details page. Both do the same thing.

Enable from a card in chat#

When a Coworker finds a connector that would help but is not enabled for it, it shows you a card titled Enable followed by the connector's name, with the connector's description.

1. Check the secrets listed under Secrets it uses (see below), and add any value that is missing.
2. Select Enable.

The Coworker carries on with your request by itself as soon as the connector is enabled. The card then reads that the connector "is enabled for this Coworker." If someone enabled it on the Coworker's page in the meantime, the card shows the same.

Enable from the Coworker's details page#

1. Open the Coworker's details page and expand Connectors. The section lists your organization's connected systems, then every connector built for your organization. Each one shows its name, a Built for your organization label, its description, and which Coworker built it and with whom.
2. Check the secrets the connector uses, and add any value that is missing.
3. Select Enable.

When your organization has no connectors, the section reads "Your organization has no connectors. A Coworker can build one with its Supervisor in conversation."

The secrets a connector uses#

Most connectors need a credential, such as a database address or an API token. Under Secrets it uses, each secret's name is followed by where the Coworker's value comes from:

• A tick with the source, such as This Coworker only, Team: followed by the Team's name, or Company-wide, and the date it was set. Before you enable the connector, an existing shared value reads Existing value — followed by its source, with the note "this value is granted when you enable." Enabling gives the Coworker access to it.
• No value is set, with Add a value. Enable stays unavailable, with the note "Add a value for each secret above to enable it," until every secret has a value.

To give the Coworker its own value:

1. Select Add a value, Use a different value for this Coworker (when the value is shared), or Replace value (when the Coworker already has its own).
2. Type the value in the Value for or New value for field, then select Save value or Replace value. Cancel closes the field.

A value saved here belongs to this Coworker alone and is used in place of a Team or company-wide value with the same name. Values are stored encrypted and can be replaced but never viewed. See Secrets.

Disable a connector#

1. Next to Enabled, which shows who enabled the connector and when, select Disable.
2. The dialog asks Disable followed by the connector's name. Select Disable connector.

From then on, the Coworker cannot use the connector. The secrets it was granted stay in place, and you can enable the connector again at any time. To also take a secret away from the Coworker, remove it in the Coworker's Secrets section.