DeskGate practical help

Connection and Login Logs

Use connection and login records to investigate a specific access question with the right time and account context.

Define scope

Verify configuration

Review the result

Before You Begin

Provides context for the recorded connection workflow; it is not a substitute for screen recordings.

Helps review access events. Interpret the actual result recorded rather than assuming every entry represents a successful sign-in.

You can trace the relevant access event to a defined period and scope, or explain why the available data does not answer the question.

Open Connection Logs for recorded connection activity or Login Logs for authentication activity. Select the source that matches the question.

Choose the available date and search filters. Confirm the time convention shown by that page before comparing another source.

Inspect the available account, endpoint, event and status details. Separate an attempted action from a successful outcome.

Compare the relevant administrative audit or security alert when needed. Record the evidence and review outcome without exporting unrelated data.

Check the selected log, dates, filters and the availability of source records.

Check UTC versus local-time labels and reporting boundaries before correlating events.

Review the account and event context, then follow the security investigation process rather than assuming an attack from a count alone.

Are login logs and administrative audit interchangeable?

No. A login event and a later administrative operation answer different questions.

Does an empty view mean nobody connected?

Not necessarily. Filter scope, retention and available records affect the result.

What should I send to support?

Provide the page name, time range, sanitized identifiers and error details. Do not include passwords or unrelated employee records.

Bring your device scope and the question you want to answer. Review the relevant capabilities in a guided demo.