Blog Security
Access that never expires is access still live three years later
Nobody decides to grant access forever. They just do not set a date, which is the same thing under another name.
Why everything ends up open-ended
Think about the last time you gave someone access. There was probably a rush, it was probably for something specific, and there was probably no field asking until when. In most tools open-ended access is not a decision — it is the only option offered.
And there is a psychological reason reinforcing it. Setting an expiry forces you to estimate how long something will last, and estimating is tedious and carries the risk of being wrong. Easier to leave it open and assume it will get closed.
It does not get closed. What happens is the access outlives the reason it was granted for, sometimes by years, and nobody notices until there is an audit or an incident.
What should always carry a date
Not every access needs an expiry. The useful distinction is whether it is tied to an open-ended relationship or to a piece of work with an end.
- Contractors and suppliers. The engagement has an end even if you never wrote one down. Set the expected end date — renewing is trivial, forgetting is not.
- Support access. When a vendor needs to come in and look at something, they need to come in today, not in 2029. This is the clearest case and the most frequently ignored.
- Integrations and automations. A key created for a specific migration or a one-off script should die with it.
- Temporarily elevated access. Someone covering a role during leave. These are the worst, because the elevated permission stays and eventually nobody remembers why that person sees what they see.
How keys with expiry work
Fichaloto API keys take an optional expiry date. Past that date the key stops authenticating: nobody has to remember, and nobody has to go in and revoke it.
Two more behaviours are worth knowing because they cover the two habitual failures. A key can be revoked in one click without touching any other, which is what lets you react fast without breaking someone else's integration. And a key always belongs to a person: if that person moves to inactive, the key stops working on its own, with nobody needing to remember that this particular contractor had one.
That last point is what solves the real case. The offboarding problem is not that you do not know how to revoke — it is that you do not remember there was something to revoke. Tying the credential to the person makes the forgetting harmless.
Periodic review is not a substitute
The standard answer here is «we do an access review every quarter». Good, and you should, but it does not solve the same thing.
A review hands you a list and asks you to judge, one by one, whether each access still makes sense. That is cognitive work, done in a hurry, and the natural bias is to leave everything as it is — because removing access that was needed creates a visible incident and leaving it creates nothing visible at all.
An expiry date inverts that bias: the default is closed, and keeping it open takes a deliberate action by somebody who knows why. It is the same difference as between a subscription you have to renew and one you have to cancel, and we all know which one persists.
Frequently asked questions
What date do I set if I do not know how long it will take?
Three months, always. Long enough not to get in the way, short enough that the access does not outlive the project. Renewing takes seconds and forces you to look at it, which is exactly what you want to happen.
Is it not disruptive if access expires mid-work?
The first time, yes, and it is a small disruption next to the alternative. What reduces the friction is warning before the date and making renewal one click for whoever has the authority, rather than an email that takes two days.
What about access that lives outside the product?
There is no technical shortcut there: hosting panels, FTP, third-party accounts. What works is noting them with their end date in the same place you keep the person's record, so you are not relying on memory. Less elegant than automatic expiry, and the difference between knowing and assuming.
All of this is built into Fichaloto. See how it works.
Keep reading
Security
«Why can Ana see that?» is a question your HR software should answer
Anybody who has administered SuccessFactors knows the screen. Everybody else has spent an afternoon clicking through roles trying to work out where a permission came from.
Security
The access list nobody maintains and everybody needs
The uncomfortable question is not what they had access to. It is how they could still get back in, and almost nobody can answer that with confidence.
Security
Five fields, written at the moment you grant it
Recording access takes thirty seconds when you grant it and an afternoon when you try to remember it.