Odoo Looker Studio Connector

$ 196.22

v 19.0 Third Party

Availability	Odoo Online Odoo.sh On Premise
Odoo Apps Dependencies	• CRM (crm) • Contacts (contacts) • Calendar (calendar) • Discuss (mail)
Lines of code	2504
Technical Name	`eb_looker_connector`
License	OPL-1
Website	https://www.echobitzit.com
Versions	15.0 16.0 17.0 18.0 19.0

You bought this module and need support? Click here!

Availability	Odoo Online Odoo.sh On Premise
Odoo Apps Dependencies	• CRM (crm) • Contacts (contacts) • Calendar (calendar) • Discuss (mail)
Lines of code	2504
Technical Name	`eb_looker_connector`
License	OPL-1
Website	https://www.echobitzit.com
Versions	15.0 16.0 17.0 18.0 19.0

Description
License

Odoo Looker Studio
Connector

Odoo Looker Studio Connector bridges your Odoo instance directly with Google Looker Studio - no CSV exports, no middleware, no manual data pipelines. Connect any Odoo model and build live business dashboards with token-based authentication, custom field selection, domain filtering, pagination, real-time request logging, and full Odoo security respected at every layer.

Why Teams Choose Looker Studio Connector

Live Odoo data in Looker Studio - no exports

Connect any Odoo model directly to Google Looker Studio via a secure REST API. Dashboards always reflect your real business data without manual CSV exports or middleware.

Full control over what data is shared

Choose exactly which fields and records get exposed using per-model configurations, visual domain filters, field toggles, and per-token model restrictions.

Enterprise security with zero friction

SHA-256 hashed API tokens, optional expiry dates, per-user Odoo access rights, and a full audit log keep everything secure and auditable from day one.

Business Value It Delivers

Zero export overhead - always live data

Eliminate manual CSV exports and scheduled data syncs entirely. Every Looker Studio chart reads directly from your live Odoo database via the REST API - so your dashboards are always accurate, even when records change by the minute.

Faster decisions across every department

Sales, Finance, Procurement, HR, and Operations teams all get polished, interactive Looker Studio dashboards from their Odoo data - without depending on a developer each time they need a new report or insight.

One connector for every Odoo model you have

From crm.lead and sale.order to account.move, hr.employee, stock.quant, and any custom model - a single installation unlocks your entire Odoo database as a Looker Studio data source, with no extra configuration per module.

Live Looker Dashboards

Stream real-time Odoo records directly into Looker Studio - no exports, no scheduled syncs.

Secure Token Authentication

SHA-256 hashed API tokens with optional expiry and per-user Odoo access rights.

Custom Field & Model Config

Select exactly which fields and models are exposed with per-record domain filtering.

Full Audit & Request Log

Every API call is logged with token, endpoint, duration, record count, and IP address.

Quick Setup - 3 Steps

Connect Odoo to Looker Studio in Minutes

Generate a secure API token inside Odoo, configure which models and fields to expose, then paste your connector URL into Google Looker Studio. Your live Odoo data will be available as a data source instantly - no coding required.

Watch Video Playlist

See all major Odoo Looker Studio Connector features and workflows in one place.

What is Odoo Looker Studio Connector?

Odoo Looker Studio Connector is a native Odoo 19 module that exposes your Odoo data through a secure REST API at /looker/api/, enabling Google Looker Studio to connect directly to any Odoo model as a live data source. No middleware, no third-party services, no data exports - just a clean, token-authenticated connection between your ERP and your dashboards.

It is also the control layer for what data gets shared. Per-model configurations, field-level toggles, visual domain builders, max-record caps, and per-token model restrictions give admins full visibility and governance over exactly what Looker Studio can see - while a built-in request log tracks every API call with timing, record count, and IP address.

Secure REST API

Exposes Odoo models via /looker/api/ with Bearer token auth, CORS support, and full JSON responses.

Per-Model Configuration

Visual domain builder, field selector, max-records cap, and live record count - all configurable per model.

Token-Based Security

SHA-256 hashed tokens with optional expiry, model restrictions, and per-user Odoo access rights enforced on every call.

