> 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/command-centre-client/using-command-centre/licensable-features/uk-govpass-card-support/uk-govpass-cards-in-command-centre/card-activation-and-expiry.md).

# Card Activation and Expiry

### 'From' date and card activation

When the **From** date is set to a future date, the Command Centre **Status** changes to 'Not Yet Activated', but there will be no change to the card status or the enrolment status on the GovPass REST API.

![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-17155328f84f117e74e25a161202e1805acbe357%2Fcardactivation_notyetactivated.png?alt=media)

When the system date passes the **From** date, the GovPass card **Status** becomes 'Active' in Command Centre, and the card status on the API updates to 'Active' and the enrolment status to 'Enrolled'. Also, an update enrolment status is sent to the API from the remote servers to 'Enrolled' state.

### 'Until' date and card expiry

When the **Until** date is set to expire in the future, the Command Centre **Status** will still be 'Active'. There will be no card status and enrolment status update on the GovPass REST API.

![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-965677ec6698416e6990113bbf645a13fdfc2cf1%2Fcardactivation_expired.png?alt=media)

When the system date passes the **Until** date, the card **Status** updates to 'Expired' in Command Centre and there is no change to the card status on the API, but the enrolment status updates to 'Suspended'. Also, an update enrolment status is sent to the API from the remote servers to 'Suspended' state.


---

# 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/command-centre-client/using-command-centre/licensable-features/uk-govpass-card-support/uk-govpass-cards-in-command-centre/card-activation-and-expiry.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.
