Files
wekan/docs/Features/Admin-Panel/Problems/Offices.md
T
Lauri Ojansivu b7589737f5 File docs/Features the way the WeKan menus are.
A feature's guide now sits under the menu it is used from, read from the
templates rather than from where somebody once put it: Header-Bar,
All-Boards, Pages, Board-Header (search and every Board View), Board-Sidebar
(Board Settings, Filter, Members, Labels, Archive), Rules, Swimlanes, Lists,
Cards, Member-Settings, Admin-Panel and Login-Page. Topics used from several
menus (editor, history, theme, translations, email, troubleshooting) are in
General.

- Each area has a README mapping its menu entries to their guides and to the
  template or server module that implements them. Board-Header/README.md
  lists all 40 Board View entries with the template boardBody.jade renders;
  five views (Table, Calendar Mode, Time, Timeline, Map) have no guide of
  their own yet and say so.
- Board-View.md listed 25 views while BOARD_VIEWS has 40; it now lists all
  of them with their English labels.
- Pages keep their file names. Where a released changelog links an old path,
  a "# Moved" page stays there and points to the new one; test-menu.sh skips
  folders holding only those.
- Undo was filed under Login; it is General/Undo now.
- Every link in docs, code comments, scripts and tests follows the move;
  docsLinksResolve checks them all.

Tests that read a doc follow it to its new place. boardViewSettings now fails
when Board-View.md or Board-Header/README.md differs from BOARD_VIEWS, or
names a template boardBody.jade does not render.

Thanks to xet7 !
2026-10-16 23:45:35 +03:00

858 B

Admin Panel / Problems / Offices

Open Offices to review successful login counts by person and address. Each person's addresses stay together. Rows can show IPv4, IPv6, first/last login times and location information when available. A shared address may represent an office, VPN or NAT; it is not proof that accounts are one person.

Location information comes from the configured trusted proxy/CDN headers. Missing information remains unknown. An IPv4/IPv6 pair is only shown when the server has evidence linking the addresses; an address alone cannot establish someone's precise physical location.

This is an administrator report of locally recorded login activity. Its implementation does not require sending login addresses to an external geolocation service. See Problems and account lockout.