Skip to content

Share your apps with the team, not your logins

Connect an app once and share it with one person or a whole team. They use it from their own AI, and nobody you share with ever sees the login.

  • Free 14-day trial
  • No credit card
  • Free plan for one person
Claude Elaichi connected

Summarize ticket #4821 and draft a reply.

JM

Using the Support team’s toolbox

  • Read ticket #4821 and its history
  • Found 2 similar tickets solved last month
  • Drafted a reply on the ticket
  • Delete tickets Not in this toolbox

The customer can’t sign in since their SSO change. Your draft on the ticket walks them through the fix that solved the last two.

Three teams, one shared app each

Each person works from a connection someone else set up, and never holds the login.

EC SalesEmily Carter

“Log my call with Acme Corp and set a follow-up for Tuesday.”

ChatGPT
Found Acme Corp in Salesforce
Logged the call and a follow-up task
Delete recordsNot in this toolbox

One Salesforce connection for the sales team

The sales lead keeps Salesforce private and shares a toolbox with the read and call-logging tools. Emily and the rest of the team run it from ChatGPT or Claude, and the login stays on the lead’s connection.

Uses Salesforce

TR OperationsTyler Reed

“Which invoices from last month are still unpaid?”

ChatGPT
Searched last month’s invoices in QuickBooks
Found 7 that are still open
Create or edit invoicesRead-only toolbox

Read-only books for operations

The finance lead keeps QuickBooks private and shares a toolbox of read-only tools with operations. Tyler gets answers from the books, and every tool he can reach only reads.

Uses QuickBooks

AP MarketingAshley Parker

“How many new HubSpot contacts came from the webinar?”

Claude
Searched contacts in HubSpot
Counted 214 from the webinar form

One HubSpot connection for the whole team

The marketing lead shares the HubSpot connection with the team at use. Everyone works from that one connection, and calls run on the lead’s account.

Uses HubSpot

Share what the app can do. Keep the login.

How teams share apps without Elaichi

  • A password or API key gets pasted into a chat or a shared doc.
  • Or everyone connects the same app on their own, one person at a time.
  • Either way, it’s hard to see who can reach what, or to take it back.

With Elaichi

  • Connect the app once. The login is stored encrypted, and nobody you share with ever sees it.
  • Share it with a person, a team or the whole company, at view, use or edit.
  • Calls run on the owner’s account, and each call that runs is logged with the person who made it.
  • Want to share less? Keep the connection private and share a toolbox with just the tools they need.
  • Take it back any time. Removing a share stops it on their next request.

Set it up in four steps

In the order an admin takes them.

  1. 1

    Connect the app

    Pick it from the catalog and sign in. The login is stored encrypted in Elaichi, and the connection is yours.

  2. 2

    Choose what to share

    Share the whole connection, or keep it private and build a toolbox with just the tools the team needs. Lock any value that must not change.

  3. 3

    Pick who gets it

    Give a person, a team or the whole company view, use or edit. Use is enough to run the tools.

  4. 4

    They use it from any AI app

    Teammates sign in to Elaichi from their own AI app, and the shared tools are there. Remove a share and it stops on their next request.

For IT and engineering

In Elaichi, one person connects an account and shares what it can do, not the login behind it. They share the connection itself with a person, a team or the whole organization at view, use or edit, or keep it private and share a toolbox over it instead. The login is stored encrypted. Elaichi decrypts it to make each call and never returns it through the API, to a person or to a model. Each person sees only what they own or what was shared with them.

Details that matter

  • Calls run on the owner’s account. A shared connection reaches the app as the account that connected it. Elaichi logs which person made each call that runs and which account it reached.

  • Locked values follow the toolbox. Locked (frozen) values hold for everyone who runs the tool through the toolbox. Anyone you also give use on the connection itself can call the tool without them, which is why a lock-down keeps the connection private.

  • You see what you own or were given. A member sees only what they own or what was shared with them. No organization-level permission widens that, owners and admins included.

  • The sign-in link is not the key. A connect link opens a one-time sign-in session and carries no token or secret, which is why an AI can safely hand one to a person.

Three ways to give a team access

Aspect A shared password or key Everyone connects their own Sharing in Elaichi
What teammates get The login, with everything it can do Their own account in the app Only the tools you share
Setup Once, then passed around Each person signs in, in each AI app Once, by the owner
Locking it down Only what the key allows Each app’s own permissions A toolbox with locked values over a private connection
Who did what Calls show as the key’s owner In each app’s own records Each call that runs, logged with the person who made it
Taking it back Change the key and share it again Remove each person’s access, app by app Remove the share; it stops on the next request
When the owner leaves Change the key Close their accounts app by app Hand the connection to someone staying as you remove them

Questions, answered

Can a teammate see the login behind an app I share?

No. The login is stored encrypted, and the API never returns it to a person or to a model. Teammates call the app through your connection without the secret reaching them.

Whose account does the app see when a teammate uses my connection?

The account that connected it. A shared connection runs on that account’s login, so the app sees its owner. Elaichi still logs which person made each call that runs and which account it reached.

How do I give a teammate read-only access?

Keep the connection private and share a toolbox that holds only read tools. Sharing the connection itself would give them every tool it has.

Can I share with a whole team at once?

Yes. Share with a person, a team or the whole organization, at view, use or edit. Use is enough to run tools, and edit lets someone change the toolbox.

How fast can I take shared access back?

Removing a share or disconnecting the account takes effect on the very next request. Access that comes through a role, a restriction or a team changes within about two minutes.

Can’t teammates just connect their own accounts in Claude or ChatGPT?

They can. Each of them then holds their own access to the app and signs in again in every AI app they use. Sharing through Elaichi means one connection, set up once, that the team uses from any AI app, narrowed to what you choose.

Does an admin automatically see everything that has been shared?

No. A member, including an owner or admin, sees only what they own or what has been shared with them. There is no organization-wide list that widens that.

What happens to a shared connection when its owner leaves?

When an admin removes them, Elaichi first asks for a decision on what others rely on. A private connection that a shared toolbox uses must be transferred or deleted before the removal goes through. A shared connection stays in place unless you transfer or delete it, and no one can hand it over afterward, so decide during the removal. Toolbox entries the person set up need a re-pin.

Does everyone who uses a shared toolbox need a paid seat?

Anyone who runs tools needs a role that can, which is a paid seat such as Member. People who only review activity can use the free Auditor role, which can’t run tools.

Share one app with one teammate

Start a trial, connect an app, and share a toolbox over it with a colleague.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot