The question this page answers
Do I let this AI agent into my Tightly account, as whom, into which organisation, reaching how far, for how long? An AI agent, Claude in a desktop or a connected client, arrives here when it asks to connect to Tightly. This page is where you grant it, and nothing is granted until you press.
What you see
The title is
Connect an AI agent
signed in or out. Signed out, the sentence is
Sign in to let an AI agent read your Tightly account.
with the agent's own name in place of "an AI agent" where it gave one, over the sign-in form, two steps as on Sign in, with no provider doors and no Forgot password door, because either would leave the request behind and let it lapse. Signed in, the sentence names who wants what:
{agent} wants to read Tightly as {email}.
or, with Read and act chosen, {agent} wants to read and act as {email}; an agent that gave no name reads An AI agent. Below it the facts and the choices: Organisation, a pick of the organisations your account holds; Reach, Read or Read and act, shown only where the agent asked to act and your organisation allows it (where the organisation withholds acting, its own sentence stands in the control's place); Read and act carries its consequence before the button,
It asks you before every act, and never signs off, releases or closes a commitment.
Access reads "24 hours at a time, renewed for up to 30 days". What it can read is one list of four: products, variants and stock levels; purchase orders and suppliers; sales and the dashboard; replenishment recommendations. A record line reads
Every call is kept for 90 days, never what it read, and Tightly trains no model on your data.
Then Cancel, with its consequence,
Nothing is granted; it lapses in 10 minutes.
and Authorize.
What to do
- Check Organisation names the one you mean to grant into.
- Choose Reach, Read or Read and act, where the control is offered.
- Press Authorize; the page leaves for the agent, which now holds a grant under your seat and your organisation.
- Or press Cancel to close the tab or open Home and tell the agent nothing; the request lapses on its own.
A read-only seat's agent reads; an agent with Read and act may propose the acts your seat may take, and asks before every one. Authorization is asked for once per request; the agent asks again when its grant runs out. The agents you have let in, and the door that ends one, stand on Profile.
When it is empty or failed
Not a valid request from an AI agent; start again there.
The request was incomplete; go back to the agent and start again.
A request the agent side refused prints its served sentence, then Go back to the agent and start again:
Invalid or expired authorization request.
An account that holds no organisation cannot authorise, and Authorize's reason stands beside it: "Tightly Connect seats cannot connect an AI agent yet.", or, where the account could not be read, "An agent reads one organisation, and this account holds none." An organisation that keeps an approved list of agents names its refusal there too, and a policy Tightly could not read reads "Tightly could not confirm your organisation's agent policy. Try again in a moment." A sign-in the page could not complete reads "Tightly could not sign you in; try again." A session that lapses on the page returns it to the sign-in state.