Connect Google Workspace and Microsoft 365 to Lura Assistant

Lura Assistant helps service-business staff answer questions using sources they choose and prepare business documents, events or replies for review. Connecting an account is optional and separate from Google sign-in. Your connection belongs to you in the current LuraFlow workspace; it does not give coworkers access to your personal provider account.

1. Open Settings → Connected apps and choose Google Workspace or Microsoft 365.
2. If your account is already connected, choose Use [your email] to open its card. Use Choose Drive file there; do not add the same account again. Update access or Reconnect is for changing or restoring provider permissions.
3. Select only the capabilities you need. Read the connected-data privacy disclosure before continuing.
4. Use the provider account chooser and review its requested permissions. You can decline; tools needing a missing permission remain unavailable.
5. Under Your accounts → Selected sources, use Choose Drive file, choose a OneDrive file, or select an owned calendar. Mail tools, when enabled, let you search a bounded date range and select a message.
6. Preview a selected source. A preview retrieves current data without storing it as an Assistant conversation.
7. To ask AI about that source, enter a question. This sends the question and a bounded excerpt to the workspace AI processor, currently OpenAI or Anthropic. Connecting alone does not send source contents to an AI model.
8. For an enabled document, calendar or email action, review the exact content and destination before approving. Read the result receipt; a provider accepting an email does not confirm recipient delivery.

• Google Drive: drive.file limits provider access to files selected for Lura or created by it. Google grants edit permission for those files, but Lura reads selected sources and creates new Docs/Sheets through reviewed actions; it does not edit existing files or change their sharing.
• Google Calendar: read access lists and reads calendars you own and explicitly select. Event creation needs a separate write capability and approval of the title, time, timezone and guests. Lura does not edit or delete existing events.
• Gmail: separately enabled read permission supports date-bounded searches and selected message bodies. Attachments are not ingested. Sending requires its own permission and exact-message approval; read access alone cannot send.
• Microsoft 365: use a supported work/school account. Provider file permissions are broader than Google selected-file access; Lura still reads only selected sources. A Microsoft or Azure login alone does not establish a mailbox, OneDrive entitlement or Microsoft 365 license.

Lura does not use connected-account content for general-purpose model training, advertising profiles or data sale. Source text is treated as information, not as instructions that authorize actions. Completed source answers have a short encrypted recovery cache and become unavailable after two minutes. This is not a promise to erase audit records, backups or processor-held copies in two minutes. See /privacy#connected-apps for retention and access/deletion requests.

Disconnect from Lura removes active credentials, selected resources and cached source answers, and stops further use of that connection. It does not undo completed actions or delete provider-held files, events or emails. Google revocation is a separate option under Permissions and Google revocation. An unconfirmed revocation stays visible and tools remain disabled. Microsoft permissions can be reviewed in My Apps or with your organization administrator.