Google is currently completing its security review of Binee, and until that review finishes, Google shows a standard notice during connection saying the app has not been verified yet. Google shows this screen to every app while its review is in progress; it does not mean anything is wrong. It is safe to continue: on the warning screen, click Advanced, then Go to binee.io, then allow access on the permissions screen that follows. Binee's Google access is read only, and each member connects their own account, so only you grant and control your own access. The warning disappears for everyone once Google's review completes.

This only happens with company (work) Microsoft accounts; personal Microsoft accounts like outlook.com or hotmail.com connect directly and never need an approval. Some companies configure Microsoft so that new apps need a one-time approval by the company's Microsoft admin before anyone can connect. If Microsoft blocks your connection with that message, open the Microsoft 365 card in Settings, then Integrations: it shows a Copy link for your admin button. Send that link to your Microsoft admin; it works without a Binee account, and approving connects nothing by itself, it only unlocks the door. Once the admin approves, everyone in the workspace connects their own Microsoft account as usual, and the card changes to say the admin has approved Binee. If you are the Microsoft admin yourself, just press Connect: you can approve for the company and connect your own account in one step.

Tool authorizations can expire (for example, Google grants for apps in pre-verification expire weekly). Open Settings, then Integrations, and press Reconnect on the card. Reconnecting re-runs the same sign-in you did the first time and restores access immediately. Your settings and history are unaffected.

Status unavailable means Binee could not check that connection's status just now, and it reports that honestly instead of guessing Connected or Not connected. It is usually temporary: reload the page or check again in a minute. If it persists, contact support from Settings, then Help & support.

Live updates on the ClickUp card reports whether ClickUp is pushing change events to Binee, and it only shows Active when events are actually arriving.

Binee detects your ClickUp plan automatically when ClickUp connects, so the card usually fills itself in. Not detected yet means detection has not run for this team, which happens on workspaces connected before automatic detection existed or when ClickUp did not answer the plan lookup during connect. Reconnecting ClickUp runs the detection again. Until then nothing is broken: Binee simply assumes the most conservative request rate when talking to ClickUp.

Your ClickUp dashboard cards work their numbers out with your own ClickUp connection, and the latest update did not finish; the card says why, and the cards keep showing the previous numbers with their time stamp. Press Refresh data on the ClickUp card to try again. If the reason mentions your connection, reconnect ClickUp from Settings, then Integrations. A very large workspace can also take a few minutes: the card then says Updating, and it finishes on its own.

Binee reads ClickUp live, with your own ClickUp access, and ClickUp does not share a task's change history (who changed what, and the before and after values) through its API. Binee tells you so instead of guessing. What it can show you is real: the tasks that changed or were finished in a period with their current state, the comments on a task, and how long a task sat in each status. For example, "what did Maria finish this week?" lists the tasks Maria completed this week, and "how long did the Hoffman intake task sit in review?" answers from ClickUp's time in status (that one needs ClickUp's Total time in Status ClickApp switched on).

ClickUp's API has no text search and returns tasks 100 at a time, so for a broad question Binee reads the most recently updated tasks and says so, for example "covered the 500 most recently updated tasks, counts are at least". Nothing is broken. Naming a person, a list, a space, or a date range narrows the read so older tasks are reached, for example "find the Hoffman settlement task in the Litigation space". Counts Binee gives as "at least" are lower bounds, never totals.

ClickUp only lets workspace owners and admins read other members' time entries. When someone else asks for the team's hours, Binee shows that person's own time and says so. An owner or admin asking the same question gets everyone's time.

Email and password signups need to be confirmed: after signing up you see a Check your email screen, and clicking the link in that email activates your account. If the email has not arrived within a few minutes, check your spam folder. The signup screen also lets you switch to a different email address.

Connections are per person: Binee only queries a tool through your own connection. Connect your own account from Settings, then Integrations.

Both live in the bar at the top of the app. The notification bell sits on the right, next to the Binee Assistant button and the help icon; the bell carries your insights and any Binee automation waiting for your approval. Your workspace lives in the account menu at the far right (your photo, with the workspace name beside it on larger screens): open it to switch workspaces, see your credits and plan, reach Settings, or, for owners and admins, invite teammates. On larger screens your live credit balance also shows directly in the bar; on a phone it lives inside the account menu.

That is how workspaces work: each one is fully separate, with its own chats, automations, insights, and connections. Switch back from the account menu at the top right and everything is where you left it.

Two usual reasons: it is still waiting for their approval on their Automations page, or their connection for one of its sources expired. Their automation's row on your Automations page shows which, with the reason spelled out; the Filters button narrows the list to "Needs attention".

Check these in order:

If the workspace is out of credits, chat pauses with an honest message until credits renew or are added (Settings, then Billing & Usage). If a single reply failed, the error is shown in the conversation; sending the message again is safe.

Contact the team from Settings, then Help & support: pick a topic, describe what happened and what you expected instead, and replies go to your account email.