Restricting access to your ThinkIQ system by network address: what it covers, how you manage it, and what to expect.
What it does
IP Whitelisting lets you restrict your ThinkIQ system so that only connections from internet addresses you have approved are accepted. Everything else is turned away at the front door, before it reaches the application.
This is an additional layer on top of the user accounts, passwords and permissions you already use. It does not replace them: a valid username and password cannot be used from a network location you have not approved.
Until you add an entry, nothing is restricted. An empty list means "allow everyone", so switching the feature on changes nothing until you decide what to allow.
What is protected
Your system has two separate entrances, each with its own independent list.
| Web application | Data ingestion | |
|---|---|---|
| Address | yourcompany.thinkiq.net |
opcua.yourcompany.thinkiq.net |
| Who connects | People and software: browser sign-in, dashboards, reports and exports, and every programmatic interface including the GraphQL and REST APIs | Machines only: the site gateways at your plants that deliver sensor and process data into the platform |
| Typical list | Office and branch internet addresses, your VPN, and any third-party systems that call the APIs on your behalf | The internet address of each plant or site where a gateway runs. Usually short, and it rarely changes |
| If blocked | The browser or API client receives an "Access restricted" page showing the address it connected from | The gateway cannot connect and data stops flowing; it retries on its own and buffers data locally until it is allowed |
Two things people often do not realize:
- The web entrance covers more than browsers. Any script, reporting tool or partner system that uses the GraphQL or REST APIs comes through the same door and must be on the web list.
- The ingestion entrance is separate and easy to overlook. It is how your plant data arrives. Its list is managed independently, so a change made for office staff can never interrupt data collection, and vice versa.
Gather the addresses your organization uses. Your IT team or internet provider can confirm them.
| What to gather | Notes |
|---|---|
| Office and site internet addresses | The public addresses your locations use to reach the internet. Ranges are fine. |
| VPN address | If staff connect through a company VPN, its public address usually covers everyone, including people working from home. |
| Remote workers | Home internet addresses change frequently. Have remote staff connect through your VPN rather than listing home addresses. |
| Third-party integrations | Any external system that reads from or writes to the platform through the APIs needs its address on the web list. |
| Plant gateway addresses | The public address of each site where a data gateway runs. These go on the ingestion list. |
Managing the lists
Administrators you designate manage both lists from the IP Whitelisting page in the admin console. No support ticket is needed for routine changes.The page
- Your current address. The banner at the top shows the address you are connecting from and whether the web list covers it. Check it before you change the web list.
- Two tabs, Web and Ingestion, one per entrance. Each shows its entries with a label, an on/off switch, who added it and when, and who last changed it.
- Enforcement status. Under each tab's description a line reports what is actually in force: Enforcing 3 entries — last checked 09:41 UTC, or the list is empty, so all addresses are allowed. Immediately after you save it reads Changes pending — applied within about a minute, and switches back once the change is live. If it ever shows a warning, the change has not been applied; contact ThinkIQ support.
Adding entries
Click Add entry on the tab you want. One save can add one address or many:
| You can type | Stored as |
|---|---|
A single address, 203.0.113.7 |
that address |
A block, 203.0.113.0/24 |
that block |
A range, 203.0.113.10 - 203.0.113.20 |
the smallest set of blocks that covers it |
| A list of any of the above, separated by commas or one per line | one entry per address or block, all sharing the label you give |
IPv4 and IPv6 are both accepted. Give the entry a label such as "Manchester office" or "Site 4 gateway" so the list stays readable.
The page checks everything before saving:
- Invalid addresses are rejected and the form stays open for correction. When you paste a list, one bad element rejects the whole list and the message tells you which one, so nothing half-lands.
- Duplicates are refused, including a different spelling of a block that is already listed.
- Very broad blocks, and private or non-routable addresses that could never match internet traffic, are flagged for you to confirm before saving.
- If you type an address with host bits set inside a block, it is stored as the block and the page tells you.
Editing, switching off and deleting
- Edit changes an entry's address or label. An existing entry holds one address or block; to add more, add new entries.
- The switch turns an entry off without deleting it. Keep the Manchester office in the list but inactive, for example.
- Delete removes it after a confirmation.
Changes take effect within about a minute, with no downtime and no interruption to connections that are already established.
The lockout safeguard
The web list will not let you lock yourself out by accident. If a change would leave the enabled web list not covering the address you are connecting from, the page stops and offers two ways forward:
- Add my current address and save, which adds your address as its own entry along with the change. This is the safe choice.
- Save without my address, for the rare case where you know better, for instance when you administer the system from an address that ThinkIQ support has already covered. You must type your current address to confirm.
The safeguard applies to every change on the web list: adding, editing, switching off and deleting. It never applies while the web list is empty, because an empty list blocks nobody.
Switching on the ingestion list: read this first
The ingestion list has no lockout safeguard, because your browser's address says nothing about where your gateways are. The first entry you enable on the ingestion list starts blocking every gateway that is not listed, immediately.
So: gather every gateway address first, then add them all in one save using a comma-separated list. A gateway that is blocked keeps retrying and buffers data locally, so a short gap is recovered, but a forgotten site stays dark until it is added.
What a blocked visitor sees
- Web: an "Access restricted" page in ThinkIQ style. It shows the visitor the address they connected from and tells them to ask their administrator to add it on the IP Whitelisting page, with a note that access is restored within about a minute of the change. That is exactly the information you need to resolve it.
- Ingestion: nothing visible. The gateway's connection is refused and it retries at increasing intervals. Its buffer drains once it is allowed.
If someone is locked out
- Ask them for the address shown on the "Access restricted" page.
- Add it on the web tab, or switch on the entry that should have covered it.
- Access returns within about a minute; they can simply reload.
If the administrator is the one locked out, ThinkIQ support retains access at all times and can restore yours. Contact support with the address you are connecting from.
- Email and notifications are unaffected. They are sent out from the system and do not depend on the lists.
- Mobile and travelling staff should connect through your company VPN. Mobile networks change addresses too often to list reliably.
- Uptime monitors and integrations you rely on must be on the web list, or they will report your system as down.
- Everything is yours to adjust at any time. Adding a new office or site is a minute's work on the settings page, and switching an entry off is reversible.
- Change tracking. Every entry shows who added it and when, and who last modified it.