# 16 octobre 2026 > Resident companies arrived, with each company's team and, in a coworking, its plan and product, along with inspection rounds in Support, where every problem found becomes a ticket. The app's navigation now opens in a new tab like any link, billing for anyone removed from the community is suspended, and the platform got new security controls. Today the coworking got two operations tools: the record of the companies that occupy the space, and the inspection round that turns each problem into a ticket. - [Resident companies](#resident-companies) - [Inspection rounds](#inspection-rounds) ## Resident companies **What it is.** The record of the community's companies, each with its team. In a coworking, the **Coworking** block stores the residence type, the company's plan and product, and the dates. One person on the team can be the **company admin** and look after colleagues without depending on the front desk. **Why it matters.** The front desk no longer keeps the list of who works for each company in a spreadsheet. The company adds and removes its own staff, and the community team sees everything in one place. Plan and product are a reference, not charged: billing is still the subscription the company buys. **Where it is.** **Administration › Members**, **Companies** tab, for the community team, and **My company**, in the account menu, for people on a company's team. **How to start.** 1. In **Administration › Members**, click **New company** and fill in the name. In a coworking, turn on **Coworking** and choose the residence type, the plan and/or the product, and the start. 2. Open the company, click **Invite** and tick **Company admin** for the person who will look after it. 3. The company admin invites colleagues by e-mail from **My company**; each one joins the team on accepting the invitation. **Example.** *Acme Tecnologia* occupies room 3. The admin registers the company as a **Private office** and invites the partner as company admin. She invites the four employees, who accept through the e-mail. When *Acme* moves out, the admin clicks **Close** and decides, in the same step, whether the team leaves too. Finance sees the Coworking block without editing; the moderator sees only the name, badge and team. See [Resident companies](/membros/empresas). ## Inspection rounds **What it is.** The walk the team takes around the building to check everything is in order, done from a phone, in the Support space. Each spot is marked **Ok** or **Problem**, and each problem instantly becomes a maintenance ticket in the queue. **Why it matters.** Nothing gets lost between the round's notes and the repair: the problem enters the queue with the description and the photo, and the room's screen in Bookings keeps the history of rounds and tickets for each item. **Where it is.** In the **Support** space, **Rounds** tab (team only). The history of each room, desk or piece of equipment is in the **History** tab of the item's screen in **Bookings**. **How to start.** 1. In the **Rounds** tab, create a **New sector** (a floor, for example) and add the spots: rooms from Bookings or free places, such as *Kitchen*. 2. Tap **Start round**, mark each spot and, on a problem, describe it and take a photo. 3. Tap **Complete round**. Anything left unmarked shows as **Pending** in the history. **Example.** At 7:40 am, the front desk walks the 2nd floor: both rooms are ok, but the kitchen light is out. One tap on **Problem**, one sentence, one photo, and the caretaker gets the new-ticket e-mail. The owner and the admin set up the sectors; the owner, the admin and the moderator walk the rounds; finance follows along. See [Inspection rounds](/espacos/rondas-de-inspecao) and [Bookings](/espacos/reservas). ## Improvements - **Cards, lists, the side menu, notifications, search and the "Back" buttons became real links.** Cmd/Ctrl+click, the middle mouse button and "Open link in new tab" now work, and a normal click still opens right away, without reloading the page. - **Companies now live in Members, work for any community and, in a coworking, store the company's plan and product.** See [Resident companies](/membros/empresas). - **Profiles no longer have the Person/Company type.** Companies are now registered in **Members › Companies**. See [Resident companies](/membros/empresas). - **Billing for anyone removed from the community is suspended.** The subscription stays on record until it is canceled. - **Profile name and photo now apply per community.** Changing your name or photo in one community no longer changes it in the others you belong to. - **Someone who already belongs to another community creates the new community's password through the invite link.** Invites, spreadsheet imports and approved community requests always send the email with **Set my password** (valid for 7 days): accounts are per community. An invitee without a name starts with the part of the email before the @. See [Invite members](/membros/convidar-membros). - New security controls. ## Fixes - The limit message when uploading several media files at once showed a placeholder instead of the number; it now shows the right limit. - The invitation e-mail when adding a member from member management is sent again. ## For developers ### API - **Resident Companies** tag: `GET` and `POST /api/resident-companies`, `GET /api/resident-companies/mine`, `GET` and `PATCH /api/resident-companies/{id}`, `POST /api/resident-companies/{id}/close`, `GET` and `POST /api/resident-companies/{id}/members`, `PATCH` and `DELETE /api/resident-companies/{id}/members/{profileId}`, `GET /api/resident-companies/{id}/invitations`, `GET /api/resident-companies/invitations/mine` and `POST /api/resident-companies/invitations/{invitationId}/accept` and `/decline`. See [Resident Companies](/api/referencia/companies). - Rounds in Support: `GET` and `POST /api/support/sectors`, `PATCH` and `DELETE /api/support/sectors/{sectorId}`, `POST /api/support/sectors/{sectorId}/spots`, `PATCH` and `DELETE /api/support/spots/{spotId}`, `GET` and `POST /api/support/rounds`, `GET /api/support/rounds/{roundId}`, `POST /api/support/rounds/{roundId}/items` and `/complete`, and the resource history at `GET /api/support/resources/{resourceId}/history`. See [Support](/api/referencia/support). - `POST /api/auth/support-entry` trades the link from Memberfy support's **Enter** for an owner session, valid only in that community. See [Auth](/api/referencia/auth/post-auth-support-entry) and [SuperAdmin](/conceitos/papeis-e-permissoes#superadmin). - The token belongs to the community: `POST /api/auth/login` takes `X-CommunityId`, the token is valid only in that community (from another community, `401`) and `PUT /api/auth/change-password` returns a new token in `data.token`. See [Authentication](/api/autenticacao). - `GET /api/auth/me` returns in `profiles` only the profile of the session's community, and `avatarUrl` is that profile's photo. See [Auth](/api/referencia/auth/get-auth-me). ### MCP: technical details - 14 resident-company tools: `list_resident_companies`, `get_resident_company`, `get_my_resident_company`, `create_resident_company`, `update_resident_company`, `close_resident_company`, `list_resident_company_members`, `invite_resident_company_member`, `update_resident_company_member`, `remove_resident_company_member`, `list_resident_company_invitations`, `list_my_company_invitations`, `accept_company_invitation` and `decline_company_invitation`. Closing, removing and declining ask to confirm; the company admin's invitation stays pending until accepted. See [Tools · Resident companies](/mcp/ferramentas-empresas). - 13 round tools: `list_inspection_sectors`, `create_inspection_sector`, `update_inspection_sector`, `delete_inspection_sector`, `create_inspection_spot`, `update_inspection_spot`, `delete_inspection_spot`, `list_inspection_rounds`, `get_inspection_round`, `start_inspection_round`, `mark_inspection_spot`, `complete_inspection_round` and `get_support_resource_history`, and the `run_inspection_round` recipe. See [Tools · Support](/mcp/ferramentas-suporte). - The server now has 437 tools and 13 ready-made recipes.