Automated Maintenance

Two daily cron jobs automatically clean up expired tokens and purge request logs older than 30 days.

Key Features

Everything you need to connect Odoo data to Google Looker Studio securely

Token-Based Authentication

Secure & cryptographically strong

API tokens are generated using Python's secrets.token_urlsafe(48) and stored as SHA-256 hashes - the raw token is never persisted after first display. Each token is linked to a specific Odoo user, so all data fetched respects that user's access rights. Tokens support optional expiry dates and are auto-deactivated by a daily cron job.

3 Ways to Pass Token

Send via

Authorization:
                                        Bearer

, custom X-Looker-Token header, or ?token= query param - all supported seamlessly.

Model-Level Restrictions

Each token can be restricted to specific Odoo models. Any request to an unauthorised model returns a clear 403 Forbidden response.

Per-Model Configuration

Configure each Odoo model independently: set a visual domain filter, choose a max-record cap (default 75,000), and see a live record-count preview - all from one Odoo form.

Domain JSON Ready

The computed Domain JSON field converts Odoo's internal tuple format to clean JSON - just copy and paste it into Looker Studio's filter field.

One Active Config Per Model

A hard database constraint prevents duplicate active configs for the same model, avoiding accidental conflicts.

Per-Field Configuration

Toggle individual fields on/off, rename display labels, override Looker data types (TEXT, NUMBER, BOOLEAN, Date, Currency, Percent) and set each as DIMENSION or METRIC.

Smart Data Type Mapping

All Odoo field types map automatically to Looker Studio types - monetary → NUMBER METRIC, date → YEAR_MONTH_DAY, many2one → TEXT label - with no manual setup required.

9 REST API Endpoints

Complete API coverage: /info, /validate, /models, /schema, /data, /fields, /search, /count, plus CORS OPTIONS preflight for browser-based Looker connectors.

Domain Filtering & Pagination

Config and runtime domains merge automatically. Pagination via limit/offset with a has_more flag supports large datasets up to 75,000 records.

Advanced Search & Group By

The /search endpoint supports group_by via Odoo's read_group, enabling aggregated metrics and grouped analytics directly in Looker Studio.

Full Request Audit Log

Every API call is logged: endpoint, method, token, model, response code, record count, duration (ms), IP address, and error messages. Auto-purged after 30 days.

Automated Cron Jobs

Two daily scheduled jobs run automatically: one deactivates expired tokens, another purges request logs older than 30 days - zero maintenance required.

CORS & Browser Connector Support

Full

Access-Control-Allow-Origin:
                                *

headers on every response plus dedicated OPTIONS preflight handlers ensure compatibility with Looker Studio's browser-based community connector.

Smart Data Serialization

many2one values become label strings, many2many becomes count, dates become ISO 8601, and False becomes null - all data is Looker Studio ready out of the box.

Connect Looker Studio to Odoo

Follow these steps to set up your first live Odoo data source in Google Looker Studio.

1 Generate an API Token in Odoo

Go to Looker Studio → API Tokens in Odoo
Click New and give your token a name
Select the Odoo user whose access rights will apply
Optionally set an Expiry Date and restrict to specific models
Click Generate Token - copy the token immediately
Note your Connector URL shown on the token form: https://your-odoo.com/looker/api

2 Configure Your Model & Fields

Go to Looker Studio → Model Configurations
Click New and select your token and Odoo model (e.g. crm.lead)
Use the Domain Builder to filter which records are exposed
Set a Max Records cap (default 75,000)
Click Sync Fields to import all available fields
Toggle fields on/off, rename labels, and set DIMENSION or METRIC per field

3 Validate Your Token

Send a quick GET request to verify the connection:
GET /looker/api/validate
Pass your token as Authorization: Bearer <token>
A successful response returns "valid": true with user name and token name
Or browse to /looker/api/info to confirm the API is reachable - no auth required

4 Connect from Google Looker Studio

Open Google Looker Studio → Create → Data Source
Search for and select the Odoo Looker Studio Connector
Enter your Connector URL: https://your-odoo.com/looker/api
Paste your API Token in the token field
Select your Odoo Model from the dropdown
Click Connect - your live Odoo fields appear ready to chart

