InnerWeb
Skip to main content

Access control integrator: how to add location to your offer

An integrator that has installed an existing access control system can extend its offer with permits, qualifications and location without replacing the client's readers. InnerWeb does not make or replace readers, so it does not compete with what the integrator has already delivered. It adds a layer on top of it.

2
versions of the REST API (v1 and v2)
Source: product documentation
3-6 mo.
duration of the pilot
Source: InnerWeb offer

Why an access control integrator is a natural partner

An integrator that has installed readers, controllers and access control software knows the plant, its gates, zones and the people responsible for security. This is exactly the knowledge a rollout of a permits and location system needs.

InnerWeb is a software manufacturer and does not make or replace access control readers. It integrates with the client's existing access control system, and the partner may be the installer of that system. For the integrator this means an additional item in the offer, without the risk that the client questions the equipment already in place.

Recommendations for the integrator

The recommendations below concern the order of actions, from the first conversation with the client to go-live.

1. Start by asking what the access control system does not do

An access control system records that a card was read. It does not say whether a person has a valid training record, a work permit for a given zone or where exactly they are after passing the gate. That gap is the subject of the conversation, not a replacement of readers.

2. Use the API and webhooks, not intervention in the controllers

The platform offers a REST API in versions 1 and 2 with JWT authentication, and webhooks to the automation platform. The integrator can pass card read events from the access control system to InnerWeb without any changes to the controllers or readers.

3. Link the card read to qualifications and permits

The security panel scans a QR badge or an RFID card and gives a verdict on whether the person may be on the site, based on valid training, qualifications and permits. For the client this is a concrete benefit that they see at the gate.

4. Propose a pilot instead of a large project

A pilot lasts 3 to 6 months and ends with acceptance against explicit criteria. A smaller scope, for example one hall or one gate, lowers the barrier to a decision on the client's side.

5. Agree your company's role in the three contracts with the client

The partner model consists of a licence agreement with the manufacturer and a maintenance and implementation agreement with the partner. The access control integrator can take over both partner agreements, and the client has one contact for service matters.

6. Count the mark-up honestly

Prices in the manufacturer's offer are without the integrator's mark-up, which you add on your side. Indicative ranges from 2025-2026 rollouts for a typical rollout are from PLN 12,600 to PLN 34,000 net, one-off; individual quotes apply. The client will see the manufacturer's price list anyway, so transparency builds trust.

Transmitter density: area covered per transmitter

Transmitter density: area covered per transmitterColumn chart: 100 m2 per transmitter at dense layout, 200 m2 at sparse layout050100150200m2 per transmitterPlant road (segment): 100 m2 per transmitter100Plant road (segment)Building, dense: 100 m2 per transmitter100Building, denseBuilding, sparse: 200 m2 per transmitter200Building, sparse
Source: Sizing rule: in a building 1 transmitter per 100 to 200 m2, on roads roughly every 100 m

How to put the integration into the specification

A good integration specification has several fixed elements. It states which events the access control system sends, in what format and with what delay, and what data goes back to the access control system if the client needs it. It also describes how a person is identified: the card number must match an account in InnerWeb.

Record who is responsible for configuration on the access control side and who on the InnerWeb side. Roles in the system and the permissions matrix let you configure access for administrators, security, OHS and the coordinators of external companies without any change to the code.

  • list of events passed from the access control system and their format
  • mapping of the card number to a person's account
  • handling of connection errors and retries
  • responsibility for configuration on both sides
  • acceptance test with the participation of security

What not to promise the client

Do not promise the replacement of readers or a change of card technology; that is outside the scope of InnerWeb. Do not promise legal compliance as a guarantee either. The system supports meeting the requirement and provides evidence for an audit, while the assessment of compliance rests with the client.

Do not treat location as a replacement for GPS. Position is calculated from signals of several transmitters averaged on the map. Inside a building, the rule is 1 transmitter per 100 to 200 m2, and on plant roads roughly every 100 m.

Video

Frequently asked questions

Does InnerWeb sell card readers?

No. InnerWeb is a software manufacturer and integrates with the client's existing access control system, which it does not replace.

How do access control events reach InnerWeb?

Through a REST API (versions 1 and 2, JWT authentication) and webhooks to the automation platform.

Can an integrator be a partner?

Yes. The partner can be the installer of the client's access control system and run the rollout and maintenance under the three-contract model.

Add location to your access control offer

We will discuss integration through the API and webhooks and the terms of partnership. Book a call or a demo.

Let's talk