One space, one set of records
Thogits is a shared workspace. You invite friends or co-workers to the organisation. They land in the same space. They see the same database. They open the same pages.
That is the whole model. There is not a private copy per person. There is not a maze of per-record permissions. Everyone in the space can see the data.
If that sounds blunt, it is. This is for small, high-trust teams — a shop, a crew, a founding pair, a studio, an agency pod. People who already talk. People who should be looking at the same tickets, invoices, and notes.
What sharing actually means
Invite someone. They get the space.
- Same records: clients, jobs, invoices, whatever you track
- Same pages: lists, boards, dashboards the assistant has built
- Same assistant in the product, working those records
- Changes sync across web and iPhone, and feel instant
You stop asking “what’s the latest?” in a group chat. The record is the latest. If someone updates a status on their phone, the board on your laptop shows it.
Thogits is built for operating together on typed records. Invite the people doing the work. One space. Same jobs, invoices, and pages.
Honest about what we do not do
No roles, no per-record ACLs
We do not ship role matrices. We do not ship per-record access lists. We do not sell a permission tree. Everyone in the space can see the data.
Invite the people doing the work. They get the same records and the same pages. One space. No permission tree to babysit.
That matches how small teams and small businesses actually run. The bottleneck is usually “nobody can find the current list,” not “we need twelve permission roles.”
How work lands in the shared space
People can:
- Use a page, the way they would use any internal screen
- Chat with the assistant
- Email or call the assistant so a record gets created or updated without opening the laptop
- Set a reminder so the follow-up is not only in someone’s head
Automations run on a schedule against the same records. Integrations and the API write into the same space. The team does not maintain a second copy.
Start from a template if you want a shared system on day one. Or describe the work and let the assistant build the types and pages, then invite the crew.
Who this is for
Founders who are still the ops team. Operations leads who want one board, not five spreadsheets. Friends running a project who are tired of a shared doc that nobody updates.
It is not for a 400-person company that needs departmental silos. It is for the group that should all be able to see the work.
Try it
Create the organisation, put real records in, and invite one person who already asks you for the latest list. See Features, check pricing, or sign up and share the space.