💡 Pass a Domain Filter at Runtime

You can send a filter domain directly from Looker Studio alongside the model request. Use the Domain JSON field from your model config - it is already formatted in the correct JSON array structure.


                        domain=[["stage_id.name","=","Won"]]

                        limit=5000&offset=0&order=date_deadline asc

🔧 Testing Locally with ngrok

If your Odoo instance is running locally (port 8069), expose it over HTTPS so Looker Studio can reach it:


                        ngrok http 8069

Set the ngrok URL as web.base.url in Odoo System Parameters, and set web.base.url.freeze to True to prevent Odoo from overriding it.

How It Works

From installation to live Looker Studio dashboards in four simple steps

Install the Module

Install the app in your Odoo 19 instance - no middleware, no external service required.

Generate a Token & Configure Models

Create a secure API token, select which Odoo models and fields to expose, and apply domain filters.

Connect from Looker Studio

Paste your connector URL and token into the Looker Studio Community Connector - your Odoo fields are ready instantly.

Build Live Dashboards

Drag & drop fields into charts, tables, and scorecards in Looker Studio - all powered by live Odoo data.

Feature Deep Dive

Explore every capability of the Odoo Looker Studio Connector in detail

Prerequisites

✅ Odoo Version

Odoo 15+ (Community or Enterprise). The module uses only built-in Odoo framework - no external libraries required.

✅ Public HTTPS URL

Looker Studio requires HTTPS. Your Odoo must be reachable over HTTPS. For local dev, use

ngrok
                                                http 8069

✅ Admin Access

You need Odoo Administrator rights to install the module and create API tokens & model configurations.

Install the Module

Go to Odoo → Apps and search for Looker Studio Connector
Click Install - no dependencies, no pip packages needed
After installation, a new menu Looker Studio appears in the main Odoo menu bar
The menu contains: API Tokens, Model Configurations, and Request Logs

Generate an API Token

Steps

Go to Looker Studio → API Tokens
Click New and give the token a name (e.g. Sales Dashboard Token)
Select the Odoo User whose access rights will apply to all queries
Optionally set an Expiry Date
Optionally restrict the token to specific Allowed Models
Click Generate Token - copy the token immediately (shown only once)
Note the Connector URL displayed on the form

Token Fields Reference

Name - friendly label for the token

User - Odoo user whose record rules apply

Expiry Date - optional; auto-deactivated at midnight

Allowed Models - leave blank to allow all models the user can read

Token Hash - SHA-256 hash stored, never the raw value

Last Used / Total Requests - auto-tracked per call

Connector URL - your Odoo base URL + /looker/api

Configure a Model

Go to Looker Studio → Model Configurations and click New
Select the Token this config will be linked to
Select the Odoo Model you want to expose (e.g. crm.lead, sale.order)
Use the Domain Builder to add filters - e.g. only won opportunities, only confirmed orders
Set the Max Records cap (default: 75,000 - the Looker Studio connector limit)
Check the Record Count field to preview how many records match your domain
Click Save - one active config per model is enforced by a database constraint

Configure Fields

Steps

Open your Model Configuration record
Click Sync Fields - all Odoo fields for the model are imported automatically
In the Field Configuration tab, toggle the Selected checkbox to include/exclude fields
Edit Display Label to rename fields for business users
Override Looker Data Type: TEXT, NUMBER, BOOLEAN, Date, DateTime, Percent, Currency
Set Concept Type to DIMENSION or METRIC for each field
Only Selected fields appear in Looker Studio schema & data responses

Auto Type Mapping (on Sync)

char, text → TEXT DIMENSION

integer, float → NUMBER METRIC

monetary → NUMBER METRIC

boolean → BOOLEAN DIMENSION

date → YEAR_MONTH_DAY DIMENSION

datetime → YEAR_MONTH_DAY_HOUR DIMENSION

many2one → TEXT (label) DIMENSION

selection → TEXT DIMENSION

many2many → NUMBER (count) METRIC

Connect from Google Looker Studio

