Integrations

Workspace and personal integrations

Understand which integrations belong to the workspace or the individual user, and configure mail, calendar, address, geolocation, Stripe, and publishing safely.

agaro separates workspace credentials from personal connections. This prevents one employee's mailbox or calendar from silently becoming the organization's shared integration.

Workspace versus personal scope

ScopeLocationExamples
WorkspaceSettings → Integrations and related workspace settingsOutgoing Gmail server, Outlook, provider application configuration, address autocomplete, geolocation
PersonalAccount Settings → IntegrationsPersonal Gmail invoice sending, personal Google Calendar connections

Workspace settings are generally available to Super Admins and Managers, with certain credentials restricted to Super Admin. Personal connection mutations are available only when the user's role, workspace modules, subscription state, and deployment configuration permit them.

Workspace outgoing Gmail

Use Settings → Integrations → Gmail to connect the mailbox used for workspace notifications and automation. This is separate from a user's personal Gmail invoice sender.

The page lists connected outgoing servers and their from addresses. Removing a server stops that route from being used for future delivery. Review Settings → Communications → Delivery Diagnostics after connection.

Personal Gmail

Use Account Settings → Integrations → Gmail to send supported invoice email from your own Gmail address. The deployment must enable personal invoice sending, Google OAuth must be configured, and the Invoices module must be available.

Disconnect the personal account when the user changes roles or leaves the organization.

Microsoft Outlook 365

Use Settings → Integrations → Outlook for shared Outlook sending and receiving. A Super Admin enters the Azure application details and authorizes the mailbox. The optional from address controls the sender used where permitted.

Disconnecting Outlook stops future mail through that connection. Keep provider secrets out of chat, notes, and source files.

Google Calendar

Workspace Settings contains the Google Calendar application enablement surface. Individual users connect their actual calendars from Account Settings → Integrations or the Scheduling page.

Connected calendars can be used for availability conflict checks and read only upcoming event visibility. Scheduling remains the system of record for agaro manual events and booking records. Google sourced rows are displayed as read only in the Scheduling list and calendar.

Address autocomplete

Use Settings → Integrations → Address Autocomplete to review provider status, store the supported provider key securely, and test a live address preview.

An autocomplete result is a convenience, not proof of a legal or deliverable address. Verify critical billing, tax, and shipping addresses.

Geolocation

Use Settings → Integrations → Geolocation to select the supported workspace coordinate provider. The current workspace configuration supports no provider or OpenStreetMap based geolocation where available.

Geocoding can fail or return an approximate location. Do not use it alone for safety critical routing or jurisdiction decisions.

Stripe for customer payments

Use Settings → Payments as a Super Admin to connect the tenant's own Stripe account for storefront orders, invoices, and supported paid booking flows. agaro does not silently route tenant customer payments through its platform subscription account.

Agency client collection uses the agency's separate Stripe Connect account under Agency → Billing.

Vercel publishing

Use Settings → Publishing to connect a workspace Vercel destination for App Builder. Without an active connection, App Builder can still use agaro hosting.

Domains

Use domain settings and the App Builder publish dialog to connect an existing domain or manage a purchased one. Domain DNS and email DNS are separate. Pointing a website does not authenticate Gmail or another email provider.

Troubleshooting

I connected Gmail but workspace automation does not use it

Confirm whether you connected personal Gmail or the workspace outgoing server. They serve different scopes. Then review delivery diagnostics.

Google Calendar is unavailable

The Scheduling module, Google application configuration, and an active mutable workspace are required. Ask a workspace administrator to verify all three.

An integration page says not configured

Some integrations require platform deployment credentials before a workspace can authorize its own account. A Super Admin cannot repair a missing platform environment setting from the browser.

A former employee's integration is still present

Disconnect the personal connection during offboarding. Suspending the user limits access but does not substitute for revoking third party authorization.