We were wondering if there might be a way, from within the application, to manage users more easily, both new useres and deletions. The problem is that some users are assigned to several databases with different roles, so:
in the case of add users, we must go through each database one by one and assign them a role. This could be managed more easily if we had an interface like the one for choosing forms in the reports section, where we could choose the database and then the role, and, if applicable, the parameters/conditions assigned to each role.
in the case of delete users, the idea is to be able to have (at least for technical contacts) a list of all users of the application within the application (I’m not talking about the Excel file that can be exported), so that when we deregister them, we would deregister them from all the databases they were working on.
This would make management much easier, as we currently have to go through each database one by one and delete the user. If there were records (for example, with the “user” field) linked to him/her, the system could alter them so that we know that this data would be deleted and then decide whether to change his/her role to “inactive.”
Hi @emanuele.lini_medico for removing users at the organization level, we’re working on this. We are adding a central page for managing users across all databases, which would include a “Revoke all” action to remove them from all databases that they have access to.
This could also be an automation target, so that when a user is removed from Microsoft Entra/Active Directory, they would be automatically removed from all databases. Because you are using SSO, these users are already blocked from logging in, but this extra step will also remove them from the database (and free up a license).
You can also ask your IT team whether they would be willing to grant the ActivityInfo application the User.Read.All Graph API permission. That would allow us to periodically poll your directory to see if any users have left the organization and remove them automatically.
For adding users across multiple databases, that’s something I don’t think we had thought of, but I can see it makes sesnse for admins who might have responsibility for several databases. If you do find yourself adding users to several databases regularly, you might consider merging the databases if they are used by the same group of users.