Outsystems incident
Incident affecting Personal Edition Users – Post-Login Permissions Issue
Outsystems experienced a major incident on November 26, 2025 affecting Identity & Access Management, lasting 10h 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Nov 26, 2025, 11:19 AM UTC
We are currently investigating an issue affecting a subset of Personal Edition users. Some users are seeing a “no permissions” message after signing in. Our team is actively working to identify the cause, apply mitigation for impacted users, and continue monitoring the situation closely. We will share an update as soon as more information becomes available.
- identified Nov 26, 2025, 02:43 PM UTC
We have identified the root cause of the issue affecting Post-Login Permissions for Personal Edition users. Some customers may still experience a “no permissions” message after signing in. Our team is actively working on a solution, and we will provide an update as soon as more details are available
- resolved Nov 26, 2025, 09:01 PM UTC
We have successfully applied a manual fix for the Personal Edition users who reported the “no permissions” error; access for these accounts has been restored. Regarding other affected users who did not submit a report, we have sent a dedicated communication to your registered email address with further details. We will continue to monitor the system to ensure stability.
- postmortem Dec 10, 2025, 11:17 AM UTC
On November 26th, an issue was experienced affecting Personal Editions users, resulting in users seeing a “no permissions” page and being unable to use their Personal Edition environments. Normal service was restored at 21:00 UTC. The incident was caused by the reconfiguration step used to fix an earlier issue. This step correctly re-applied the Identity Provider \(IdP\) but also unintentionally made the affected Personal Editions environments available for re-assignment. As a result, many of the previously fixed Personal Editions were re-assigned to "second" users who were created without any permissions upon first login, leading to the “no permissions” screen. To prevent new occurrences, all Personal Editions environments created during the faulty period that had gone through the reconfiguration were discarded. Impacted users were proactively informed and instructed to request a new Personal Edition.