ELO Permissions

The permissions concept was not planned but grew organically until it got incomprehensible. It had to be analyzed, simplified, implemented, and documented.


Between 2013 - 2018.

What was it all about

The permission system, which had grown over the years, needed a refresh. This required precise documentation of the current status in order to then develop a simplified concept.

What was my part

I had a driving role in simplifying the concept. I tested our software, and researched and documented any issues and discrepancies. I then organized meetings so that informed decisions could be made, and took care of the necessary to-dos for the developers to implement the changes. I documented the new concept and held a very well attended webinar. This showed how relevant the topic was.


TestingDocumentationTrainingTo Do ManagementProduct Owner role

Microsoft OfficeELO Java ClientELO Windows ClientELO Administration ConsoleELO IndexserverELO Modules

What I learned

The way things, even software, grow organically. Observing this process, understanding the intrinsic behavior in our software, and the logic of developers. Asking anybody difficult questions and please check the code for me, to find out how a certain behavior was implemented.

What I liked the most

Having an overview in a time in which nobody else had. I could help make the software easier to use and build a frame for easier future decisions.