FOR COMPANIES THAT PREFER AUTOMATED PROCESSES. NOT EMAILS AND IT QUEUES
Leave with cover and auto-reply. Access to a SharePoint folder or a mail group. A new person on the team. A different matter every time, the same portal and the same approval path. After the owner agrees, the portal grants rights, adds members to the group, turns on auto-reply, or runs the rest in your system.
WHAT THE PORTAL HANDLES
Concrete tasks that today go by email or manual clicks in a console. The same request, the same approval, automatic execution in Microsoft 365.
The portal builds a view of who has access to which folder. No manual list gathering before an audit or before someone leaves.
An employee asks for access or reports they no longer need it. After owner approval, the portal automatically grants or removes permissions on the site or folder.
An employee requests a new site or deletion of an existing one. They choose Team site or Communication site and name owners and members. After approval, the portal creates or removes the space in SharePoint.
An employee asks to add or remove people from a distribution list or a Microsoft 365 group. After owner approval, the portal updates group membership.
One request instead of an email to IT. After approval, the portal creates a distribution list or Microsoft 365 group with a mail address, owners, and initial members.
One form instead of three emails. After manager approval, the portal sets the auto-reply and forwards mail to the substitute.
No processes match your search.
Governance
Permission chaos usually starts with free-for-all grants: everyone assigns differently, nobody knows who has access where. The portal keeps one group schema, owner approval before change, a matrix for audit, and a trail of every decision.
MODEL
Four steps that look the same no matter the request. People learn them once.
The employee chooses from the catalog. Same view, same way to file a request.
Someone accountable for that matter decides. Not a generic IT queue and not a manual change in a console.
After approval, the portal runs the change in the system. Status shows in the portal, including when something did not land.
Who asked, who agreed, what went out. History stays with the request, with no later reconstruction.
Price per company
In every plan: all processes · hosting · onboarding · no per-person or per-request fee.
PLN 4.50 per person at 100 people. Less than one email to IT.
From PLN 1.50 per person. Support and training on the same invoice.
A fixed amount after we size you up. No per-seat price list.
QUESTIONS
No. We join additively: the portal reads existing permissions and adds new ones. We do not remove anything we did not grant.
Opposite — that is a typical starting point. The portal first shows who really has access. Cleanup is a separate decision after you see the list, not a prerequisite.
The narrowest set needed for the operations you enable. You get the full list in writing before signing. If you do not enable leave, the app does not ask for calendar access.
We check that on a call. Sync scenarios are supported, but grant order can differ and we want that clear before the contract, not after.
Permissions stay — they live in your systems, not ours. You get an export of request history; we remove the app from the tenant.
Whoever is accountable for that matter and whom you name at onboarding: a manager, a project owner, or someone in IT. The portal does not dictate who that is.
If it works and nobody complains, keep it and we connect the rest. Value appears when leave lives in one tool, access goes by email to IT, and cover lives nowhere. Then one window with one approval saves more than a leave module alone.
Both, each their part. HR sets who approves leave and the rules. IT names resource owners. Employees see one window and do not need to know who configured what.
Helpdesk finishes where we start. The ticket closes, but someone still had to open the Microsoft console and click by hand. Here approval is execution: after the owner clicks, nobody enters anywhere. If you have JSM, we can keep it as the intake and plug in underneath as the layer that executes.
Contact
Company, headcount, which matters still bounce by email between staff, HR and IT. We call or write back. Aclovo is run by Interactive Workspace Sp. z o.o.
Interactive Workspace Sp. z o.o.
+48 451 522 320
contact@interactive-workspace.com
interactive-workspace.com
