Connect the tools
your team already uses

1. Go to Settings → Linear.
2. Click Connect and authorize Ethira through Linear.

• Create a Linear issue straight from a risk mitigation — it carries the mitigation's title and action across — or link the mitigation to an existing issue.
• Pull the linked issue's status back onto the mitigation on demand, so Ethira reflects where the work stands.
• Unlink an issue from a mitigation at any time.

1. Go to Settings → Jira.
2. Click Connect and authorize Ethira for the Jira site you want to link.

• Create a Jira issue straight from a mitigation — pick the project, issue type, priority, and assignee; Ethira fills in the summary, description, and a tracking label from the mitigation.
• Link an existing Jira issue to a mitigation by searching within a project, and unlink it whenever you need to.
• Refresh the mitigation's status from its linked Jira issue on demand — for example once the issue moves to Done.

1. Go to Settings → Slack and authorize Ethira.
2. Pick a channel by typing part of its name (or paste a channel ID for private channels). Make sure the Ethira bot is a member of that channel.

• Get alerts in Slack for vendor events, risk changes, and other workspace activity.
• Send discovered-vendor (shadow-IT) alerts to a dedicated channel — set it under Supply Chain → Settings → Discovered vendor notifications.
• Ask the Ethira Agent or a scheduled workflow to post to Slack — e.g. "post this summary to #compliance."
• @-mention or DM the Ethira bot to work in Slack the way you would in-app: read and manage vendors and risks; query ERM, regulatory, inventory, RoPA, and the audit log; search and add documents; and kick off research — every action scoped to your own workspace permissions.

1. Go to Settings → Microsoft Teams.
2. Click Connect Microsoft Teams and authorize a Microsoft 365 account. Each connected account appears under Connections.

• Post Ethira Trust Portal updates — questionnaire submissions, answer-ready and reviewer digests — into a Microsoft Teams channel.
• Choose the channel from the teams your connected Microsoft 365 account can access.

1. Go to Settings → Google Drive and authorize Ethira.

• Browse your Drive by folder or search, and link documents into Ethira by reference — no download-and-re-upload.
• Attach Drive files to policies and to your Trust Exchange public documents.

1. Go to Settings → Microsoft 365 and authorize Ethira.

• Browse and link files from OneDrive and SharePoint sites into Ethira — the same way as Google Drive, for policies and documents.

1. Go to Settings → Notion and click Connect Notion workspace.
2. Authorize Ethira in Notion and choose which pages and databases to share — the Agent only ever sees what you share here.

Connect more than one Notion workspace if you need to — each appears under Connections.

• Ask the Ethira Agent — in the app or in Slack — to search your connected Notion workspace and read page content and database entries on demand.
• Have the Agent create a new Notion page for you, such as a summary written under a parent page you choose.

1. Go to Settings → GitHub and authorize Ethira via OAuth — this creates a Personal connection and starts the first repository sync in the background.
2. To include an organization's repos, use Add organization on your personal connection and pick the org — it appears as its own Organization connection.

If your org restricts OAuth Apps, an admin may need to grant Ethira access at github.com/settings/connections/applications first.

• Sync repositories into Inventory → Assets as repository assets (archived repos marked inactive).
• Watch live sync state per connection: queued, syncing, last synced, or failed — with a repository count.
• Re-sync automatically once a day, or on demand with Sync repositories now (which doubles as Retry after a failure).
• Connect multiple accounts and organizations, each as its own connection. Removing one removes the repos it synced — CLI-registered repos are never touched.

1. Go to Settings → GitLab and authorize Ethira via OAuth.
2. Self-hosted GitLab is supported through server configuration.

• Sync every project visible to the account into Inventory → Assets — on connect, daily, and on demand.
• Track the same per-connection sync states as GitHub (queued, syncing, last synced, failed).

1. Go to Settings → Vanta.
2. Enter your Vanta Client ID and Client secret and save.

