GoTerm
All guides

Teams and admin

Who did what, and what it showed

The audit log records sessions, files, sharing, sign-ins and errors, with who, on which device and from where. Recordings keep what a session’s screen showed, sealed, to watch back.

Updated

On this page
  1. How the audit log works
  2. Find something
  3. What a row says
  4. Errors
  5. How long addresses are kept
  6. How recording works
  7. Turn recording on
  8. Find a recording
  9. Watch it
  10. People are told
  11. Good to know

How the audit log works

One log for the whole workspace. Each row says who did what and when, on which device, from which address, and on which host.

The audit logone for the workspaceSessionsattached, left, endedFilesuploads, downloads, deletesSharinginvites and linksSecuritysign-ins, devices, addressesErrorsGoTerm’s and its apps’
Sessions, files, sharing, sign-ins and security, and errors all go into one audit log.
  • The organization’s owner and admins read the whole workspace; a team’s admins, their team’s hosts; everyone, their own rows.
  • Who connected from where shows to the owner and admins, to a team’s admins on their team’s hosts, and to each person on their own rows.
  • Rows stay. Only the addresses go, after the time the workspace keeps them.

Find something

  1. Open Audit log. Its tabs narrow it: Sessions, Sharing, Security, Files and Errors.
  2. Filter by Team, Host, Person, Event and When.
  3. Or search the whole log for a name, an address or a device’s ID.

What a row says

  1. Each row names who did it, on which device and that device’s ID, from which address, and on which host.
  2. Where GoTerm can place the address, its city and country show beside it.
  3. Show the details opens more, such as the file an upload stopped on, with Copy.

Errors

  1. Open Audit log, then Errors: what went wrong in GoTerm, the desktop app or a browser, and where.
  2. The same error repeating within minutes is one row, with a count.
  3. The owner and admins see each error’s full text; everyone else, its plain message.

How long addresses are kept

  1. Open Admin, then Settings, and find Connection addresses.
  2. Choose how long to Keep the addresses and their countries for, from 30 days to 2 years. A year unless you change it.
  3. After that, a row’s address, city and country are removed. The row stays.

How recording works

A recorded session keeps what its screen showed, who joined, and when they typed: never what they typed. It’s sealed as it’s written, and only its watchers can play it.

The screenand who joinsSealeda key of its ownKeptin your regionThe playerfor its watchers
The session’s screen is sealed under a key of its own, kept in the workspace’s store in its region, and opened only in the player.
  • Typing is kept as when and by whom, never what, so a password typed at a prompt stays out.
  • A recorded host’s sessions always go through GoTerm: the desktop app won’t dial it in Direct mode.
  • Recording is on Teams, kept up to 90 days, and on Business, up to a year.

Turn recording on

  1. Open Admin, then Settings. Under Session recording, switch on Record team hosts' sessions.
  2. Or record one group: on Hosts, open its … menu, choose Rename or record (Rename or limit access on Business), and under Record its hosts' sessions pick Record.
  3. Choose how long to Keep recordings for, then Save.

Find a recording

  1. Open Recordings: each one with its host, who started it, and how long it ran.
  2. Pick a Host and type Text on the screen to search what it showed, between two dates.
  3. Each match shows the line it was found on, and when in the recording.

Watch it

  1. Open a recording, or a match, and press play. Pick 1× to 8×, and Skip idle to jump the quiet parts.
  2. The Typing lane shows when someone typed. People joining and leaving show too.
  3. Opening a recording goes in the audit log.

People are told

  1. A recorded session says recorded at its top right, for everyone in it.
  2. The host list, and the page for joining a shared session, say so before anyone connects.
  3. A contractor sees it before they connect too.

Good to know

  • A team host’s recordings are watched by the organization’s owner and admins and by the team’s admins; a personal host’s, by its owner alone.
  • Recordings older than the workspace keeps them are deleted for good.
  • A change that stops a host’s recording goes in the audit log, with who made it.
  • Recordings are sealed like the Vault’s secrets: a copy of the store alone opens nothing.

Didn’t find your answer?

Write to us, and an engineer who builds GoTerm will reply.

Ask an engineer
  • Getting started

    Try the demo, add your first host and open a terminal.
  • Desktop app

    Install it on Windows, dial from your own computer, or use it free.
  • Hosts and jump hosts

    Quick connect, groups, and private servers through a bastion.
  • Sessions and sharing

    Keep sessions running, come back to them, and share them live.
  • Files

    Move files beside your terminal, or between hosts.
  • Web tabs and tunnels

    Open private pages and forward ports through a host.
  • Snippets

    Save commands once, and run them on one host or ten.
  • Monitors

    Check sites and ports, and get told when they go down.
  • Teams and roles

    People, teams, roles, host groups and each team’s activity.
  • Access and contractors

    Give a host for a few hours, and see what changed after.
  • Running a workspace

    Your address and region, colours, settings and moves.
  • The Vault and your keys

    Save, share and replace passwords and private keys.
  • Security and sign-in

    Two-factor, confirmed devices, and how secrets are kept.
  • Allowed addresses

    Open your workspace only from your office or VPN.
  • VPN only

    Open your workspace only to your own WireGuard devices.