Sometimes, particularly when we take responsibility for something, it's tempting to put up barriers of one kind or another that stop other people from (intentionally or accidentally) messing it up.
We put fences around our yards, use a key to start our car and protect our digital information with passwords or PINs. As long as these don't get in our way (we forget our password or lose our key), we hardly notice them. For the most part, we have achieved a healthy balance between granting access to those who need it (my son has a key to my car) and blocking access to those who don't (my neighbour does not).
This balance is important to keep in mind if you are a Team Admin for your ABAKiS Program Team. When you first start, your default access level will be "General", meaning you can access everything. This unrestricted access is ideal for when you are just getting started and learning how everything works, but you will quickly want to add restrictions for new team members (including yourself).
Of particular interest is the "Data Entry" role. Similar to the "Interventionist", this allows a team member to enter data either during session or directly after. But this role also has additional controls specifically designed for easily adding or editing historical data.
On the one hand, it's really useful to have someone on your team who can go back and correct possible recording errors. Or perhaps you have months of data stored in binders that you want to include in the progress charts for reference and completeness. Assigning the "Data Entry" role to a team member makes it possible for them to do this quickly and easily.
Of course you also want to be careful. The more people who have the ability to make changes to past data, the more errors are likely to be introduced (whether accidentally or, less likely, maliciously).