# Company tools and your own tools

Dija works directly inside the tools your team already uses, including your CRM, outbound email platform, mailbox, calendar, meeting notes, product analytics, publishing and email marketing tools, ad and SEO reporting, docs, and web search. You manage every integration on [Connections](https://app.dija.ai/connections).

## Company tools vs. personal tools

Every tool in the directory shows its sharing scope under **For whom**:

| Scope on **For whom** | Who connects it | Who uses it and sees its data |
| --- | --- | --- |
| **The company** (for example, CRM or email sender) | Workspace owner only | Shared across everyone's jobs; results are visible to the team |
| **Each person their own** (for example, personal meeting notes) | Each teammate connects their own | Used only in that person's jobs; everything read stays private to them |
| **The company, or each person their own** (for example, mailbox or calendar) | Owner for **For the company**; anyone for **Just for me** | Shared when connected **For the company**; private to you when connected **Just for me** |

Active connections display **Company**, **Yours**, or the teammate's name. Everyone on the team can see which tools are connected and whose they are, but nobody can see what Dija reads inside someone else's personal tools. See [Private and shared work](privacy.md).

## How Dija works in connected tools

A job can use shared company tools plus the personal tools of the person who started it, never a colleague's personal tools. Read-only lookups run immediately, while any action that creates, edits, sends, or deletes external data waits for approval first. See [Approvals and rules](approvals.md).

If you ask for work that needs a tool nobody has connected yet, Dija completes what it can without it and links the tools that would unlock the rest. When the missing tool is a company tool and you are not the owner, Dija forwards the connection link to the owner and mentions that you asked.

## Connecting a tool

1. Open **Connections**, search by name or pick a category tab, and click **Connect**.
2. Sign in with OAuth at the vendor or paste an API key from your account there (a few tools ask for part of your workspace URL first). Enter keys only on **Connections**, never in chat.
3. When a shared company tool connects for the first time, Dija reads its structure and a sample of recent records (read-only) and writes a tool note so future jobs follow your setup. Any jobs waiting on that tool category resume automatically.

### Permissions

- **Workspace owner:** Connects, reconnects, and removes company tools, and adds custom integrations.
- **Every teammate:** Connects their own personal tools. You, anyone above you in your reporting chain, or the owner can manage your personal connections.

## Reconnecting or removing a tool

If a connection loses access (for example, when a token is revoked at the vendor), its status changes to **Needs attention** and Dija sends a link to the connection's owner (or the workspace owner for company tools).

- On **Connections**, click **Reconnect** to restore access, or **Finish** if the initial sign-in was left incomplete.
- Inside a connection's detail view, click **Check again** to test it or **Replace the key** to rotate an API key.
- Removing a connection revokes Dija's access and stops any scheduled checks. Past jobs, notes, and approval rules stay intact; if you reconnect the tool later, Dija drafts fresh tool notes while your existing rules still apply.

## Browsing the directory and adding custom tools

**Connections** groups integrations by category alongside tabs for **Models**, **Channels**, and **Methods** (covered in [Models and keys](models.md) and [Chat, voice and calls](channels.md)). **Recommended for you** highlights tool categories your active methods still need. Verified partners appear first in their category with a **Partner** badge, and every listing shows its publisher, source, **For whom** scope, and included skills. You hold your own account with each vendor and pay them directly.

To connect internal or unlisted tools, the workspace owner can open **Your own** and click **Add your own**:

- **A tool Dija works in (an MCP server):** Add a name, a public `https` URL, and optional usage notes.
- **A tool that only sends events (a webhook):** Generates a unique webhook URL to paste into your external tool.
- **A plugin folder:** Upload a plugin folder built for Dija, Claude, or OpenAI containing its manifest and skills.

## Credentials stay sealed

Dija connects directly to each vendor with no third-party middleware in between. OAuth tokens and API keys are stored encrypted and never placed in prompts, logs, or messages, so the AI model never sees your credentials. See [Models and keys](models.md).
