Connected appsRevocable, on your terms

Your other apps, on the same desk.

Connect the tools you already use and LumenAgent reads from them, or writes back, inside the same run that produces your files. Eight connections are built in; provider-hosted ones arrive over the open connector standard as they become available.

Download freeSee every permission

Every connection is optional, scoped to the feature that needs it, and revocable from where you made it.

Built in
Eight connectionsGoogle, Microsoft, Dropbox, Slack
Scopes
Only what is neededEach beside the feature that uses it
Sends and posts
Wait for youBehind your approval setting
Disconnect
Deletes our tokenAnd asks the provider to revoke, where it can

01What it does

What a connection is actually worth.

Not a wall of logos. A source the agent can read in the same run that produces your files — and a permission you can read, scope down and take back.

01In the run

It reads from them and writes back, mid-run.

A connected app is not another tab to visit. LumenAgent pulls from it while it works and writes the result back in the same run. Pages, files, messages and events become sources — and the moment something would leave your desk, the run stops for you.

  • Pages, files, messages and events become sources
  • Writes land in the app you connected
  • A send, a post or a publish waits for you
Run — Launch briefLumen Core3 connected apps · 1 gated action
No Notion · read14 pages from the Launch workspace Done
Gd Google Drive · read3 attachments the pages linked to Done
LumenDocs · wroteLaunch brief.lumendoc, in your library Done
Sl Slack · post to #launchA four-line summary with a link to the brief Needs approvalApprove
Launch brief.lumendocIn your libraryOpen

02Every scope, in plain words

The permissions page lists each scope LumenQube asks for beside the feature that needs it — and the line it cannot cross.

Least privilege, scope by scope

Service and scopeWhat it is forWhat it cannot do
OneDrive & SharePointFiles.Read.All Find a file, import CSV, XLSX or JSON, refresh a connected table. Write — unless you choose save-back and grant it.
Outlook MailMail.Send Send a new email or reply — only after you start or approve it. Send arbitrary HTML, scripts or unsafe links.
Slackchannels:history Read conversations the LumenQube bot was added to. Search the workspace, read the member list, delete.
Slackchat:write Post when you start or approve it. Post because a conversation was read.
Dropboxfiles.content.read Search and import the file you pick. Upload, edit, share or delete.

03One service at a time

Google is not one switch. Drive, Gmail, Calendar and YouTube are authorized separately, and read and write stay apart. Disconnect deletes LumenQube’s stored token record and asks Google to revoke the grant once no other Google service you connected still relies on it.

Google accountEach service on its own
GdDriveReadWrite
GmGmailReadSendConnect
GcCalendarReadWrite
YoYouTubeNot connected
Gmail disconnected. LumenQube’s stored token record was deleted; Google is asked to revoke the grant once no other Google service you connected still relies on it.

04Read-only until you ask for more

Dropbox can find and import a file, and can never upload, edit, share or delete one. OneDrive and SharePoint start read-only and ask for write access only when you choose to save back.

DrDropboxRead-only SearchImport a fileRefresh a tableUploadEditShareDelete
OnOneDriveStarts read-only SearchImport a fileRefresh a table Save back to OneDrive? It asks for Files.ReadWrite.All first.

05Bring your own tools

Connect any server that speaks the open standard and its tools join the same run, behind the same approvals as everything else.

Your own serverhttps://tools.northwind.co/mcpConnected Tools it brings · 4 lookup_customerReadopen_ticketReadlist_invoicesReadrefund_orderAsks first
In the same run lookup_customerFound Acme Ltd · 3 open invoiceslist_invoicesINV-3308 and INV-3311 both billedLumenSheetsBuilt the reconciliation

02LumenAgent + your apps

Three apps, one run, one question for you.

It reads the Notion workspace, pulls the attachments from Drive, writes the brief in LumenDocs — and stops before posting to Slack. Approve the exact post, change it, or decline and it takes a different route.

