> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-p-2.md).

# Printing - Windows User Accounts

[Command Centre - Connection Issues](/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues.md) › Printing - Windows User Accounts

Almost every Command Centre printing problem comes down to **which account is being used and whether that account has print permission.**

## Which account prints?

| Print type                          | Account used                                               | What it needs                                              |
| ----------------------------------- | ---------------------------------------------------------- | ---------------------------------------------------------- |
| **Workstation print** (interactive) | The Windows user account the operator is logged in with    | That Windows user must have print access to the printer    |
| **Scheduled or Macro-driven print** | The Windows account the **Command Centre Service** runs as | That service account must have print access to the printer |

A workstation **on the server** still uses the account the user is logged into Windows with to connect to the printer.

## Diagnosing a printing failure

If the user account for any situation does not have authorisation to print, you will run into printing issues.

**Simplest test:** log into the Windows machine doing the printing with the Windows user account being tested, and see if that machine can print anything on the printer (for example, a test print). If it cannot, that must be resolved first. It is a Windows / printer permission problem, not a Command Centre one.

## Network printing (interactive)

If you have trouble printing a report through a **networked** printer, the Windows user logged into the workstation must have access to print to the printer.

***

🔗 **Related**

* [Printing - Macros or Scheduled Printing not working](/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-print.md). Printing that runs under the Command Centre Service account.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-p-2.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.