If credentials are later rotated or revoked, syncs auto-pause after repeated auth failures — save fresh credentials to resume; nothing else to re-enable.

• Import your Vanta vendors into Ethira's vendor register on a daily schedule — including risk levels and contract details.
• Pull in Vanta security-review documents, and import Vanta people into your workspace.
• Feed vendor discovery: each Vanta vendor runs through Vendor Triage and surfaces on your Discovered list once Ethira also sees it in use — no separate "find third parties" step for Vanta.

1. In Cursor (cursor.com/dashboard, as a team admin), go to Settings → Advanced → Admin API Keys → Create New API Key and copy it.
2. In Ethira, go to Settings → Cursor, paste the key, and click Connect Cursor.
3. Optional: install the Ethira Cursor Cost Tracker extension to break spend down by Git branch.

• See Cursor AI usage and cost on the AI Spend dashboard, attributed per person (and per branch with the extension).

1. In OpenAI (platform.openai.com, as an org owner), go to Settings → Organization → Admin keys → Create admin key and copy the sk-admin-… key.
2. In Ethira, go to Settings → OpenAI, paste the admin key, and click Connect OpenAI.

A project key (sk-proj-…) will not work — it must be an admin key.

• Track your OpenAI organization's API spend on the AI Spend dashboard, broken down by model and API key.

1. In Anthropic (console.anthropic.com, as an org admin), go to Settings → Admin keys → Create key and copy it.
2. In Ethira, go to Settings → Claude, paste the key, and click Connect Claude.
3. Optional: for claude.ai Team/Enterprise seat usage (no API), export the spend report CSV from claude.ai and upload it under the claude.ai spend report section.

An Admin key is required to read spend; a regular key connects but reports nothing.

• Track Anthropic Console (API) spend automatically, plus claude.ai seat/usage spend via CSV import, on the AI Spend dashboard.

1. In Requesty (app.requesty.ai), go to Settings → API keys and create a key with the manage permission, then copy it.
2. In Ethira, go to Settings → Requesty, paste the manage key, and click Connect Requesty.

• Track your Requesty routed-model spend on the AI Spend dashboard (Ethira keeps its own running history, since Requesty serves at most 99 days per request).

1. Go to Settings → SAML.
2. Enter your IdP SSO URL, provide the IdP certificate, and configure attribute mappings.
3. Test the connection to verify.

• Let your team sign in through your identity provider instead of email and password.
• Provision new users automatically on their first SSO sign-in, once their email domain is verified on the workspace.

1. Create a workspace API key under Settings → API Keys — SCIM authenticates with it (no separate SCIM token).
2. In your IdP, set the SCIM base URL to <your Ethira API URL>/v1/scim/v2 and authenticate with HTTP Basic — the key ID as the username and the key secret as the password.
3. Run your IdP's test to verify users provision.

• Automatically create user accounts when people are added to Ethira in your IdP, matched by email.
• Deactivate accounts automatically when users are removed or offboarded in your IdP.

1. Make sure the Connected MCP servers workspace feature is on (admin, under Settings → Workspace features).
2. Go to Settings → Integrations → Agent tools → MCP servers and open the connect dialog.
3. Name the server, choose the transport (Streamable HTTP by default), paste its public HTTPS URL, set authentication, and click Test connection — nothing saves until a test passes.
4. Choose which discovered tools the agents may use — read tools on by default, write tools off — then Save.

• Let Ethira's chat and Slack agents use tools from other products you run — PagerDuty, Sentry, or any MCP server — e.g. "pull the latest incident from PagerDuty and link it to this risk."
• Read tools run on request; write tools are held for explicit confirmation before they run, and every call is written to your Activity Log.

1. Go to Settings → API Keys and create a key.

• Give scripts, the Ethira CLI, and custom integrations programmatic access to your workspace.
• Scope each key to a permission group so it can do only what you allow, and disable it whenever you need to.