Automation and self-service

Our own product and integrations written around your process

JSM requests should not end in a manual queue. Aclovo fulfils them automatically; we wire the rest with integrations.

Aclovo

Aclovo is our fulfilment product: automatic execution of Jira Service Management requests on the infrastructure.

  • A self-service portal for your staff
  • Approval sits with the resource owner, not with IT
  • Permissions granted automatically in Microsoft 365, Google Workspace and Atlassian
  • The permission matrix builds itself, with no spreadsheet to maintain

Our own product

Integrations and flows

We connect JSM, Microsoft 365, Google Workspace, Active Directory, backup and monitoring, without waiting for manual fulfilment.

  • Integrations over REST API and webhooks
  • Flows in n8n, Zapier and Power Automate
  • PowerShell scripts where an API is not enough
  • JSM connected to Microsoft 365, Google Workspace and Active Directory

Integrations

Aclovo is a competence signal: we can deploy JSM and close the loop through to execution.

What we automate

We take on the work that repeats often enough for the cost of doing it by hand to be countable. We start from the process, not from the tool.

Access and permission requests

An employee requests from the portal, the resource owner approves, permissions are granted on their own. IT drops out of the queue and the approval history stays in the system.

Onboarding a new employee

Account, mailbox, groups, licences, drive access and a computer ready for day one. One request instead of a task list scattered across departments.

Offboarding and revoking access

Access revoked the same day, recurring tasks reassigned to an active account, data kept where it should stay. Nothing is left open by accident.

Approval flows and internal requests

Requests for hardware, licences or permission changes with a clear approval path and a deadline. It is obvious who is holding the case and since when.

Service catalogue and queues in JSM

Tickets land straight in the right queue, with an SLA and a form that collects the data you need. IT stops being a mailbox.

Reports and permission reviews

Recurring reports on who has access to what and what has changed. Permission reviews stop being a once a year project.

These six are the most common requests, not a closed list. We automate whatever eats time in your company, including outside IT: document routing, reports assembled by hand from several systems, retyping the same data between programs. If a process can be written down step by step, it can usually be closed. Tell us what you do by hand today and we will work out whether automating it pays off.

How we run an automation project

We do not automate a process nobody understands. First we write it down, then we try it on a single case, and only at the end do we switch it on for everyone.

  1. Day 1-3

    Writing the process down

    We sit down with the people who handle the process by hand today. We record the steps, the exceptions and the points where a case stalls. We measure how long it takes now.

  2. Day 4-5

    Scope and quote

    We show what can be automated straight away, what needs changes in the systems, and what is not worth automating. Plus a quote and an order of work.

  3. Week 1-2

    A pilot on one case

    We run the automation for one team or one request type. We check what happens on exceptions and fix it before the rest goes live.

  4. Week 3-4

    Rollout and handover

    We switch the process on for everyone, write the documentation and show your team how to manage it. We do not leave behind something nobody on your side understands.

  5. After go-live

    Maintenance and growth

    We check that the automation still works after changes in the source systems. Further processes go in once the previous one is stable.

What we build on

First we check whether the process can be handled with the tools you already own. Our own product comes in where standard solutions do not reach.

Aclovo, our product

A self-service portal that carries out access requests: the employee requests, the resource owner approves, permissions are granted automatically.

Aclovo

Jira Service Management

Service catalogue, queues, SLAs and the request portal. Most automation starts there, because that is where the request arrives.

Jira Service Management Atlassian

Flow platforms

Simpler connections we build in n8n, Zapier and Power Automate, because they are easy to maintain later without a developer.

n8n Zapier Power Automate

The systems we connect

Microsoft 365, Google Workspace and Active Directory, and through REST API and webhooks also industry systems and ERP.

Microsoft 365 Google Workspace Active Directory

Sample projects

Offboarding cut from a week and a half to a few hours

Industry and size:
Law firm, 30 people
Starting point:
Every departure meant several days of work for the back office. The industry system was the worst part: someone had to find all the leaver's recurring tasks by hand and reassign them to an active account, or they stopped being created.
What we did:
We wrote a tool that walks through the whole system on its own, finds the tasks of the person being offboarded and reassigns every recurring one to a chosen account.
Timeline:
5 working days
Result:
An offboarding that could take one person out of the back office for a week and a half now closes in 3 to 4 hours. That is how long it takes to get through the system API limits.

SharePoint split up, permissions without a queue to IT

Industry and size:
Construction, 50 people
Starting point:
The whole company worked on a single SharePoint site, long past the size Microsoft recommends. Sync stopped keeping up and files went missing. Permissions were granted by hand, folder by folder, and the permission matrix was never up to date.
What we did:
We split SharePoint into smaller, ordered areas and rolled out Aclovo, our self service portal. Granting access moved from IT to the resource owners: an employee requests a folder, the owner approves, permissions are granted automatically.
Timeline:
1 month
Result:
The back office got back the time that used to go into permissions, and the permission matrix builds itself, with no spreadsheet to keep alive.

The terms we work on

The same terms apply to a one-off project and to a monthly plan.

PLN 2 million liability insurance

Our liability for damages is insured for PLN 2 million. A policy with a stated sum insured, not a reassurance given in a sales call.

No minimum contract term

We do not tie you into an annual contract or a lock-in period. One month’s notice applies from the first day, with no exit penalties.

Your environment, documented

We document the whole environment as we go and it belongs to you. When the partnership ends, we hand it over within 5 days and brief your next provider.

Access always stays on your side

Administrator accounts, domains and licences are registered to your company. Taking back control of the infrastructure needs neither our consent nor our help.

Predictable subscription

One fixed monthly rate. Work outside the subscription is quoted upfront and starts once you approve it, so nothing reaches the invoice that you have not agreed to.

One account manager and an SLA in the contract

You have an assigned account manager and you know them by name. Response times are written into the contract, from 15 minutes for critical incidents.

Tell us about your infrastructure

The first meeting takes 30 minutes and commits you to nothing. We will tell you straight whether we can help and what we would propose.

Wielkopolska · Poznań · Kalisz · Konin · all of Poland