> For the complete documentation index, see [llms.txt](https://docs.3q.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3q.video/user-guide-new-ui/modules/ip-geo-blocking.md). # IP/Geo-Blocking
The IP/Geo-Blocking module allows you to restrict or allow access to content based on countries and IP address rules. Profiles can be created as either **allowlists** or **denylists** and can then be used to control where content is accessible from. {% hint style="info" %} IP/Geoblocking profiles are applied through the player configuration. After a profile has been created, it can be selected in the [**Player Management**](/user-guide-new-ui/players.md) and assigned to a specific player configuration. Once assigned, the selected allowlist or denylist controls access for all content played through that player configuration. This allows users to manage access rules centrally in the IP/Geoblocking module and apply them flexibly to different players depending on the required use case, region, or licensing restrictions. {% endhint %} This module is useful when content access must be limited for licensing, regional availability, security, or internal access control reasons. From the IP/Geoblocking module, users can: * View existing geoblocking profiles * Create new allowlist or denylist profiles * Restrict access by country * Restrict access by IP address or IP range * Edit or delete existing profiles * Quickly filter profiles by type or last edited status {% hint style="info" %} The IP/Geoblocking module is available from the main navigation under [**Modules**](/user-guide-new-ui/modules.md). {% endhint %} *** ### Profile Overview The IP/Geoblocking overview displays all configured profiles in a table. Each row represents one profile and includes the most relevant information: * Profile ID * Profile title * Profile type * Selected countries * IP address rules * Creation date * Available profile actions At the top of the page, users can switch between different views: * **All Profiles**\ Shows all existing IP/Geoblocking profiles. * **Allowlists**\ Shows only profiles that allow access for selected countries or IP addresses. * **Denylists**\ Shows only profiles that block access for selected countries or IP addresses. * **Last Edited**\ Sorts or filters profiles by the most recently changed entries. A search field is available to quickly find profiles by title or related information. *** ### Allowlist and Denylist IP/Geoblocking profiles can be created as either an **allowlist** or a **denylist**. #### Allowlist An allowlist grants access only to the selected countries or IP addresses. Users outside the defined countries or IP rules will not be allowed to access the protected content. Use an allowlist when content should only be available in specific regions or for specific networks. Example use cases: * Content licensed only for Germany, Austria, and Switzerland * Internal company streams available only from office IP addresses * Test content available only for selected customer networks #### Denylist A denylist blocks access for the selected countries or IP addresses. Users from all other countries or IP addresses remain allowed unless blocked by another rule. Use a denylist when content should be generally available, except for specific regions or networks. Example use cases: * Blocking access from countries without distribution rights * Preventing access from known unwanted IP ranges * Restricting access for specific external networks *** ### Creating an IP/Geo-Blocking Profile
To create a new profile: 1. Open **Modules** in the main navigation. 2. Select **IP/Geoblocking**. 3. Click **Add Profile**. 4. The **Add Profile** side panel opens. 5. Enter a **Title**. 6. Optionally add a **Description**. 7. Select the profile **Type**: * **Allowlist** * **Denylist** 8. Select one or more **Countries**. 9. Optionally add **IP-Address Rules**. 10. Save the profile. After saving, the profile appears in the overview and can be selected wherever IP/Geoblocking profiles are supported. *** ### Profile Settings #### Title The title is the name of the IP/Geoblocking profile. Choose a clear and descriptive title, especially when multiple regional or customer-specific profiles are used. Example titles: * DACH * No License * Internal Access Only * Europe Allowlist * Blocked Regions #### Description The description field can be used for internal notes or additional context. This field is optional. Useful information can include: * Purpose of the profile * Licensing details * Customer or project reference * Notes about included IP ranges * Internal approval information #### Type The type defines how the selected countries and IP address rules are handled. Available options are: * **Allowlist**\ Only selected countries or IP addresses are allowed. * **Denylist**\ Selected countries or IP addresses are blocked. The selected type should be reviewed carefully before saving, as allowlists and denylists have opposite behavior. #### Countries The countries field allows users to select one or more countries for the profile. The country list includes country names with flags for easier identification. Selected countries are displayed in the profile overview after saving. For example, a DACH allowlist could include: * Austria * Switzerland * Germany A denylist could include a country where no streaming license is available. #### IP-Address Rules IP address rules allow more specific access control based on IP addresses or IP ranges. They can be used in addition to country-based rules. Supported input formats include: ``` 91.242.173.24 91.242.173 91.242 ``` These examples show that rules can be entered with different levels of specificity, from a full IP address to broader IP prefixes. *** ### Editing Existing Profiles Existing profiles can be edited from the overview. Use the action buttons on the right side of a profile row to open or modify a profile. When editing a profile, users can adjust: * Title * Description * Type * Countries * IP address rules Changes to a profile may affect content access immediately wherever the profile is used. Review all country and IP rules carefully before saving changes. *** ### Deleting Profiles Profiles can be deleted from the overview using the delete action. Before deleting a profile, make sure it is no longer used by any active content, player, project, or configuration. Deleting an active profile may affect access restrictions for content that previously relied on it. *** ### Typical Use Cases IP/Geoblocking can be used for different access control workflows, for example: * Restricting videos to licensed countries * Blocking countries where content rights are not available * Allowing access only from selected company networks * Creating regional availability profiles * Separating public and internal access rules * Applying customer-specific geographic restrictions *** ### Notes The IP/Geoblocking module can be booked in **Module Management**. The availability of IP/Geoblocking options may depend on the account configuration and user permissions. IP-based restrictions depend on the detected viewer IP address. Country-based restrictions depend on IP geolocation and may vary depending on the accuracy of the geolocation provider. When using both country rules and IP address rules, review the final access behavior carefully to avoid unintentionally blocking legitimate viewers. --- # 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: ``` GET https://docs.3q.video/user-guide-new-ui/modules/ip-geo-blocking.md?ask= ``` 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.