# Geo Fencing Report

<figure><img src="/files/PaLauzcWHUTUL9nGhN43" alt=""><figcaption></figcaption></figure>

**1. Introduction**

* **Purpose:** The Geo-Fencing Report is a tool for administrators to monitor and analyze Geo-Fencing activity, specifically successes ("Allowed") and failures ("Restricted") based on users' locations. It helps track whether users are accessing applications or systems from within authorized geographic boundaries.
* **Key Features:**
  * **Track Geo-Fence Activity:** Monitor both successful and unsuccessful attempts to access resources based on location.
  * **Identify Policy Violations:** Easily spot instances where users are attempting access from outside the defined geo-fence.
  * **Detailed Reporting:** Filter and view reports based on various criteria, including user, application (flow), and date range.

**2. Using the Search Filters**

The report includes the following search filters to help you find the information you need:

* **Email:** Enter the email address of a user to view their geo-fencing activity. The system provides suggestions as you type. Select an email from the dropdown to refine your search.
* **Flow Name:** Select one or more "flows" (systems or applications) from the dropdown list. A "flow" represents a specific application or system protected by geo-fencing.
* **Status:** Select the status of the access attempt: "Allowed" or "Restricted." This filter allows you to focus on successful accesses (within the geo-fence) or failures (outside the geo-fence).
* **Start Date & End Date:** Define a date range to view geo-fencing activity within a specific time period.
* **Search Button:** Click the "Search" button to generate the report based on your selected filters.

**3. Understanding the Report Table**

The generated report displays a table with the following columns:

* **S.No:** The sequential number of the entry in the table.
* **Name:** The name of the user whose activity is being reported.
* **Email:** The email address of the user.
* **Flow Name:** The name of the system or application (flow) being accessed.
* **Restriction Type:** The type of geo-fencing restriction in place. (e.g., Common)
* **Coordinates (Longitude / Latitude):** The geographic coordinates (longitude and latitude) from which the user attempted to access the system. Clicking the coordinates will open a map showing the location.
* **Status:** Indicates whether the user's access was "Allowed" (within the geo-fence) or "Restricted" (outside the geo-fence). The table highlights rows with a status of "Restricted" for easier identification.
* **Redirect (View Config):** A button that allows you to navigate to the configuration settings related to the geo-fencing restriction for that specific user and flow.

**4. Viewing Location on a Map**

To view the user's location on a map:

1. Locate the row in the table corresponding to the activity you want to investigate.
2. Click on the coordinates (Longitude / Latitude) in the "Coordinates" column.
3. A modal window will appear, displaying the location on a map.

**5. Navigating the Report**

* **Pagination:** If the report spans multiple pages, use the "Previous" and "Next" buttons at the bottom of the table to navigate.

**6. Viewing Configuration Details**

To view the geo-fencing configuration details:

1. Locate the row in the table for the event you're interested in.
2. Click the "View Config" button in the "Redirect" column.
3. You'll be taken to the geo-fencing restriction settings page for that user and flow.


---

# Agent Instructions: 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:

```
GET https://authdocs.skill-mine.com/licentio-documentation/report/geo-fencing-report.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.