> For the complete documentation index, see [llms.txt](https://help.jurisphere.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jurisphere.ai/jurisphere-word-add-in/help-section/errors-and-faqs/log-in-duration.md).
# Log In Duration
Do I need to sign in again every time I open Word?
Do I need to sign in again every time I open Word?\
No. Once you've signed in on a given device, the Add-In generally keeps you signed in across Word sessions on that device — you shouldn't need to re-enter your email and code every time you open a document. You'll only be prompted again if you've explicitly signed out, your session has been inactive for a very long time, or you're setting up the Add-In on a **different** device for the first time (sign-in, like installation, is per-device — see [Installing the Word Add-In](https://claude.ai/cowork/cse_019A8QdUyX6GKXxDLJs3SeuB#) for how installation itself works across devices).
\ \ \What if my connection drops mid-task, or a request suddenly starts failing?\
The Add-In is designed to reconnect automatically if your connection drops mid-conversation, refreshing your session token in the background rather than logging you out. If you do run into a request that fails outright (for example, a "Request failed" or "Something went wrong, please try again" message), the most common causes are a genuinely dropped connection or, less commonly, a stale session — try the query again first, and if it keeps failing, sign out and back in once before contacting support.
{% hint style="info" %} If requests fail specifically on a **corporate network**, ask your IT team to confirm that outbound traffic to Jurisphere's domains (including `api.jurisphere.ai`) isn't being blocked by a firewall or proxy — this is the same category of issue documented for file uploads in [Upload Failed While Uploading File](https://claude.ai/cowork/cse_019A8QdUyX6GKXxDLJs3SeuB#), and it can affect the Add-In's connection just as easily. {% endhint %}
\ \ \I signed in but the panel is blank, or shows a spinner that never resolves\
This is almost always one of the following:
1. **A slow or interrupted connection** during the sign-in handshake — close and reopen the panel, then try again.
2. **A corporate firewall or proxy** blocking the connection — see the note above.
3. **A genuinely stale add-in session** — try Word on the web as a quick test; if sign-in works there but not on your desktop install, the issue is local to that device rather than your account.
If none of these resolve it, contact support with your organization's email domain and a screenshot of exactly what you're seeing.
\ \ \I signed in but everything looks empty — no Skills, no history, nothing familiar\
This is almost always the wrong-email issue flagged in the warning near the top of this page: you've successfully signed in, just to the **wrong account** (a personal email instead of your licensed work email, for example). Sign out, confirm the exact email address tied to your Jurisphere license with your admin if you're not sure, and sign back in with that one.
\ \ \I clicked Sign In and nothing happens at all\
If the button itself appears unresponsive:
1. Confirm you have an active internet connection.
2. Close and reopen the Jurisphere panel (or restart Word) and try again — this resolves the majority of cases.
3. Try Word on the web as a quick isolation test.
4. If it still doesn't respond, this may be a device- or network-specific issue rather than an account issue — contact support with details of your Word version and platform (Windows, Mac, or web).
\ \ \Google sign-in showed a Bluetooth or passkey error — is my device broken?\
No — this is a known, tracked limitation, not a hardware or account problem. It happens when Google's own sign-in flow tries to fall back to a passkey/cross-device verification step that the embedded browser inside Word's desktop Add-In cannot complete. If you land here:
1. On that Google screen, look for a **"Try another way"** option and choose a password-based method instead of the passkey/Bluetooth prompt — this sometimes gets you through.
2. If that doesn't work, close the Google window and sign in with **email + verification code** instead — this is the documented, reliable path and never touches Google's flow at all.
3. Alternatively, use **Word on the web**, where Google sign-in runs in a real browser and this issue doesn't occur.
Do not reinstall the Add-In — this is unrelated to installation.
\ \ \Does signing in to the Word Add-In use a different license from the web platform?\
No — it's the same account, the same license, and the same seat. There's no separate Word Add-In subscription to activate. See [Installing the Word Add-In](https://claude.ai/cowork/cse_019A8QdUyX6GKXxDLJs3SeuB#) for how installation (as distinct from signing in) works, including for organization-wide, IT-managed rollouts.
\ \ \My organization deployed the Add-In centrally — do I still need to do anything?\
Yes, one thing: signing in. Centralized (admin-managed) deployment through the Microsoft 365 admin center makes the Add-In **available** in everyone's Word ribbon automatically, but it doesn't sign anyone in — each person still needs to complete the sign-in steps on this page individually, once per device, using their own Jurisphere account email.
\
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.jurisphere.ai/jurisphere-word-add-in/help-section/errors-and-faqs/log-in-duration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.