Skip to content

Scout Connectors ​

Scout Connectors connect external systems to one user account, through OAuth. Scout then retrieves context in the permission boundary of that user.

What this is ​

Connectors are:

  • user-scoped: they belong to one user
  • type-scoped: one Connector for each user for each Connector type
  • OAuth-based: Modulos stores access and refresh tokens for the user

Connectors are for interactive, user-scoped access. If a Connector expires, authorize it again.

Where in Modulos ​

  • User Settings → Connectors. The tab shows when chat or Scout is on for your organization.

If you cannot see the Connectors tab, speak to your Organization Admin.

Supported Connector types ​

Supported Connector types include:

  • GitHub
  • Bitbucket
  • Google Drive
  • Atlassian

Organization controls

Organization Admins can make Connector types available or unavailable for the organization on the Organization → Source & Connectors page. If you cannot see an expected Connector type, speak to your Organization Admin.

Connect an external system ​

  1. Open User Settings → Connectors.
  2. Select Add Connector.
  3. Select a Connector type.
  4. Follow the authorization flow.
  5. Make sure that the Connector shows the status Active.

You cannot select a type that you connected before, or a type that your organization did not turn on. After you connect a Connector, Scout can find and retrieve context that the connected account has permission to read. Scout uses a Connector only when you select it with Context in a chat about an AI System or a Draft. A Global chat cannot use Connectors. See Scout.

When you accept an Evidence proposal from Scout, Modulos gets the proposed files through your Google Drive, GitHub, or Bitbucket Connector. For a file in GitHub, a GitHub Source of the AI System comes first, if one has the repository. See Propose Evidence.

User Settings Connectors tab with a GitHub Connector that is Active, a Google Drive Connector that is Expired, and the Add Connector button.

The Connectors tab shows the status of each Connector.

  1. Add Connector Connects a new type of Connector.
  2. Expired The Connector needs a new authorization.
  3. Re-authorize Authorizes the Connector again with new credentials.

A Connector has the status Active, Expired, or Disabled. For an Expired Connector, select the refresh icon to authorize it again. To remove a Connector, select the delete icon.

Google Drive: you pick what Scout can see ​

The Google Drive Connector does not give access to your full Drive. The Connector holds Google's drive.file scope, which covers only the items that you select.

  • To select items, use the Connector controls in the Scout panel. Select the Add files from Google Drive icon. The Google Picker opens. Select the files that Scout can read. You can open folders, but you cannot select a folder.
  • To give Scout more material, open the Picker again and select more files.
  • When you delete the Connector, Scout loses access to all the items that you selected.

Sources vs Connectors ​

Connectors are not Sources:

  • Sources are service accounts attached to AI Systems. All users of an AI System share them. Runtime Inspection and other AI System automation use them.
  • Connectors are user accounts connected to users. They are personal. They follow the permissions and accountability of the individual user.

Important considerations ​

  • Use Connectors when Scout must use your user-level access to docs, code, or tickets.
  • Use Sources when the automation must be stable and shared, and must not use the account of one person.
  • If your access changes in an external system, the access of Scout changes too.