Reconnect company data without broadening access

An IT administrator or a knowledge owner who sees that a connected source stopped syncing into Company Knowledge, often after a password rotation in the source system. It shows up when a lesson update fails because the SOP it depends on is stale. The temptation is to fix the connection by granting more access than the original approval covered.

A recovery plan confirms the intended account, current authorization and a bounded test of one permitted source.

• Ask your workspace owner which connection stopped, who owns the source and when the last successful import ran.
• Copy the error shown on the connector, removing any token or private path, and check it against the source system's own status.
• Sign in to the source system as the intended service account and reauthorize through the provider's documented flow, keeping the same scope as before.
• Restore one permitted source first and confirm its document version in Company Knowledge before asking for anything else to be connected.

A fictional manufacturing supplier keeps its work instructions in a shared drive connected to Company Knowledge. After IT rotated the service account password, the connector has failed to sync for six days. The knowledge owner, Ahmed, notices when a revised torque procedure is missing from a lesson draft.

• The connector row shows the last successful sync six days ago, the error text, and the same three approved folders as before.
• After the connection is restored, Company Knowledge shows the new version number and date of the torque procedure.
• The other two folders sync afterward, and no folder was added during the fix.

Only use the provider's documented reconnection flow. Reconnecting must not silently ingest a wider folder or restore revoked permissions.

• The reconnected account is the same service account that was originally approved.
• The connector scope after the fix lists the same sources as before.
• One source synced and showed a new version before the rest were enabled.

If it does not work: check whether the source system revoked the app authorization entirely, which only the source owner can fix. If the sync succeeds but the document version does not change, the file may not be in the approved folder. Contact the source owner for permissions and your workspace owner for connector settings; a reconnection must never quietly widen scope or restore permissions revoked on purpose.

Will reconnecting re-import everything? It resumes syncing the approved scope. Documents already in Company Knowledge keep their version history; unchanged files are not duplicated.

• Which connectors are available? Google Drive and Notion connect to Company Knowledge directly; Dropbox and SharePoint are planned, not available today. Your connector list shows what your organization has enabled.