No Passwords Shared
Access uses each app's own approval system. FLCPA.AI holds a token the app can cancel, never a password.
Client Connections
FLCPA.AI works inside the systems your business already runs. Connecting them takes two short sign-in sequences, each approved by you on the app's own page and each revocable at any time.
Why Two Sign-Ins
Part 1 lets assistants work in your apps as tasks happen. Part 2 keeps a read-only copy of your records for reporting and backup. Keeping them apart means your read-only copy never shares a key with tools that can act.
| Topic | Part 1 · AI Assistance | Part 2 · Reporting And Backup |
|---|---|---|
| Purpose | Assistants look things up and take approved actions for you. | A complete, dated copy of your records for dashboards, history and backup. |
| How It Works | Each task reaches into the app at the moment it runs. | Records are copied on a schedule into your private dataset. |
| Timing | Live. | Nightly, then only what changed. |
| Can It Change Records | Only where you approved Read And Act. | Never. Read only. |
| Where Data Lives | In your apps. Results appear in your Reporting Studio workspace. | Your own Google BigQuery dataset, separate from every other client. |
| Runs Through | Composio | Airbyte and Google BigQuery |
| Typical Apps | QuickBooks, Gmail, Slack, Shopify, Outlook | QuickBooks, Stripe, Shopify, Zoho Books, Xero |
Each part holds its own access. Approving QuickBooks in Part 1 gives Part 2 nothing, and removing one leaves the other untouched. The separation is deliberate: the service that can act never holds the key to your full record history.
The Sign-In Sequence
The same four steps for every app, in both parts.
Your engagement email includes a link made for your business. It lists only the apps your engagement needs.
Connect opens QuickBooks, Google or Microsoft directly: their page, their address bar, their login.
The app lists exactly what FLCPA.AI is asking for. Approve, and the app issues an access token.
You land back on your link with the app marked Connected ✓. Repeat for the next app.
Security And Control
What protects each connection, and how to end one.
Access uses each app's own approval system. FLCPA.AI holds a token the app can cancel, never a password.
Read only wherever the work allows. Every card shows its access level before you approve.
Part 2 copies land in a dataset set aside for your business alone.
Assistant actions in Part 1 are recorded with the time, the app and the result.
Disconnect on your private link, ask your engagement lead, or remove FLCPA.AI in the app's settings.
Microsoft 365 and Google Workspace admins can approve once for the whole organization.
Common Questions
The questions clients ask most often.
Already A Client
Lost it or expired? Your engagement lead can send a new one the same day.