User Login Activity

[Mukesh_Kumar]

Is there a report/Query or something through which I can get "Use Login Activity".

When was the last time user/s logged into MEGA?

How frequently they logged in?

Duration of Login?

What activities were performed?

[aseph]

Hello @jhorber, 

we are in V5 now and where we can get this information as @Mukesh_Kumar asking about

this is my supervisor version. Thanks!

[foleyjff]

Any update on this?  Pretty basic admin function required of most systems.  Who logged in, when, etc.  

[AHassan]

Hi,

Is this still not possbile to extract a report with user's login activity e.g. last login information for all the users?

Regards,

Asim

[ColruytTeam]

Hi Mukesh,

you could also use a script that would write a text file each time a user connects to MEGA.

You could use a macro  similar to this one :

Sub lastUserAccess()

  Dim macroGlobals, pathFile, strInfo, userName, fso

  pathFile = <pathToYourFile>
  nomUser = getObjectFromId(megaEnv.getCurrentUserId).getProp(​"short name")
  Set fso = CreateObject("Scripting.FileSystemObject")
  Set myFile = fso.OpenTextFile(pathFile, 8, True)
  myFile.WriteLine(username & ";" & megaEnv.getRoot.name & ";" & Date())
  Set myFile = nothing
  Set fso = nothing

End Sub

lastUserAccess

Then, create a MetaCommand linked to your "Repository" metaClass and connect it to your macro.

Every time a user connects to MEGA, it will be logged in your text file 🙂

## Took solution from another post ##

Regards,

Venkatesh.

[Mukesh_Kumar]

thanks for the update. At least I got awareness on what is possible and available, on this aspect.

[jhorber · Accepted solution]

Hello Mukesh

There is not such reports/query/statistics.

Information is generated

• Log of actions performed in the repository log (internal respository log)
• Log of updates (dispatch) in environment report (megacrxx.txt)

In the future, information of this kind will also be saved in supervision logs

However this Information needs to processed/filtered and there is no standard report ready to use.

Reports would need to be designed, developped an tested specifically