Project connectors bring shared data sources, communication services, and configured AI providers into a workspace. Available choices depend on the product profile and deployment. Owners and Admins manage connections from the project panel. An Editor can also share an eligible personal connector into the current project, but cannot use the project-only administration controls. A provider appears only when its capability is enabled for project scope.
Connect or refresh a source
Open Settings > Connectors and choose an available provider. The setup follows that connector's capability: some providers use OAuth or admin consent, Google Workspace and Lark also ask for one Drive folder, and API-based services or the workspace AI provider can require configuration values or an API key.
Use Sync now only when the connected card offers it. Pull-based sources such as SharePoint, Google Workspace, Lark, and Airtable can show sync progress, while live-access or externally managed connectors have no scheduled pull. Disconnecting removes the workspace connection but does not delete data in the external source.
An active sync can be paused at a safe checkpoint and resumed later from saved progress. The connected card can also show whether its Skill binding is enabled; turning that binding off stops the linked Skill automation without deleting the underlying connector.
Airtable connections sync exactly the bases the connection was granted on Airtable's consent screen (Airtable grants access per base). To add or remove a base, open the connection's menu and choose reconnect/repair, then adjust the base selection on Airtable's screen — there is no base picker inside Settings, and the granted set is re-read on every successful check.
Connect a workspace AI provider
Owner and Admin roles can choose an AI provider tile and configure the workspace account. Select the provider and, when offered, its API type and region. Enter the API key plus the fields required by that provider, such as endpoint, deployment, API version, base model, or base URL. Use the connection test before saving; a successful probe can return the models available to that credential.
The API key is submitted as a secret and is not shown again in the connection response. Changing an existing endpoint requires the key to be entered again in the same update. A provider can be listed by the deployment but still fail its probe when the endpoint, deployment, region, API version, key, or upstream account is unavailable.
Review SharePoint changes with AI
For SharePoint, open the connection menu and choose Configure AI review. When Review synced changes with AI is enabled and the deployment allows this feature, Evane compares supported content after a successful sync. The first review records a baseline and intentionally creates no Proposal. Later added or changed content can produce an AI-authored Proposal for an eligible reviewer; unchanged, unsupported, or unverified content does not create one. A successful sync therefore does not by itself guarantee a Proposal.
Project connectors and personal connectors are different scopes. Files synchronized by a project connector are readable to members inside that workspace. A member may still need personal Microsoft authorization to open the original SharePoint page, send mail, or use another user-owned capability. See Manage personal connectors and MCP access for user-owned grants.
A missing provider option is different from a disconnected account. Ask the deployment administrator to check provider configuration before repeatedly reconnecting.
