Connected Apps

Connected Apps let you securely link outside tools (Gmail, Google Calendar, Google Drive, Slack, Dropbox, GitHub, HubSpot, Mailchimp and Xero today) so your Chief of Staff can search and cite them alongside your workspace data. Connect an account once and its items are indexed for fast, permission-aware recall; Chief answers with a link straight back to the original.

• Your data stays yours, a personal connection (e.g. your own mailbox) is indexed privately: only YOU can recall it through Chief. Nobody else in your workspace (not even an admin) sees your private connected items. Shared/org connections are visible to the whole team. This per-user fence is enforced in the database, not just the UI.
• Secure by design: access tokens are stored in a secret-isolated table with no client access (service-side only), every read is RLS + role-checked, and connecting is gated per role under Settings ▸ Roles (the /connectors CRUD matrix) and by your plan.
• Write-back is approve-first, the Outbox on Connected Apps lets you (or Chief) draft an email or Slack message, but nothing leaves your workspace until an owner/admin approves it. Sending is switched on app by app: until it is on for an app, approving says so, and Chief hands you the text to send yourself rather than queuing it. Sends are capped per hour, every attempt is logged with its result, and the whole lane sits behind a per-app platform kill-switch.
• Google Calendar (since this release) is read-only: Chief sees your primary calendar from two weeks ago to six weeks ahead, each meeting with its time, place, people and video link, so you can ask what is on tomorrow, when you last met a client, or who is in Thursday's call. Nothing is ever written to your calendar, and a private connection is visible to you alone.
• Dropbox, GitHub, HubSpot, Mailchimp and Xero are live. Dropbox shows Chief your files by name, folder and date (never their contents), GitHub your open issues and pull requests, HubSpot your contacts and deals, Mailchimp your campaigns and how each one did, and Xero your invoices with who each is for and what is still owed. Every one asks the vendor for read access only, and Chief never writes to any of them. The one exception you will see on a consent screen is GitHub, which offers no read-only permission for private repositories; WorkBOS only ever reads with it.
• QuickBooks (invoices) is live too. Three more are built and switch on once Microsoft registers the WorkBOS app: Outlook mail, Outlook Calendar and OneDrive.

• Connecting: open Connected Apps, choose whether the connection is “Only me” (private) or “Whole team”, then click Connect and approve access in the provider’s window. Disconnect any time from the list (that also removes its synced items).
• Admins: under Provider setup (platform admins only) paste each app’s OAuth client id and secret, set the redirect URI and scopes, and enable it. Secrets are kept encrypted in the secure key store (Vault) and are never shown back.