Reads
Notion pages, Drive files, Slack threads, mail
Writes
Into the app you connected, or a file in your library
Asks
Before a send, a post or a publish
Disconnects
Deleting our token record, and asking the provider to revoke where it can

03The full toolkit

Every app, every scope, every control.

Connected from the feature that needs it, readable in plain words, and disconnected the moment you say so.

Built in · 8

Wired into the editors.

  • Google Drive and Gmail
  • Google Calendar and YouTube
  • OneDrive and SharePoint
  • Outlook
  • Dropbox and Slack

Provider-hosted

Over the open connector standard.

  • Offered once configured and available
  • The provider supplies sign-in and scopes
  • A catalog entry is not a promise of approval
  • Your own servers and tools

Least privilege

Only what the feature needs.

  • Dropbox read-only
  • OneDrive starts read-only; save-back asks
  • Reading and sending mail are separate actions
  • Slack reads only where the bot was added
  • Nothing posted because something was read

Your controls

From the same screen.

  • Review the provider’s consent screen
  • Ask before every consequential action
  • Disconnect deletes our token record
  • And asks the provider to revoke, where it offers that
  • Microsoft and Slack workspace installs: revoke at the provider

04Permissions, app by app

Permissions and why they are necessary

Every scope LumenQube asks Microsoft, Dropbox and Slack for, the feature it serves, and the boundary it cannot cross.

Connected apps · Reviewed July 28, 2026

Service and OAuth scopeUser-facing use in LumenQubeAccess boundary
Microsoft identityopenidprofileemailoffline_accessIdentify the Microsoft account connected to Outlook or OneDrive & SharePoint, and keep the user-selected connection available without repeated sign-in.Identity and offline access do not themselves grant file, mail, calendar, or contact access.
OneDrive & SharePointFiles.Read.AllFiles.ReadWrite.All (incremental)Sites.ReadWrite.All (incremental)Search and import files with read access. When the user chooses save-back and grants the additional scopes, create or update the selected file or site content for that action.The connection starts read-only. Write scopes are requested incrementally for user-directed save-back; they are not part of the default read connection.
Outlook MailMail.ReadWriteSearch and read requested messages and, when the user directs it, create or update mail content needed for the Outlook workflow.The product does not expose mailbox deletion or bulk background processing. Sending is separately authorized by Mail.Send.
Outlook MailMail.SendSend a new email or reply only after the user initiates or approves the action. Messages can be plain text or use a safe Markdown subset rendered to formatted HTML with a plain-text alternative.Used only for sending; formatting requires no additional permission. Arbitrary HTML, scripts, styles, event handlers, and unsafe link schemes are not accepted.
Outlook CalendarCalendars.ReadWriteList or search events and create, update, or respond to an event at the user’s direction.Limited to calendar data. It does not grant access to Microsoft files or mail.
Outlook ContactsContacts.ReadFind a contact the user asks for when addressing an approved message or completing an Outlook task.Read-only; LumenQube cannot create, change, or delete contacts.
Dropboxfiles.metadata.readfiles.content.readSearch files the user can access, import the spreadsheet or structured-data file they select, and refresh explicitly connected table data.Read-only. LumenQube does not request file upload, edit, sharing, or deletion permissions.
Slack conversationschannels:readchannels:historygroups:readgroups:historyim:readim:historympim:readmpim:historyList and read only conversations where the installed LumenQube bot is a member, and search recent messages locally within those joined conversations for a user-requested task.LumenQube does not request workspace-wide search:read, user-token history, member-directory, administration, or deletion scopes.
Slack postingchat:writePost a message to a conversation where the LumenQube app is permitted, only when the user initiates or approves it.No posting is performed merely because the app is installed or a conversation is read.

