Give the people a place, then discuss the projects
Imagine a studio preparing a booking flow, a client portal and a website refresh in the same week. Company rooms belong to members. Open a person’s room to see their recent agent task states, then move to the next room without rebuilding a mental map from separate terminal windows. Running, waiting and finished work have visible places in that view.
The rooms show generated task labels and metadata, so the project story still comes from your team and your existing delivery tools. Company does not expose client task titles, create client-specific permissions or isolate repositories. Keep client access, source control and project ownership in the systems that already govern them. Use the room as the start of a focused conversation with the person doing the work.
Make the handoff deliberate
Ask teammates to use Send to manager for review when a completed task needs a lead’s attention. The resulting orange Manager review state stands apart from ordinary ready and working states. That is useful when one person is finishing a routine adjustment and another is waiting for a decision about the next client demonstration. Both can be finished locally while needing different next steps.
Open the metadata, contact the task owner through your normal team channel, and review the actual change and evidence together. Mark metadata seen acknowledges the shared task record. Client acceptance, code approval and release decisions remain separate. This makes a lead’s acknowledgement useful without confusing it with permission to ship.
Set up seats around the actual team
Choose how many Team seats you want before checkout. Every owner, manager and member uses one seat at $14.99 USD per month. For example, a studio with an owner, two additional managers and nine members needs twelve seats, totaling $179.88 per month before tax. The owner and managers can code in their own Office as well as use the company view. They do not appear as member rooms.
Plan for people who are already active and invitations still pending when changing the seat count. Team billing is separate from personal billing, so an existing personal VibeiDE subscription continues until canceled. Provider subscriptions also remain separate. The useful budgeting question is how many people need a seat, not how many agent desks happen to be visible at a particular moment.
Make joining understandable
Team settings supports generating invite links. Each link is single use and expires after three days; it can also be revoked. Share it with the intended teammate through your existing channel. Acceptance explains that room sharing starts enabled before the person joins. Members can later turn sharing off, and managers can see that preference in the roster.
The invitation workflow also includes an email option when the hosted mail service is configured. The generated-link path gives you a concrete invitation to use independently of email delivery. Keep one invitation per intended recipient, account for pending invites in your seat planning, and remove or revoke access when a collaboration ends through the appropriate owner controls.
Keep Friday’s review small enough to use
Start with the default ten rooms per floor. You can choose from one to forty, but an agency lead working on a laptop may prefer smaller floors and a few deliberate room visits. Floors organize the display; they are not client security boundaries. A denser floor can require more scrolling, so choose the size that makes the next person and next handoff easy to find.
Use Finished today and the weekly daily counts to open recent completion metadata. Shared data covers a rolling seven days, grouped into UTC days. Counts represent completed execution attempts, not billable hours, client deliverables or production releases. Build the client update from verified changes and delivery records, using Company to find which teammate and recent work to follow up with. That is a Friday routine a growing studio can keep understandable.
Explore Engineering managers: give finished agent work a clear next step, Your AI coding agents deserve an office, One operator workspace for multiple client repositories.