InnerWeb
Skip to main content

Cost of handling access requests: manually and after linking companies

Every access request to the plant requires a decision, and the decision costs operator time. The question the head of security asks is: how much of that time can be recovered without losing control? Below is a sample calculation for two models, manual approval of every request and automatic acceptance of requests from companies already linked, together with the conditions that must be met before the second model can be switched on at all.

approx. 4 h
saved a month in the sample calculation
Source: sample calculation
1
manual acceptance per company before automation
Source: internal card

Why does a company's first request always get reviewed by a person?

The link between an organisation in the portal and a company at the plant is created only after the first manual approval by the operator, when the company's tax ID matches the organisation's tax ID. The tax ID from the portal alone grants no access, because it is not verified in the portal. The operator is therefore the first and only filter that confirms that a real company stands behind the organisation and that the plant has a relationship with it.

Only after this step can subsequent requests from people in that organisation be accepted faster. This is a reasonable compromise: the cost of manual verification is paid once per company, not once per employee.

When does a request pass automatically, and when does it stay manual?

Automatic acceptance of requests from a linked company is disabled by default. It is switched on with a configuration variable in the installation, and removing the variable restores full manual approval, so returning to the cautious model requires no changes to the data. Automation works only when the e-mail address in the request does not yet have an account at the plant.

If the address exists, the account is not linked automatically. The decision reads: approved, with instructions to log in with the portal account and confirm with the password. A request from an employee with an existing account is therefore not a candidate for full automation, and in the calculation we count it on the manual side.

What happens at acceptance?

Acceptance of a request is atomic: the company, account, permissions and pass are created in one transaction, and an error at any step leaves the request unprocessed. The operator does not have to clean up after a half-completed save, which also shortens the time spent on exceptions.

Operator time on requests with 60 requests a month (sample calculation)

Operator time on requests with 60 requests a month (sample calculation)Bar chart: 9 hours a month with manual approval of all requests, 5 hours with automatic acceptance of half of them0246810hAll manual: 9 h9 hAll manualHalf automatic: 5 h5 hHalf automatic
Source: Sample calculation based on the assumptions in the Calculation section

Who can decide, and what does the queue look like?

Acceptance, rejection and retrying a decision are limited to the service administrator role, and a new request creates a notification for this role. The cost therefore covers not only the assessment of a request but also the reaction to the notification. In a plant where one person holds the role, it is worth planning a backup for holidays, because a request without a response blocks the contractor.

If a decision does not reach the portal, it is saved with the request together with the error description and can be retried from the panel. This scenario is rare, but it should be included in the operator's contingency time.

How much can be saved and what does it depend on?

The calculation below assumes 60 requests a month, half of which come from companies that are linked and from people without an account at the plant. The remainder need manual assessment, because they concern new companies or existing addresses. The result is a few hours a month: a real but moderate benefit, larger at plants with many returning companies.

Indicative ranges for the integration, with individual quotes from 2025-2026 implementations, are discussed at the conversation stage. We do not assume that automation is a goal in itself: plants with high turnover of new companies should keep manual acceptance.

Example calculation

Sample calculation: 60 access requests a month

Assumptions
ParameterValue
Requests a month60 pcs
Time for a manual review of a request9 min
Share of requests eligible for automation50 %
Time to review a request accepted automatically1 min

Result: All manual: 60 x 9 min = 540 min = 9 h. With automation: 30 x 9 min + 30 x 1 min = 300 min = 5 h. Saving 4 h a month.

Note: Sample calculation on openly stated assumptions. The share of requests eligible for automation depends on the number of linked companies at a given plant.

Video

Frequently asked questions

Does the tax ID of an organisation in the portal alone give access to the plant?

No. The tax ID is not verified in the portal, so the link is created only after the first manual approval by the operator, when the company's tax ID matches the organisation's.

How do we switch off automatic acceptance of requests?

Remove the configuration variable in the installation. Then all requests require manual acceptance.

Who sees the notification about a new request?

The service administrator role. Only this role can also accept, reject and retry decisions.

Let's check how many of your requests qualify for automation

Based on the number of returning and new companies, we will show whether switching on automatic acceptance makes sense and describe the conditions for a safe start.

Let's talk