Open Google Looker Studio → Create → Data Source
Search for and select the Odoo Looker Studio Connector
Enter your Connector URL: https://your-odoo.com/looker/api
Paste your API Token in the token field
Select the Odoo Model from the dropdown (models accessible by your token)
Click Connect - your configured fields appear as Looker Studio dimensions & metrics
Click Create Report and start building charts, tables, and scorecards

Validate & Test Your Setup

🔍 Validate Token

Test your token with a quick GET request:


                                            GET /looker/api/validate

                                            Authorization: Bearer <your-token>

Returns

{"valid":
                                            true, "user": "...", "token": "..."}

🔧 Local Testing with ngrok

If running Odoo locally on port 8069:

ngrok
                                            http 8069

Set the ngrok URL as web.base.url in Odoo System Parameters.
Set web.base.url.freeze = True to prevent Odoo from overriding it.

📋 Monitor via Request Logs

Every API call is logged under Looker Studio → Request Logs. Check the response code, duration (ms), records returned, and any error messages. Logs are auto-purged after 30 days.

Configuration Screenshots

Open the Looker Studio app from the Odoo Apps.

Create a new Looker Instance to configure your data connection.

Click on Generate Token to create the API access token.

Refresh the page after generating the token to load the credentials.

Click on Model Configs and create a new model configuration.

Select the desired Odoo model (e.g., contacts, sales orders).

Open script.google.com.

Create a new Apps Script project.

Replace the default Code.gs content with the connector script file.

Enable and open the appsscript.json manifest file in project settings.

Copy and paste the manifest content from the module into Apps Script.

Save all files and click Deploy → New Deployment.

Configure and deploy the web app by selecting access permissions and clicking Deploy.

Authorize the web app to access your Google account.

Bypass the unverified app warning by proceeding in advanced settings.

Review permissions and continue to grant access to the app.

Copy the Deployment ID and open the generated Data Studio connector URL.

Enter Odoo connector details (URL, API token, model) and click Connect.

Create a report from the connected Odoo data source.

Add the data source to your report in Looker Studio.

Start building the report by adding charts and components.

Select a chart type from available visualization options.

Configure the chart by adding dimensions and metrics to display data.

Token-Based Authentication

Each API token is generated using Python's secrets.token_urlsafe(48) — a 64-character, URL-safe, cryptographically secure token. Only a SHA-256 hash is stored in the database. The raw value is displayed only once and never stored in plaintext.

3 Ways to Pass the Token

Authorization: Bearer <token>
X-Looker-Token: <token>
?token=<token> query param

Token Lifecycle

Optional Expiry Date
Daily cron auto-deactivates expired tokens
Manual Revoke & Refresh buttons
Tracks Last Used & Total Requests

Model-Level Access Restriction

Each token can be restricted to a whitelist of Odoo models via the Allowed Models field. Requests to unauthorised models return 403 Forbidden. Tokens with no restriction allow access to all models the linked user can read.

How Authentication Works

Looker Studio sends a request to /looker/api/data/<model>
Token extracted from header or query param
Token is SHA-256 hashed and looked up in the database
If valid and not expired, authentication passes
last_used and request_count updated automatically
All ORM queries run as env(user=token.user_id) — Odoo record rules apply
Every call is written to the Request Audit Log

Validate Endpoint


                                    GET /looker/api/validate

                                    Authorization: Bearer <your-token>


                                    { "valid": true, "user": "Admin", "token_name": "My Token" }

Per-Model Configuration

Each Odoo model you want to expose gets its own Model Config record. A database constraint enforces one active config per model — onchange warnings appear immediately on duplicates.

Configuration Options

Select any non-transient Odoo Model
Tie config to a specific Token
Set Max Records cap (default 75,000)
Visual Domain Builder for record filtering
Live Matching Record Count preview

Domain JSON Export

The Domain JSON computed field auto-converts Odoo's internal tuple format to clean JSON — copy directly into Looker Studio.

[["state","=","sale"],
 ["date_order",">","2024-01-01"]]

Domain Merging

Config domain and runtime Looker Studio filter domain are merged together. Both enforced on every search_read. The parser handles JSON strings, Python literal strings, or already-parsed Python lists.

