My Connectors
My Connectors is where you link your own work accounts — your Outlook, your Gmail, your JIRA — so that agents can act on your behalf, with your data, under your control. Until you connect something, agents simply can't see it; once you do, they can only see what you've allowed.
You'll find My Connectors in the EnClaw web app when your role includes it — the sidebar shows it if managing your own connectors is part of your setup. If you don't see the page, that's not a fault: in some organisations an admin manages connectors on your behalf, so ask them if an account needs linking.
What "delegated access" means
When you connect an account, you're delegating: the agent acts as you, and sees only what you can see.
- If you connect Outlook, an agent reading "the calendar" reads your calendar — not your manager's, not the company's.
- Your colleague connecting their own Outlook sees only their data. Connectors are strictly personal; nothing you connect is visible to anyone else's agents.
- If you haven't connected a service, an agent asked about it will say it's not connected rather than guessing or borrowing someone else's access.
In short: connectors extend your own reach, nothing more. The agent becomes a pair of hands working inside accounts you already own.
The connectors
| Connector | How it links | What agents can then do for you |
|---|---|---|
| Microsoft / Outlook | Sign-in pop-up — approve with your Microsoft account | Read your email and calendar, draft and send email, create events, manage your To-Do tasks |
| Google / Gmail | Sign-in pop-up — approve with your Google account | Read and send Gmail, work with Drive files |
| JIRA | Your email + a personal API token from JIRA | Search and read issues, create and update them (with approval) |
| Productive.io | A personal API token + your organisation ID | Read projects and tasks, create/update/assign tasks (with approval) |
| GitHub | A personal access token | Work with repositories on your behalf |
| Slack | A short code exchange — the EnClaw bot DMs you a code to confirm it's you | Ties your Slack identity to your EnClaw account so DMs and mentions are correctly yours |
For the sign-in style connectors (Microsoft, Google), you'll see the provider's own consent screen listing exactly what's being granted — the same pop-up you'd see connecting any app. For the token style (JIRA, Productive.io, GitHub), the service's own settings page is where you create the token; you then paste it into EnClaw, where it's stored encrypted.
Connecting, step by step
- Open My Connectors and pick the service.
- Follow the prompt — sign in and approve, or paste your token.
- Choose your permissions (next section).
- Save. The card shows Connected, and agents can start using it immediately.
Granular permissions and risk indicators
Connecting a service doesn't have to mean handing over everything. Each connector offers per-action toggles — separate switches for things like:
- Read my email — on
- Read my calendar — on
- Send email — off, thanks
Alongside each permission you'll see a risk indicator: read-only actions are low risk (they can't change anything), while actions that create, change or send things are flagged higher. A sensible pattern is to start read-only, live with it for a week, then switch on the write actions you actually want — remembering that risky actions are also protected by approvals, so even a permission you've enabled still pauses for your yes before anything is sent or created.
You can change these toggles at any time; changes take effect straight away.
Token health: connected, expired, disconnected
Each connector card wears a health badge:
| Badge | Meaning | What to do |
|---|---|---|
| Connected | All good — agents can use it | Nothing |
| Expired | The link has lapsed (tokens and sign-ins don't last forever, and password changes can end them early) | Re-authenticate — one click, see below |
| Disconnected | No active link | Connect (or reconnect) if you want agents to use this service |
An expired connector is the single most common reason an agent suddenly "can't see" your email or calendar. Nothing is broken and nothing is lost — the permission slip has just run out.
Re-authenticating
- Open My Connectors.
- On the expired card, choose Re-authenticate.
- Approve the sign-in (or paste a fresh token for the token-based services).
The badge flips back to Connected and agents pick up where they left off. Your permission toggles are kept — you won't need to set those again.
Disconnecting
To cut a service off, open its card and disconnect it. Agents lose access immediately. You can reconnect any time, and it's completely fine to keep only the connectors you actually use — many people run happily with just Outlook or just Gmail.
Quick answers
- "Do agents read my email all the time?" No. They look only when you (or a schedule you created) ask them to do something that needs it.
- "Can my admin see my inbox through my connector?" No. Your connector serves your own conversations with agents; it isn't a window for anyone else.
- "Something says it's not connected but I did connect it." Check the badge — it's probably Expired. Re-authenticate and try again. More in Troubleshooting.