The problem
You need to know who someone is. Role, team, how to reach them, who they report to, which customers they own. That should be one page. Instead it is a people table that nobody updates, a spreadsheet exported from payroll, and a Slack canvas with photos from last year’s offsite.
The roster spreadsheet is accurate the week you make it. Then someone changes email, a contractor starts, a person sits on two teams, and the sheet lies. A prettier table of pages is still a table of pages. The person does not know about their tickets, projects, or customers unless you maintain relations by hand.
When a new person joins, you still ask in chat: “Who owns billing?” The directory was supposed to answer that.
How Thogits is that system
You describe the directory you actually need. Thogits stores people as records and builds pages on them: a searchable list, a person page, a team roster. Those screens sit on the same records as the rest of the workspace, so a person can be a teammate, an assignee, a customer contact, or all of those at once.
A working directory for a small, high-trust team. Invite people into the workspace and they see the same directory. Everyone in the space can see the people — the roster is not a permission maze.
An assistant can look someone up in chat, by email, or on a phone call: “Who owns the North account?” “What’s Priya’s email?” It does not send SMS.
A scheduled job can remind you to review starters and leavers. It does not fire the instant a field changes.
The directory syncs across web and iOS. There is no offline mode.
What you actually use
A people directory in Thogits is usually a person record plus the things that person is already linked to.
- Person — name, role, team, email, phone, start date, manager, location, notes.
- Team or group — the bucket they belong to (ops, delivery, founders).
- Links out — tickets assigned to them, projects they own, customers they run, docs they wrote.
Pages you open:
- Everyone — search by name, filter by team or role.
- Person detail — how to reach them, who they report to, what they currently own.
- Team roster — one screen per group, not a filtered spreadsheet.
- New starter — a short form: name, role, manager, start date.
Example: you open Priya. Role: delivery lead. Team: projects. Email and phone on the page. Manager: Sam. Three open tickets. Owns project “Website rebuild.” Related customer: the account she leads. The person record is the same record the ticket tracker already assigns.
Ask the assistant: “Who should a customer email about invoices?” or “Add Jordan as a contractor on the delivery team, starting Monday.” Same directory the rest of the team sees.
Why this instead of a spreadsheet
A spreadsheet is a one-off export. It is a lousy living roster. No links, no search that understands “who owns this,” and a file that lives in someone’s Drive.
A people gallery you will not update fails the moment that person is also an assignee, a customer contact, and an author.
Thogits is the people layer on tickets, projects, and docs — not a separate roster you copy names into.
Try it
Sign up. An account is free. A new organisation starts a 30-day trial, no card required. See features, comparisons, and pricing.