Common Models to Configure

crm.lead sale.order account.move stock.quant hr.employee purchase.order product.template

Per-Field Configuration

Click Sync Fields on any model config to auto-import every field from that Odoo model. Each field becomes a configurable row — toggle, rename, or retype before Looker Studio sees it.

Per-Field Controls

Selected toggle — include or exclude from API response
Display Label — rename to business-friendly names
Looker Data Type — override auto-mapped type: TEXT, NUMBER, BOOLEAN, Date, DateTime, Percent, Currency
Concept Type — DIMENSION (grouping) or METRIC (aggregation)
Description — shown in Looker Studio field picker

Automatic Type Mapping

Odoo field types are automatically mapped to Looker Studio equivalents on sync. Override any individually.

Odoo Type	Looker Type	Concept
`char`, `text`	TEXT	DIMENSION
`integer`, `float`	NUMBER	METRIC
`monetary`	NUMBER	METRIC
`boolean`	BOOLEAN	DIMENSION
`date`	YEAR_MONTH_DAY	DIMENSION
`datetime`	YEAR_MONTH_DAY_HOUR	DIMENSION
`many2one`	TEXT (label)	DIMENSION
`selection`	TEXT	DIMENSION
`many2many`	NUMBER (count)	METRIC

REST API Endpoints

Endpoint	Purpose
`/looker/api/info`	Version & status (public)
`/looker/api/validate`	Verify token validity
`/looker/api/models`	List accessible models
`/looker/api/schema/<model>`	Field schema for Looker
`/looker/api/data/<model>`	Fetch paginated records
`/looker/api/fields/<model>`	Raw Odoo field metadata
`/looker/api/search`	Advanced search + group_by
`/looker/api/count/<model>`	Count records by domain
`OPTIONS *`	CORS preflight handler

Data Endpoint Parameters & Response

Query Parameters

fields — comma-separated field names
domain — JSON filter domain
limit — max records (cap: 75,000)
offset — pagination offset
order — e.g. date_order desc

Response Shape


                                            {

                                             "records": [...],

                                             "count": 500,

                                             "total": 4830,

                                             "has_more": true,

                                             "duration_ms": 143

                                            }

Smart Serialization

many2one tuples → label string
many2many lists → item count

date/datetime → ISO 8601
False (non-bool) → null

Request Audit Log

Every API call is automatically logged. Browse the full history from Looker Studio → Request Logs.

Fields Captured per Request
Endpoint	`/looker/api/data/crm.lead`
HTTP Method	GET or POST
Token	Linked record
Odoo User	Token owner
Model	Target model name
Response Code	200 / 401 / 403 / 500
Records Returned	Exact count
Duration (ms)	Full response time
IP Address	Caller's remote IP
Error Message	Captured on 500 errors

Automated Cron Jobs

Cleanup Expired Tokens — daily, deactivates expired tokens
Cleanup Old Logs — daily, purges logs older than 30 days

Frequently Asked Questions

Which Odoo models can I connect to Looker Studio?

Any non-transient Odoo model is available — standard models like crm.lead, sale.order, account.move, hr.employee, stock.quant, and any custom model your business has built.

Is my Odoo data safe? Does this bypass security?

No. All queries run as env(user=token.user_id) — Odoo's own record rules, field-level access, and model access control apply. Only a SHA-256 hash is stored; the raw token is never saved.

What is the maximum number of records I can fetch?

75,000 records per request — matching Looker Studio's own connector limit. You can set a lower cap per model. Use limit and offset for pagination on larger datasets.

Does this work with Odoo running locally?

Looker Studio requires HTTPS. For local testing use ngrok: ngrok http 8069. Set the URL as web.base.url in Odoo System Parameters and freeze it with web.base.url.freeze = True.

Can I have multiple tokens for different teams?

Yes. Create as many tokens as needed, each tied to a different Odoo user with different model restrictions. Sales gets crm.lead, Finance gets account.move — fully isolated.

Does this module require external libraries?

No. Uses only Odoo 19's built-in framework and Python's standard library (json, ast, hashlib, secrets). No pip packages, no external services, no third-party API keys required.

