Overview
The Binocs integration reads user and capacity data from Binocs, so your Binocs commitment can be compared with what is actually being used.
What you get
- A self-serve connection on the Integrations page
- Your API token stored encrypted against your tenant
- Connection status visible to your team
Prerequisites
You need a License Logic account and a Binocs administrator.
License Logic Requirements
- Account: active License Logic subscription
- Role: a role holding Settings: Edit — that is what the Connect action checks
- Page: Integrations in the left sidebar, which requires Integrations: View
If the Integrations page is missing, or Connect does nothing. These are two different permissions. Integrations: View shows the page and the tiles; Settings: Edit is what allows a connection to be made. A user can hold the first without the second, see the tile, and be unable to complete the connection. Your License Logic administrator grants both in People → Roles.
Binocs Requirements
- Account: an active Binocs instance
- Role: access to the Binocs admin section, or a Binocs contact who can issue an API token on your behalf
- Your instance host — for example
yourcompany.mybinocs.com - Network: nothing to install. License Logic calls Binocs outbound over HTTPS
Setup Guide
A note on this section, so you know what you are reading. Binocs does not publish a public API reference — its documentation is not reachable without a login, and Bluecrux’s public material on integration describes a business-configured, zero-code approach rather than a developer API. This guide therefore documents what we can state accurately: what License Logic needs and how the connection works on our side. Your Binocs administrator or Bluecrux contact is the right source for the exact steps inside Binocs, and we would rather send you to them than invent a menu path.
Step 1: Request an API token
In the Binocs admin section, request an API token. Binocs issues the token to you after you have signed in yourself, which is the property that matters here: License Logic never receives your Binocs password — only a token that you can revoke at any time.
If the option is not visible to you, your Bluecrux contact can arrange it.
Ask for a token dedicated to this integration where Binocs allows it, so that revoking it later affects nothing else you have connected.
Step 2: Note your instance host
This is your Binocs hostname — for example yourcompany.mybinocs.com. Hostname only: no https:// and no path.
Step 3: Connect in License Logic
- In License Logic, click Integrations in the left sidebar
- Find the Binocs tile and click Connect
- Enter your Instance host
- Paste the Bearer token from Step 1
- Click Connect
| Field | Required | What to enter |
|---|---|---|
| Instance host | Yes | yourcompany.mybinocs.com. Hostname only, no protocol or path |
| Bearer token | Yes | The API token from Step 1. Stored encrypted; never shown again |
Your credentials are stored and the tile records the connection as saved but not yet confirmed. That is the correct outcome — see Security & Data Handling.
What Data Is Synced
Users and roles
License Logic reads who holds access to Binocs and in what capacity, joined to your employee records by email address:
- The user list — name, email address, and account status
- The role or access level each person holds, which is what any seat-based commitment would be counted against
- Last activity, where Binocs exposes it
How your Binocs agreement is counted is confirmed with you. Binocs commitments are structured differently between customers, and Binocs documentation is available through Bluecrux rather than publicly. We confirm the basis your agreement is counted on as part of setting you up, so the seat figures you see match the way you actually buy. If your team already knows, telling us at the start makes it quicker.
Read-only, and narrow. The integration reads user and access information. It reads no plans, schedules, resource data or operational records, and it writes nothing.
Where Your Binocs Data Appears
Binocs data lands in the places you already use to answer licence questions, rather than in a separate Binocs area you would have to remember to visit.
Applications
Your Binocs row on the Applications page shows access facts rather than sign-in counts:
- Total licences — the seats you hold, sourced from the Binocs API rather than typed in by hand
- Assigned — how many of those seats are actually allocated to a person
- Breakdown by licence type — entitled against assigned, per licence, ordered so the largest gap is first. That top row is the one worth acting on, and it is rarely the alphabetically-first one
- Idle seats — the difference, which is the number that converts into a renewal conversation
Application drill-down
Opening Binocs shows everyone holding access and the role they hold, joined to your employee records.
Insights → Employee
Each employee’s record gains Binocs as a source alongside SSO sign-in, desktop agent and card-spend data. Opening a person shows the applications they hold, so a leaver review or a role change can see the Binocs seat in the same place as everything else they hold.
Suppliers and renewals
Because seat counts arrive as data rather than as a number someone typed into a contract, your Binocs agreement can be compared against actual allocation as the renewal approaches — which is the moment the difference is worth money.
Two switches, not one. A tenant needs the integration connected and the licence display enabled for it. That is deliberate: it stops a seat panel appearing for a tenant whose connection cannot actually compute one, which would show an empty panel rather than an honest absence. We enable both together and tell you when we have.
Sync Schedule & Refresh
Daily sync
License Logic reads Binocs once per day, overnight UTC, in the same window as our other licence integrations. Each run replaces the previous day’s picture, so revoked seats and new assignments are both reflected without anything to reconcile by hand.
Initial sync
Your first sync is scheduled once your connection is confirmed. It reads user records only and completes quickly.
What triggers a sync
- Initial connection — your first sync is scheduled once your connection is confirmed
- Daily scheduled sync — automatically, once per day
- Reconnection — reconnecting with new credentials resumes syncing on the next scheduled run
A failed sync leaves yesterday’s data in place. If a run cannot complete — Binocs is unreachable, or the credential has been revoked — License Logic keeps the previous successful result rather than emptying the panel. “This tenant has no licences” and “we could not read them today” look identical on screen, so we never let a failure produce the first one.
Disconnecting Binocs
Disconnecting deletes your stored Binocs credentials. They are removed from the database outright, not disabled behind a flag, so reconnecting means entering them again, and any data already synced is removed with them. Your Binocs account itself is untouched, but you may need to issue a new credential there if you did not keep the original.
To disconnect:
- Go to Integrations in the left sidebar
- Find the Binocs tile (showing “Connected”)
- Click Disconnect
- Confirm in the dialog
Revoking from the Binocs side
Ask your Binocs administrator, or your Bluecrux contact, to revoke the API token. The connection stops working immediately and nothing else about your Binocs account is affected.
Revoking on the vendor side and disconnecting in License Logic are independent. Doing both is the complete removal: one stops the credential working, the other removes our copy of it.
Security & Data Handling
What License Logic holds
A single Binocs API token — never a user password. Binocs issues the token to your administrator after they sign in themselves, so License Logic never sees a Binocs password, and the token can be revoked at any time. Also your instance hostname, which is not a secret.
| Control | Detail |
|---|---|
| Encryption at rest | AES-256-GCM with a random initialisation vector per value, applied before the value is written to storage |
| In logs | Never written. Connection events are logged with the credential values redacted |
| Retrievable via API | Never returned — not even to your own administrators. The connection-status endpoint is built from the non-secret fields only, so a secret cannot be read back through it |
| In transit | TLS 1.2 or above, passed in a request header or form body. Never placed in a URL or query string |
| Who can connect or disconnect | Only a user holding Settings: Edit in your License Logic tenant |
| Who can see the connection status | A user holding Integrations: View. Status shows the non-secret settings, whether the connection is verified, and when it was made |
| Tenant scope | Stored against your License Logic tenant. Connect, status and disconnect are all keyed on the caller’s own tenant, so no request from another customer can reach your connection |
| Permissions the token carries | Whatever Binocs grants that token. License Logic cannot widen it — if you want to narrow what we could ever see, narrow the token |
Verification on connect
License Logic does not verify this credential on connect. There is no published Binocs endpoint we have been able to read our own documentation for, so there is nothing we can call that would tell you something true. Your credentials are stored and the tile shows them as saved, not yet confirmed.
This is a deliberate choice over the alternative. A check written against a guessed endpoint reports a good credential as unverified, and then nobody can tell whether the credential or the guess was wrong. An honest “we have not confirmed this” is more useful than a red mark that means nothing.
Access control
- Settings: Edit is required to connect or disconnect
- Integrations: View is required to see the Integrations page and connection status
- All endpoints are authenticated through your License Logic session
Data retention
Credentials are retained until you disconnect, at which point they are deleted from the database outright rather than disabled behind a flag.
Revoking the token in Binocs stops the connection immediately, whether or not you also disconnect in License Logic. Doing both is the complete removal.
For more about License Logic’s security practices, see our Security Policy or contact security@licenselogic.co.
Troubleshooting
The tile will say “saved, not yet confirmed”, and that is correct. License Logic does not test Binocs credentials at connect time, because there is no published endpoint we have been able to read documentation for. An unconfirmed connection here is not a fault and does not need reporting.
We cannot find where to request an API token
This is a Binocs question rather than a License Logic one. Your Bluecrux contact or Binocs support can arrange it. If API access is not available on your Binocs arrangement, that is the answer, and worth establishing before anyone spends longer on it.
Connected, but no data has appeared yet
Your first sync is scheduled once your connection is confirmed, so data appears shortly after rather than the instant you click Connect. If the tile shows the connection as verified, the credential side is done. If nothing has appeared after your first scheduled sync, contact support and we will look at the run.
The Connect button does nothing, or the tile is missing
This is almost always permissions on the License Logic side. Integrations: View shows the page; Settings: Edit is required to connect. Ask your License Logic administrator to check both in People → Roles.
Frequently Asked Questions
Does License Logic receive our Binocs password?
No. Binocs issues an API token to your administrator after they have signed in themselves. License Logic only ever holds that token, and it can be revoked at any time.
Can License Logic change anything in Binocs?
No. The integration reads user and capacity information. It does not create, edit or delete plans, resources, users or settings. Today it does not read anything at all.
How are Binocs licences counted?
That varies between Binocs agreements, so we confirm it with you during setup rather than assuming a basis that may not match your contract. If your team already knows how yours is counted, telling us at the start saves a round trip.
What happens if we disconnect?
The stored token is deleted from License Logic, and any Binocs data already synced is removed with it. Your Binocs account itself is untouched — the token remains valid there until you revoke it.
Support
If you need help with the Binocs integration:
- Email: support@licenselogic.co
- In-app chat: click the chat icon in the bottom-right corner of License Logic
- Security questions: security@licenselogic.co
When contacting support, please include your company name, your Binocs instance host, and a description of the issue. Never send a credential by email — if we need to look at a connection, we can do so from our side.
If you would like to be told when the sync for this integration is enabled, say so and we will add you to the notification list for it.