> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide/sites/site-details.md). # Site Details When users navigate to Administration > Site Management > Sites, Verifone Commander Central displays the Site Details page for the selected site. This page consolidates all site-related information and configuration access in one location, and is especially useful for accounts with large numbers of sites where navigating through Administration > Site Management > Sites may be less efficient.

### **Accessing the Site Details** {% stepper %} {% step %} **Log In** Log into the Verifone Commander Central application. {% endstep %} {% step %} **Open Sites** Click Administration > Site Management > Sites. {% endstep %} {% step %} **Find Site** Use the search bar to locate a site by Service ID or Site Name, or scroll through the list. {% endstep %} {% step %} **Open Details** Click on a site to open its Site Details page. {% endstep %} {% endstepper %} {% hint style="info" %} The Administration > Sites path provides the same site data as Administration > Site Management > Sites. Both navigation paths remain available. {% endhint %}

### **Site Details** The Site Details page displays three action buttons and a More menu in the upper-right corner of the screen:

Field/Button	Description
Configuration	Opens the site configuration settings, including Store Operations, Payment Operations, Forecourt, System Settings, Promos & Discounts, and Devices. See the Site Configuration chapter for details.
Reports	Opens site-level reports. See Chapter 9: Reports for details.
Site Assets	Opens the Site Assets report for the site, displaying hardware asset data including serial numbers and dispenser firmware versions.
More > TLog Viewer	Opens the Transaction Log Viewer for the site. See the T-Log Viewer section in Chapter 9: Reports for search functions and download options.
More > Audit Logs	More > Audit Logs Opens the Audit Log for the site, showing a record of configuration changes made to the site. See the Audit Log section below for details.
More > Replicate Config	Opens the Replicate Configuration tool for the site.
More > Device Swap	Opens the Onboarded Device Swap tool, allowing a merchant administrator or authorized VASC technician to replace the site's Commander unit. See the Onboarded Device Swap page for details.
More > Edit Site	Opens the Edit Site form, allowing changes to site details. See the Editing Existing Sites section for details.
More > Re-Assign Site	Opens the Re-Assign Site tool to move the site to a different location in the hierarchy.
More > Delete Site	Permanently deletes the site from the current merchant account. See the Deleting a Site section for details.

#### Site Details Fields The Site Details page displays the following read-only information for the selected site:

Field/Button	Description
Service ID	The Verifone Service ID shown in the site's contract with Verifone.
Site ID	Any ID number used by the organization operating the site.
Site Name	The name of the site.
Connection Status	Displays the current connection status of the site (e.g., ONLINE).
Status Received At	The date and time the current connection status was last received.
Status Description	A description of the site's current status (e.g., ONBOARDED).
Attributes	Custom attributes assigned to the site for filtering and sorting.
Country	The country in which the site is located.

#### Address Details Fields The Address Details section displays the physical address information for the site:

Field/Button	Description
Address Line 1	The street address of the site.
Country	The country in which the site is located.
State	The state in which the site is located.
City	The city in which the site is located.
ZIP Code	The ZIP code for the site.
Phone	The phone number for the site.

### **Hierarchy** The Hierarchy section displays the hierarchy group the site is currently assigned to, with options to expand or collapse the hierarchy tree. To re-assign the site to a different group, select More > Re-Assign Site from the top of the page. ### Audit Log The Audit Log records configuration changes made to a site, showing who made the change and when. Currently, Audit Log scope is limited to configuration changes. #### Accessing the Audit Log {% stepper %} {% step %} **Open Site Details** Navigate to Administration > Sites, then select a site to open its Site Details page. {% endstep %} {% step %} **Open Audit Logs** Select More > Audit Logs. {% endstep %} {% step %} **Search and filter** Use the available filters to narrow results, or select Download Report to export the current results as a report.

#### Filters


Filter	Description
Service ID	Search by a specific site's Service ID.
Date Range	Limit results to a specific date range.
Configuration	Filter by the configuration area affected by the change.
Hierarchy	Filter by the site's position in the business hierarchy.
Add filter	Add additional filter criteria.
Clear filters	Reset all applied filters back to the default view.

{% endstep %} {% step %} **View Details** Select an entry's row to open Audit Log Details for that change.

{% endstep %} {% endstepper %} #### Audit Log List Each row in the Audit Log list shows:

Column	Description
Company Name	The company associated with the change.
User Email	The email address of the user who made the change.
Operation	The type of change made (for example, EntityCreated).
Configuration	The configuration area or dataset affected by the change.
Timestamp	The date and time the change occurred.

Select Download Report to export the currently filtered list. #### Audit Log Details Selecting an entry opens Audit Log Details for that change, showing: • The operation and configuration area affected, with a status indicator (for example, Success). • Timestamp of the change. • User Details: User Email, Roles, Account Admin, and Account Company. • Target Site: Service ID, Merchant, and Branded Oil. #### Change details for sensitive configuration For Fuel Prices, Tax Rates, and Fees, the Audit Log captures the full before-and-after values when a change is made, not just the fact that a change occurred. This change detail is visible to Merchant/Site Owner, VASC, and Verifone Internal users. It is not visible to Major Oil users. #### Who can see what

Entity	Access
Merchant / Site Owner	Full, unfiltered Audit Log for their own sites, including actions taken by any other entity.
VASC	Full, unfiltered Audit Log for sites they are authorized to manage.
Verifone Internal (Support)	Read-only access across their support scope; ESG can query across all entities and sites. No ticket number is required to view a log.
Major Oil	No access by default. Access can be enabled by a Verifone Internal administrator based on a contractual agreement with the merchant.

An entity admin can grant or revoke Audit Log access for their own sub-users; by default this is configurable per sub-user. #### Data retention Audit Log entries are retained for 180 days by default. Verifone can configure a different retention period for a specific merchant, or a specific merchant and Major Oil combination, as a premium offering. --- # 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://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide/sites/site-details.md?ask=&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.