ThirtyFileLogs and branding
See what happened, and make the site look like yours.
Logs
Open Control panel › Activity log.
| Log | Records |
|---|---|
| Activity | Uploads, edits, moves, deletions, sharing and changes to settings |
| Share link access | Who opened a link, password attempts, previews and downloads |
| Sign-ins | Successful and failed sign-ins, sign-outs (including devices signed out from Devices), password changes, two-factor sign-in (wrong codes, recovery codes used, turned on, off or reset), and app passwords created, removed or tried with a wrong secret |
| Errors | Errors people ran into: requests the server couldn't complete, and errors the web page hit (a page that broke, an upload, preview or file operation that failed) |
Filter by person, action and date, and export the result as a CSV file that opens in Excel. The file uses the names and the language you see on the page, and your time zone.
The activity log is for administrators, and for space managers in the space's properties (This PC). Everyone else sees the recent activity of a file or folder they can open in its details pane.
Entries about other people's personal spaces say who did what and when, but not to which file or folder: the item and the details are left out (What administrators can see). The search and the CSV export leave them out too, and so do the share link access log for links in those spaces, and archive files.
Everyone can see their own sign-in history and signed-in devices from the account menu. See Your account.
Errors
The Errors tab is for administrators. Each entry says when it happened, who ran into it (or Not signed in), where it comes from and what was being done. Click the time to see the details: the kind of error, the request's status, a request ID, the version, and a stack trace for errors of the web page.
- Server entries are requests the server answered with an error. Unexpected failures (a database or storage problem, a request that took too long) are errors. Changes it refused (a name already taken, no permission, a file too large) are warnings. Filter by Severity to see one or the other.
- Web page entries are sent by the page: a page that broke, an uncaught script error, and failures it showed during uploads, previews, saving and file operations.
- When the page reports a failed request the server already recorded, the two are joined by the request ID into one entry, with what the page showed under Reported by the page.
- The same error again within 10 minutes adds to the entry's count instead of adding another entry. Reports are limited per person and per minute, so a page stuck in a loop can't fill the log.
- Names of files and folders are left out: text in quotes is replaced with
"…"(or「…」), the page reports the server's English message rather than its translation, and requests are recorded by their route (PATCH /api/nodes/{id}), never by the path asked for. Passwords, cookies, share link tokens and file contents are never recorded. The full text of a server failure is in the server's log (docker logs), under the same request ID.
How long logs are kept
Under Control panel › Log settings:
- Activity and share link access are kept for 180 days, sign-ins for 365 days. Errors are kept as long as activity.
- Older entries are moved to compressed archive files, which are kept for 3 years and can be downloaded from the same page. An archive has one JSON entry per line, with the codes the log keeps (
upload,bad_password) and times in seconds since 1970 (UTC), the same in every language. - Recording visitors' IP addresses and browsers can be switched off.
Branding
Open Control panel › Branding.
- Name and logo, with an optional second logo for dark mode. The logo is also the icon in the browser tab.
- Colours for light and dark mode.
- Appearance: light, dark or following each person's device, and whether people may change it.
- Sign-in screen: the background picture, the texts, and whether the lock screen is shown.