Every account, license and credential exists because a person joined the company. Mekovault ties that origin to what the person holds in each platform, and closes it when they change roles or leave the organization. With evidence.
Origin: payroll
P. Riquelme 路 Design
Last day in the organization: 2026-09-30
What usually happens without governance: email gets closed and nobody looks at the rest again. Names and platforms are examples.
Email is closed the same day. But the design license, the Slack seat, the card-paid subscription and the shared account that person managed stay alive. Each one is a monthly charge and an open door.
Slack, Figma, Adobe, Canva or Zoom never learn the person is gone. The seat stays assigned and the invoice keeps coming, month after month, until someone notices.
With governance: the exit runs across every connected platform and the report shows what was released and how much you stop paying.
Shared accounts were managed by one specific person. When that person changes roles or leaves, nobody knows who holds the password or who answers for them.
With governance: every shared account has an owner and, on exit, Mekovault asks for a new one before closing anything.
The credential that connects payroll, billing or the CRM was created by someone under their own user. If that person is gone, the integration keeps running under an identity nobody controls.
With governance: service credentials are stored encrypted per company, with an owner, an expiry and a record of every use.
A tool contracted by a team renews automatically even when nobody uses it anymore. The invoice goes to the email of whoever bought it and nobody else sees it.
With governance: Software Purchases records every license with its billing period, warns 30 days before renewal and asks for the invoice every month from the right person.
Governance is not a policy in a PDF. It means every account has a reason to exist, someone who answers for it and a record of what happened.
The onboarding request defines what the person gets. Role changes and exits come from the same place: HR requests it and Mekovault executes it on time, without going through Support.
Who requests, who approves and what runs on its own is defined once per role: HR, Support, Purchasing, Treasury, Audit. Nobody needs to be granted access: they have it because of what they do.
Who requested, what was done, on which platform, when and from where. 365-day audit trail, an exit report per person and a full export for auditors.
Four moments when an account is born, changes or ends. In each one Mekovault knows what to do because the data comes from the origin.
HR registers the person with their role and date. The accounts and licenses they are entitled to are created on day one, with the cheapest license that fits.
HR requests 路 Mekovault executes
What no longer applies is released and what is new gets assigned. Per-seat tools are requested through Software Purchases, with manager approval by email.
The manager requests 路 approves by email
Block on the last day, email forwarded, licenses released on every platform, shared accounts reassigned and subscriptions under that person reviewed.
HR requests 路 exit report with the savings
Scheduled deletion with grace days, temporary reactivation if needed, renewals flagged 30 days ahead and an invoice reminder every month.
Automatic 路 with notice to the right people
Shared accounts and the credentials systems use to talk to each other are the easiest to forget. Here too there is an owner, an expiry and a record.
Accounts and credentials with an owner
| Account | Type | Owner |
|---|---|---|
| soporte@tu-empresa.cl | shared account | c.mena |
| ventas@tu-empresa.cl | shared account | a.rojas |
| API 路 facturaci贸n | service credential | Finanzas |
| Integraci贸n 路 BUK | service credential | Personas |
When a person leaves, Mekovault lists what they were in charge of and asks for a new owner. Example data.
Not one more tool for IT. It is where every area finds the answer they ask for by email today.
Licenses per platform, unused seats, savings from exits and monthly reports without asking anyone.
Onboarding, change and exit from one form. It runs on the date and gets recorded. No Google console, no tickets to Support.
Tool requests with manager approval, purchase order, Treasury and invoice reminders. Nothing renews without someone seeing it.
Immutable 365-day log with IP and browser, an exit report per person and a full export. What an auditor asks for already exists.
Connect your Google Workspace in an afternoon, upload your payroll (or connect BUK) and the Leak Map shows you, with the monthly cost, which accounts and licenses are still being paid for people who are gone.