Three warnings from your own log

Nothing new is collected from you. Two of the three warnings come from sign-ins and profile starts already in your log, over the last thirty days.

The third comes from today's profile list instead, because a cluster on one address is a fact about how your profiles sit right now rather than an event that happened.

• Sign-ins

  Who signed in and when, with the address they actually came from and the country, where a country is known at all.

• Profile starts

  A profile you opened through the server. If the server was out of reach, your window opens but nothing lands in the log.

• Today's profiles

  The name and the exit address of each profile that has not been deleted.

Either the person travelled or the password is in somebody else's hands. Both are worth the same day rather than the week when profiles start vanishing.

Your usual country is your own, not the team's. A colleague living in Poland does not make an Argentine sign-in normal for you, and a first sign-in never raises anything: a newcomer has no usual country yet.

Platforms take a cluster of accounts on one address together, and they need no simultaneous logins to find it. Three profiles is still work; four on one exit is where the line sits.

You see profile names for the three heaviest clusters, so thirty identical lines never bury the one worth reading.

Accounts signing in together read as one script behind all of them, whatever the names on them say. Five starts inside a minute is the count that warns you.

The count alone is not enough, so the pace matters too. A pack is a burst only when the smallest gap between two neighbouring starts falls under two and a half seconds.

The panel heads your dashboard and the app's Members screen, and is absent when there is nothing to say.

A line cannot be dismissed. The cluster line goes when you spread the profiles apart; the other two go on their own when their entries fall out of the window.

• Most urgent first

  A possible stolen password stands above the housekeeping lines, and equally urgent lines stand newest first.

• Admin and owner only

  Reading the log is their right. A manager, an operator or a member sees none of these lines, and the panel stays quiet rather than breaking.

• Through the interface too

  You can pull the same lines through the interface with a key allowed to read logs, and both toolkits carry it.

A line tells you the shape. What actually happened you read in the log, three ways over one set of rows.

1. 1

   Actions

   The whole workspace newest first, with the email of the person instead of an internal id.

2. 2

   Profile sessions

   Only the starts and stops of browser windows: the view behind a burst and behind who was working when.

3. 3

   IP log

   Sign-ins and machine registrations with the address, the country and the machine name.

Each of the three asks a different repair, and no browser setting does it for you.

1. 1

   A new country

   Change the password, turn on the second sign-in step and look through the linked machines.

2. 2

   A cluster on one address

   Spread those profiles over more addresses, or keep the cluster knowingly for accounts meant to sit together.

3. 3

   A burst of openings

   Open through the queue or a schedule, so a morning arrives spread out instead of in a row.