Granting access, an account for a new joiner, removing permissions after someone leaves: the same thing a dozen times a month, by hand and after hours. We set these processes up so they run without waiting for someone in IT to be free.
30-minute call · risk list within 1 business day · no obligation
Trusted by
Granting access and removing it after someone leaves is set up so it does not wait for a free person in IT.
Our fulfilment product: an employee raises a request in the portal, the resource owner approves it, and the permissions are granted without an administrator stepping in.
We connect Jira Service Management, Microsoft 365, Google Workspace, Active Directory, backup and monitoring so data is not retyped from one system into another.
We built Aclovo because deploying Jira Service Management alone ends the work at the ticket, not at getting it done. Where the tools you already have are enough, we do not push our own product.
Six processes clients most often start with. Each can be counted in working hours, and under every description there is a link to the page that goes into detail.
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.
Account, mailbox, groups, licences, drive access and a computer ready for day one. One request instead of a task list scattered across departments.
Access revoked the same day, recurring tasks reassigned to an active account, data kept where it should stay. Nothing is left open by accident.
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.
Tickets land straight in the right queue, with an SLA and a form that collects the data you need. IT stops being a mailbox.
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 cases, not a closed list. We also automate what eats time 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.
Free preliminary review
Not sure where to start? A 30-minute call, and within one business day you get a list of risks in your company.
Because the process stays on your accounts, not in our inbox. These are the problems companies bring most often, and how we close them.
1–3 days
“We do not know what can even be automated.”
Writing the process down takes 1 to 3 days. It ends with a list: what can start now, what needs a change in the systems, and what is not worth touching.
No queue
“A new hire waits until someone in IT grants access.”
The request, the approval and the permission go through without waiting for a free person in IT. Removing access after someone leaves is the same flow.
Stays with you
“What happens when you stop running this?”
Flows are built on your accounts and licences. The documentation describes every step. If you leave Aclovo, the data and the approval history stay in your systems.
One team
“Will the automation stop work when something fails?”
Every process starts with one team or one type of request. The manual path stays open until the automation also handles the exceptions.
A few days
“What does automating one process cost?”
A simple access request in tools you already have is a few days of work. You get the price after the process is written down, with an estimate of the hours it removes each month.
1 month
“I am afraid of being stuck with one company.”
Notice is one month, from day one. What we built on your licences keeps running after the engagement ends.
Plus someone who knows the process and the history of exceptions. Not a hotline, and not a new person every time.
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.
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.
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.
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.
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.
We check that the automation still works after changes in the source systems. Further processes go in once the previous one is stable.
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.
An Aclovo rollout gives you a self-service portal that fulfils access requests: the employee asks, the resource owner approves, the permissions are granted automatically.
Service catalogue, queues, SLAs and the request portal. A Jira Service Management rollout is the most common starting point, because that is where the request lands.
Process automation in n8n, Zapier integrations and Power Automate flows go where they can later be maintained without a developer.
Microsoft 365, Google Workspace and Active Directory, and through REST API and webhooks also industry systems and ERP.
Microsoft 365 Google Workspace Active Directory
Two processes that used to run through a shared mailbox. What we found, what we built and how much time it took off the team.
A law firm grants access to the files of one specific case, an accounting office lets a client into their folder only, and a software house opens accounts in a dozen systems at once. See what we automate in your industry.
By counting what repeats most often. Usually it is enough to go through the last three months of tickets and see which ones come back in the same shape. Writing the process down takes us one to three days and ends with a list: what can be automated straight away, what needs changes in the systems, and what is not worth touching.
No. Jira Service Management is the most convenient place to start, because that is where the request lands, but we also build automations on forms, mail and whatever you already have. If there is no portal, we say plainly what deploying one costs and whether it makes sense in your case.
It stays with you and keeps running. We build the flows on your accounts and licences, and we hand over documentation describing what every step does. Aclovo is a subscription service, so if you drop it you go back to granting permissions by hand, but the data and the approval history stay in your systems.
It depends on how many systems have to be connected and how many exceptions there are. A simple access request flow in tools you already have is a few days of work. A process running through an ERP and industry systems can be several times more. You get the quote after the process is written down, together with an estimate of how many hours a month it will save.
That is why every process starts with one team or one type of request, and the manual route stays open until the automation handles the exceptions too. After the rollout we monitor the flows and react to errors before a user reports them.
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.
2019 - 2024 Interactive Workspace Ltd. - All rights reserved.