How connected-app data is handled

  • Access and use. LumenQube accesses provider data only after the user connects that service and only to deliver the visible feature described above.
  • Storage and security. OAuth tokens are encrypted at rest in LumenQube’s server-side vault. Provider responses are not routinely retained as a separate server-side dataset. Content may remain in a local LumenQube document or task history when the user chooses to use or save the result.
  • AI-assisted tasks. When a user explicitly asks LumenAgent to summarize or transform connected content, the content needed for that request may be sent through LumenQube’s managed backend to the selected processor or eligible fallback identified in our Privacy Policy. LumenQube uses it to return the requested result, not for advertising or as generalized model-training material. A provider’s own data use, retention and permitted security or legal processing depend on the service and our account terms and settings.
  • Sharing. LumenQube does not sell connected-app data, use it for targeted advertising, or disclose it to data brokers. Service providers receive data only as needed to deliver the user-requested feature, secure the service, or comply with law.
  • Human access. LumenQube personnel do not read connected content unless the user gives explicit permission for specific support, access is necessary to investigate abuse or a security incident, or access is required by law.
  • Retention, disconnect and revocation. The encrypted authorization record remains until the user disconnects or closes the account. Disconnect deletes LumenQube's stored token record and, where the provider offers revocation, also asks the provider to revoke the grant: Google once no other Google service you connected relies on it, Dropbox, Slack user tokens, and Connect Hub apps that publish a revocation endpoint. Microsoft offers no per-app revocation, and a Slack workspace installation is shared with your workspace, so revoke those in the provider’s account controls, where you can also confirm any grant has ended. Neither action undoes completed provider actions or deletes messages, files, events, posts or saved copies.

User-directed deployments

Vercel, Netlify, Cloudflare Pages and GitHub Pages connections use a token you provide to upload selected project files. LumenQube stores the token in sealed form until you disconnect it. Disconnecting does not revoke the token at the provider or delete the remote site or repository. GitHub Pages creates a public repository by default, so review the destination and visibility before approving the deployment and remove remote content in the provider account when it is no longer needed.

Your controls

  1. Connect only the service you want from its relevant feature in LumenQube.
  2. Review the provider consent screen before granting access.
  3. Set Act in connected apps to Ask if you want approval before every consequential action.
  4. Use Disconnect in LumenQube to delete the stored token record; LumenQube also asks Dropbox to revoke its grant. Revoke Microsoft access, and a Slack workspace installation, from those providers’ account controls. Remove remote or saved content through the service where it remains.
  5. Request account and associated cloud-data deletion at privacy@lumenqube.com.

Google permissions are documented separately on our Google integrations page. For the complete legal disclosure, read our Privacy Policy. For connection help, contact support@lumenqube.com.

05Questions

Common questions

Which apps can I connect?

Eight connections are built in: Google Drive, Gmail, Google Calendar, YouTube, OneDrive and SharePoint, Outlook, Dropbox and Slack. Provider-hosted connections over the open connector standard — Linear, Notion, Sentry, Stripe and others — appear when they are configured and available; a catalog entry is not a promise. You can also add your own server.

Will it post or send without asking?

Consequential actions wait for your approval setting. Set “Act in connected apps” to ask, and every send, post and publish stops for you with the exact content shown.

Where are my tokens kept?

Encrypted at rest in a server-side vault. Disconnect deletes LumenQube’s stored token record and, where the provider offers revocation, asks it to revoke the grant: Google once no other Google service you connected relies on it, Dropbox, Slack user tokens, and provider-hosted apps that publish revocation. Microsoft and a Slack workspace installation are revoked in the provider’s own account controls. Neither undoes actions already taken.

Is connected content used to train models?

LumenQube does not use your content to train a generalized AI model as a product purpose. Content is sent only when you request an AI feature, to the selected processor or eligible fallback needed for that request. A provider’s own data use, retention and permitted security or legal processing depend on the service and our account terms and settings. See Privacy Policy §7.

Which plan do I need?

Connectors come with Pro and up. Every editor stays free, with no trial timer.

Connected, not absorbed.

Connect the apps you already use, keep every permission readable, and disconnect any of them in one click.

Download freeSee pricing

Connectors come with Pro and up. Every editor is free.