Вашою мовою цієї сторінки поки немає. Ви читаєте англійський текст.
Knowledge base
Read the workspace history
Who can open it
The record belongs to the workspace, and the server hands it to the Owner and to an Admin. If you work alone, the workspace is yours and the list opens for you.
A Manager, an Operator or a Member sees, in place of the list, that only the workspace owner and admins can see its history, with a See who they are button that opens Members, where the roles are listed. Signed out, the screen asks you to sign in first, and without a connection it says you are offline.
How a line reads
The newest event stands at the top. A line gives the date and time, the event in words, the profile after a dot and, on the right, the email of the person who did it.
Above the list the screen says how many events are shown out of how many exist. The server does not trim old lines by age, so Show more keeps going back to the first event of the workspace.
- 1
Open the History tab
In the left column, between Protection and Extensions.
- 2
Read from the top
The list starts with the most recent event.
- 3
Press Show more
The button under the list, while older events remain.
What gets written down
Profiles: Profile created, Profile edited, Profile deleted, Profile restored, Profile opened and Profile closed. Proxies: Proxy added, Proxy edited, Proxy deleted and Proxy password taken.
The team: Team invite sent, Invite accepted, Member removed, Left the team, Left the team: account deleted, Member role changed and Group access changed. The account: Signed in, Locked after wrong passwords, Device connected, Device unlinked, Plan changed, API key created, API key revoked, Account deletion requested and Deletion cancelled by sign-in.
Automation and extensions add Flow saved, Flow deleted, Schedule saved, Schedule deleted, Extension enabled and Extension disabled.
Whose events these are
The members of the workspace write into one shared record, and a line names its author by email. A line without an email has no person behind it that the server can name.
When someone leaves or is removed, their lines stay with the workspace and they stop reading its history. What a newcomer did in another team does not come with them. Someone who left by deleting their account is shown as Left the team: account deleted, and their sign-ins leave the list together with their IP addresses.
Edits with before and after
Under a Profile edited line the screen lists what changed. The name, scenario, fingerprint template, group and proxy come as before and after, with an arrow between them.
A proxy shows its address without the login or password. A field that was empty before shows a dash.
Notes and tags stay private
One kind of event at a time
The History screen is one list with no filter or search. An Owner or an Admin who needs one kind at a time opens Members, where Logs splits the same record into Actions, Profile sessions and IP log.
Profile sessions keeps only openings and closings, and IP log shows sign-ins and connected devices with the address and country. Previous and Next move through them page by page.
The history of one profile
The profile menu has Profile history. It shows the launches, closes and running time of that profile on this computer.
For the owner and admins it adds rows from this record: edits made on any computer, and opens and closes on other computers, with the email of whoever did it. An open that took the profile over names the machine it was taken from.
What this does not do
- It does not record what happens inside a profile: the pages it opens, what is typed there or its cookies.
- It does not record a launch made while the program was signed out or could not reach the server.
- It does not record a flow run or a schedule run. Saving and deleting them leave lines, the runs themselves do not.
- It does not filter or search on the History screen. Splitting by kind lives on Members, for an Owner or an Admin.
- It does not show what notes and tags were changed to, only that they were changed.
Where this is decided
Each claim above is one place in the code and one stand.
- A plain member of the workspace does not read the history
- apps/server/test/audit-filters.js
- A member without the right sees who can read the history and is led to Members, and each server event has a label in words
- apps/desktop/test/история-и-защита-в-окне.js
- A removed teammate's lines stay with the owner and still name who did them
- apps/server/test/team-money-seats.js
- Notes and tags are written as the fact of an edit, and a save with no change leaves no line
- apps/server/test/было-и-стало.js
- The screen shows before and after, and a private field only by its name
- apps/desktop/test/история-показывает-правки.js
- The list does not stop at the first batch: Show more fetches the next page
- apps/desktop/test/window-really-works.js
Questions
- The screen says only the owner and admins can see the history.
- That is right: the server hands it to them only. See who they are opens Members, where each person's role is shown, and the owner or an admin can change your role there.
- Yesterday's launch is not in the list.
- Press Show more first, because the list arrives in batches. A profile opened while the program was signed out or offline leaves no line.
- A line shows a code instead of words.
- That is an event the program has no words for yet. It is shown as it came rather than hidden, so you still see that something happened.
- Does a removed teammate's history disappear?
- No. Their lines stay with the workspace, with their email next to them.
- Can I see which sites a teammate visited in a profile?
- No. The history records what was done to profiles and to the account, not what happened inside the browser.
Next to this
Invite a teammate
How people get into the workspace in the first place.
Decide who sees which profiles
The roles that decide who reads this screen.
Working as a team without shared passwords
Why roles and a record replace one shared login.
Three warnings from your own log
Patterns the server picks out of the same record.
Look at your own history
The free plan gives two profiles, with no time limit and no card.