Connecting your accounts

Your administrator can set up outside systems, such as GitHub, for your Coworkers to work in. A Coworker can work in a system only when its Supervisor has enabled that system for it. When it works for you there, it uses your own account, so it can see and do only what you can. You sign in with the system yourself. You never type a password or a token into Workforce Intelligence.

Connect an account#

1. Open your profile menu and select Settings. My API keys is the page it opens on, and Connected accounts is on it.
2. Under Connected accounts, find the system and select Connect.
3. Sign in with the system and approve the access it asks about.

You return to the page you started from, which here is Settings, where a message reads, for example, "GitHub is connected." The row now reads "Connected as" followed by your account name. If you cancel on the system's own page, the message reads "You chose not to connect, so nothing was changed." Select Connect to try again. If the system itself turns the sign-in down, the message reads "<System> refused the sign-in. Ask your administrator to check the connection settings." Your administrator can see the system's reason and fix the connection.

Connected accounts appears once your administrator has set up at least one system.

If your organization lets Knowledge Bases sync SharePoint as a person's Microsoft account, one entry named after the SharePoint connection appears in the same list. Connect it the same way. Under its name the entry reads "Used to sync SharePoint sites into Knowledge Bases you own. Coworkers cannot use it." Your account is then used only to sync the SharePoint sites of Knowledge Bases that you own and that you chose to sync as your account (see SharePoint sources). When such a site needs you to sign in again, its row on the Knowledge Base says so and links here.

You can also connect from a conversation. When a Coworker needs your account on a system you have not connected, a card reads the system's name followed by "isn't connected for you". Select Connect on the card. After you sign in, you return to the same conversation and the card reads "is connected." The Coworker carries on with your request by itself, so you don't need to type anything. If you cancel on the system's own page, a message above the conversation says so, and you can select Dismiss. If an earlier connection has stopped working, the card reads the system's name followed by "needs to be connected again". Select Connect to sign in again.

To sign in again from Settings, select Connect again on the system's row. If your administrator has added permissions to a system since you connected, its row reads "Needs new access — connect again"; connecting again gives your Coworkers that access. The row also asks you to connect again when the system itself turns down your sign-in during a request, and a Coworker's request then shows the same connect card. If a Coworker reports that your connection doesn't have the access something needs, ask your administrator to add the permission, then connect again. To remove your account, select Disconnect and confirm. Your Coworkers cannot use that system for you until you connect again. Disconnecting the SharePoint entry instead stops the sites that sync as your account until you connect it again.

Choose what your Coworkers may do#

Under What your Coworkers may do, each system has its own card, closed to start with. The card shows the system's name and a summary such as "15 functions · 9 allowed · 4 ask first · 2 blocked". Select the card to open it and see the things a Coworker can do in that system, such as opening an issue, in name order. Long descriptions are shortened; select Show more to read all of one. A system with many items also has a Filter functions box. Your administrator sets where each one starts, and you can only make a choice stricter than that starting point.

Choice	What it means
Allow	Coworkers do it for you without asking.
Review	Coworkers do it without asking unless it looks risky, such as sending a message to someone outside your company or sharing personal information. A risky one asks you first, and the request shows why.
Ask	You are asked before each use.
Block	Coworkers cannot do it for you.

Review is listed only when your administrator has turned on risky-write checks. Without it, an item your administrator set to Review shows as Ask.

A line under each item says what applies now, for example "Your administrator allows this. You can choose to be asked first, or block it." Select a choice to apply it. Select Use the default to go back to the starting point your administrator set.

Some systems also have a Custom requests item, listed once under the system's own name (for example Microsoft) rather than under each of its services. It lets a Coworker send a request that is not one of the listed functions, and it is always one you can set to Ask or Block. Your administrator decides whether it is offered at all.

Choices that would be looser than your administrator's starting point are not offered. An item your administrator has blocked shows Blocked and has no buttons.

A Coworker the system is not enabled for cannot use your account, even though you connected it. It tells you the system is not enabled for it and that its Supervisor can enable it.

Permission cards appear only for the systems you are connected to. If you disconnect a system, its card disappears, and the choices you made are kept for when you connect again.

When a Coworker asks first#

An item set to Ask pauses the Coworker until you answer. An item set to Review pauses it only when the automatic check finds the action risky. See Approving a request.

An item that only looks things up is never held for a check. When nobody is in the conversation, for example in a scheduled run, an item that would need your answer is not run: the Coworker is told it could not ask, and nothing happens in the system.