All API Endpoints at a Glance

Everything the Odoo Looker Studio Connector exposes - grouped for quick reference

🔍 Discovery & Info

GET /looker/api/info - connector version & status (public, no auth)

GET /looker/api/validate - verify token is valid and active

GET /looker/api/models - list all models accessible by the token

GET /looker/api/fields/<model> - raw Odoo field metadata for a model

📐 Schema & Structure

GET /looker/api/schema/<model> - Looker-ready field schema with types and concept

Returns dataType, conceptType, label per field

Respects per-field config - only selected fields returned

Auto-maps Odoo types to Looker Studio data types

📦 Data Fetch

GET/POST /looker/api/data/<model> - paginated record fetch

Supports fields, domain, limit, offset, order

Merges config domain + runtime domain automatically

Returns records, total, has_more, duration_ms

Hard cap: 75,000 records per request

🔎 Search & Aggregation

GET/POST /looker/api/search - advanced search with group_by

Uses Odoo's read_group for aggregated metrics

GET/POST /looker/api/count/<model> - count records by domain

All endpoints support CORS OPTIONS preflight

🔐 Security & Tokens

SHA-256 hashed tokens - never stored in plaintext

Per-token Allowed Models restriction list

Token expiry with daily auto-deactivation cron

All queries run as the token's linked Odoo user

Full Odoo record rules and field-level access enforced

🗂️ Config & Automation

Per-model config: domain filter, max records, field selection

Per-field config: label, Looker type, concept type

Request Audit Log - every call logged with timing & IP

Cron: expired tokens auto-deactivated daily

Cron: logs older than 30 days auto-purged daily

Book a Demo or Watch Odoo Looker Studio Connector in Action

Schedule a walkthrough with our team or explore the product video playlist.

Watch Video Playlist

See Odoo Looker Studio Connector workflows, setup guidance, and real demonstrations of how the module works inside Odoo.

Schedule a Meeting

Talk to echoBitz about your use case, rollout plan, and the best Odoo Looker Studio Connector setup for your Odoo project.

Scan and Connect with echoBitz

Book a meeting, start a WhatsApp conversation, or reach us by email from one simple visual card. It is the fastest way to move from curiosity to a real MCP Studio discussion.

Meeting WhatsApp Email

Our Services

Odoo Integration

Seamlessly integrate Odoo with third-party apps, platforms, and tools for better workflow.

Odoo Implementation

We plan, configure, and deploy Odoo tailored to your business processes.

Customization

Get modules and workflows customized to meet your exact needs in Odoo.

Community Apps

Access or develop robust community apps to enhance your Odoo functionality.

Development Outsourcing

Hire dedicated Odoo developers to build solutions efficiently and cost-effectively.

Support & Maintenance

Enjoy peace of mind with our reliable support, updates, and bug fixing services.

Discover More Solutions by echoBitz IT

Explore our other Odoo integration apps

Odoo Xero Integration

Sync contacts, users, Quotes, and many more form sync both way.

Odoo Zoho CRM Integration

Bidirectional sync of leads, contacts, accounts, and activities with Zoho CRM.

Odoo HubSpot Integration

Connect contacts, companies, deals, and marketing workflows between HubSpot and Odoo.

Odoo Zendesk Integration

Sync Zendesk tickets, customers, and organizations with Odoo Helpdesk and contacts.

Odoo Office 365 Integration

Connect calendar, contacts, tasks, and emails with Microsoft 365 services.

Odoo WooCommerce Integration

Bidirectional sync of products, orders, customers, inventory, and payments.

View All echoBitz Apps on Odoo App Store

Ready to connect your Odoo data to Google Looker Studio?

Install the Odoo Looker Studio Connector, generate your first secure API token, and start building live dashboards from your Odoo data in minutes - no middleware, no exports, no code required.

Get Support Schedule a Demo Visit Our Website

echoBitz IT Solution Pvt. Ltd. | Odoo Certified Partner | info@echobitzit.com | www.echobitzit.com

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

The author can leave a single reply to each comment.
This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
If you want to start a discussion with the author or have a question related to your purchase, please use the support page.