The assistant says it cannot sign in

Find the words you see below. EstatesBase uses exactly these sentences. Your assistant may show them, or may put them in its own words.

Switched off

AI assistants are switched off for every organisation at the moment.

EstatesBase has paused AI assistants for everyone. Your connections are kept and work again when they return. There is nothing to do but wait.

AI assistants are not available for your organisation.

EstatesBase has not switched AI assistants on for your organisation. Ask your administrator. They ask EstatesBase support.

Your administrator has switched AI assistants off.

Your organisation's policy is off. Ask your administrator.

The policy does not include you

Your role cannot connect an AI assistant here. Ask your administrator if you need to.

Your role is below the lowest role the policy allows, and you are not named in it. Your administrator can add you, or a group you belong to.

Your administrator has not allowed Board members to connect AI assistants.

Trustees may only connect if the policy allows Board members.

Your administrator has not allowed this assistant.

The policy does not allow the assistant you are using. Use one that is allowed. Connected apps lists them under Assistants you can connect.

Who is signing in

An assistant can only be connected by the person themselves.

This browser is in a View as session, where EstatesBase support sees the system as another person. Nobody can connect an assistant for someone else. End View as, or use a browser where you are signed in as yourself.

Sign in to this organisation to connect an assistant.

You are signed in to a different organisation from the one your server address belongs to. Sign out, then sign in to the right one. Check that the server address is the one on your own Connected apps page: https://<your organisation>.estatesbase.com/mcp

The assistant itself

This assistant is not known to EstatesBase, or its access has been withdrawn. Remove it from your assistant and add it again.

Remove EstatesBase from your assistant, then add it again with your server address. If it still happens, your administrator may have revoked the assistant.

The assistant asked to return to an address it has not registered.

Something about the assistant's set up has changed. Remove EstatesBase from your assistant and add it again.

Too many assistants have registered from this address in the last hour.

Wait an hour and try again. If it keeps happening, tell your administrator.

On the consent page

Choose at least one site, or let the assistant see all your sites. Go back and try again.

You chose Only these sites but did not tick any. Go back and tick at least one, or choose All the sites you can see.

After it has connected

This connection has ended. Connect the assistant again to carry on.

Your administrator shortened the longest a connection may last, or the connection waited for approval for more than 7 days. Connect the assistant again.

When a connection is ended in any other way (it reached its end date, or you or your administrator ended it), your assistant is simply no longer signed in. It usually asks you to sign in again, or says it is not authorised. Sign in again to make a new connection, if the policy lets you. Connected apps shows ended connections under Recently ended, with the reason.

Your administrator has not approved this connection yet.

See It says I need approval.

If your assistant shows words such as "invalid, revoked or expired" or "re-authorize", its sign-in has ended. Connect it again. If it says "This sign-in was refreshed a moment ago: use the newest one", wait a few seconds and try again.

Still stuck

• Check your server address on Connected apps under My Profile.
• Sign in to EstatesBase in your browser as usual, to be sure your password, two-factor code or single sign-on are working.
• Ask your administrator to look at the Activity tab for refusals from your connection.