Office
See where your team is and what is waiting on you, on a live office floor
Overview
The Office shows your workspace as an office floor. Each person on your staff sits at a desk in their team's pod, takes lunch in the break room and a break on the lounge sofa, and drives out when they head to a customer. The board, the TV, and your own desk show what is waiting.
The main floor uses timers, visits, approved time off, and the statuses people set for themselves. An admin can also connect Zoom, Microsoft 365, and Slack so calls, meetings, and lunch breaks show up on their own (see Automatic status). Core never tracks anyone's location. The manager Portfolio floor combines project records, check-ins, Asana tasks, and imported time.
Opening the Office
Open Office from the sidebar or visit /office. Every staff role with Office access can open it without enabling experimental features. Customer portal users never see it.
The Office fills the window, without the app's sidebar or top bar; Back at the top of the tool rail on the right returns to the page you last visited. If you opened the Office directly, it opens the dashboard. The main floor needs a screen at least 1024 pixels wide. On a phone, a tablet, or a narrower window, it opens as the list view. Portfolio provides its project roster and inspectors on smaller screens.
A small animated Office scene covers the page for five seconds each time you enter while your saved floor and its data load underneath. Each floor loads its scene, data, and live updates only when selected. Your last choice is saved to your account for this workspace, so returning to /office restores it after a reload or in another browser. An explicit floor link opens that floor and updates your choice.
On the main floor, you can pan, zoom, and fit the room after the cover clears. On a slow connection, any remaining data continues loading. Walking to a break or meeting and arrival gestures play at a slower pace so you can follow the movement; onsite departures and returns take three times longer than indoor movements. Reduced-motion behavior stays brief, and visit times and road travel estimates stay unchanged. Historical SLA numbers load separately in the background, so they do not hold up the rest of the Office. Pending counts stay unknown until their data is available. If data cannot load, Try again reloads the page.
Portfolio floor
Workspace managers and administrators can choose 5 Portfolio beside the main floor's elevator views. The same entry appears above the Office list on smaller screens. Portfolio keeps the shared Office top bar with 5 selected. Choose 1–4 to go directly to that Office view; the chosen floor is remembered for your account.
The Delivery Studio places the eight projects with the highest recorded attention needs on its workbenches across all visible operating units. Mixed bays are labelled Mixed operating units. The top bar's project picker replaces the main floor's staff-team picker. Open Choose projects to search and select the projects to show, or choose an operating unit inside the picker. The workbenches, rooms, and roster follow this selection, and existing company access still applies. Search projects opens the complete roster within the current selection. Search names, check-in summaries, next steps, concerns, and contract titles, or filter the roster by project manager.
Select a workbench to see its manager, delivery target, linked contract dates, source records, and latest check-in. Choose Add check-in to record a summary, next step, reported health, who the project is waiting on, and whether a decision is needed. Select Save check-in to save; closing the form does not save it. Check-ins are attributed and audited without sending notifications.
The Portfolio dispatch noticeboard opens queues for decisions, blocked or at-risk reports, waits, missing updates or owners, passed delivery targets, mapping items, and contract dates that need review. Counts describe recorded concerns; zero does not confirm project health. Lamps use only health from check-ins within seven days. Historical requests retain their report dates. Contract review checks linked terms and current coverage; a missing end date alone is not a warning. The Decision desk collects explicit decision requests. The Waiting bay collects recorded client, vendor, or internal dependencies. The Contract library opens linked contracts and their dates; delivery targets remain separate from contract terms. Missing information and check-ins older than seven days show Needs update. Open the project to see the previous report and its date.
Open a project to retrieve its linked Asana tasks, including owners, due dates, completion, milestones, and dependency references. The task summary shows retrieved completion, overdue open tasks, unassigned open tasks, and the next open milestone. Partial retrieval is labelled and counts apply only to retrieved tasks. Task details load only while the project is open. Missing connections, provider failures, and incomplete task lists are shown explicitly. A dependency reference alone does not mean the task is blocked.
The project also shows recorded hours, including imported Everhour hours, within your existing time-entry access. The panel identifies whether you can see all, team, or only your own entries. Hours beside tasks include all recorded sources; the Everhour total is shown separately. Historical Everhour entries may lack task links, so project hours can exceed the hours assigned to tasks. New imports preserve these links, and eligible imported entries receive them when refreshed. Running and paused timers are excluded. The latest Everhour work date is a calendar date, not the time of the last import.
The Source updates cabinet explains what is available. Core supplies project and contract records and labels their refresh time. Asana shows the last project import when recorded. Everhour import freshness is unavailable here, and Slack messages load on project open. The neutral On project open trays describe when evidence loads. Asana task evidence is retrieved when a linked project opens; its retrieval time does not establish project health. On your first Portfolio visit, Core prompts you to connect your own Slack account; Not now lets you continue. You can connect, reconnect, or disconnect later in Source updates. Your personal connection follows your Core account across browsers and never grants another manager access to your Slack messages.
Inside a project, paste a Slack channel link or channel ID and select Read project messages. Core checks your current Slack identity and channel membership, and reads up to 50 channel posts from the last 30 days. Direct messages and thread replies are excluded. The channel mapping is private to your account. Possible blockers, decisions, and delivery dates are prompts for your review, rather than established project health.
Select Review as check-in to edit an excerpt. Health starts as unknown. Approve sharing the reviewed excerpt with authorized project managers, then select Save check-in. Core rechecks your access to the source message before saving and retains a source link. Reading or reviewing a message never publishes it. Private evidence clears when access changes or a refresh fails. Check-ins and their reported health remain explicit manager reports. The floor refreshes while visible and when you return online, and pauses automatic refresh while an inspector is open. Refresh is also available.
Portfolio data is restricted to managers and administrators and is never shown in the Office wall-display mode. Wall displays always open the main floor without changing your personal floor choice. If you lose Portfolio access, /office returns to the main floor.
Choosing teams
Open the team selector in the floor's top bar or above the list to pick one or more teams. Your selection is saved for your account and applies to both views, including live refreshes. Only teams you have permission to read appear in the picker; private teams stay subject to their existing access rules. When only one team is available, its name appears without a picker.
Your first visit shows your own specific teams. If you belong only to the workspace's default team, that team is shown. Choose All teams to include all visible staff, including people without a team. If all your saved teams become unavailable, the Office falls back to your current teams. If you have no current team, choose another team or All teams to restore the people view.
The people count, field visits, and clocked-in count follow your selected teams. Ticket counts, SLA figures, and your attention queue retain their existing permission scope.
Day and night
The floor automatically switches to night after sunset and returns to daylight after sunrise, independently of your app theme. Sunrise and sunset are seasonal estimates for the reference city in your browser’s timezone, so they may differ from your exact location. No location permission is needed. Timezones without a reference city use 6 AM to 6 PM for daylight. Checks are scheduled near sunrise and sunset, and pause while the tab is hidden.
Choosing your look
Open My look on the floor’s tool rail or above the list to customize your character: skin tone, hair color, hair style, and shirt color. Until you save a look, colleagues see a stable suggestion based on your account. After you save, everyone sees your choice on their next Office refresh.
Choosing your vehicle
Open My vehicle to load the vehicle picker. On your first choice, a suggested vehicle is selected. Choose a Cybertruck, Off-road Pickup, Classic SUV, Camper Van, Basket Bicycle, Sport Motorcycle, or Classic Cruiser. Select Save vehicle to save your choice. Closing the picker leaves your saved choice unchanged. If saving fails, the picker stays open so you can retry.
Change your choice through My vehicle on the floor’s tool rail or above the list. Your vehicle follows you on the road and at customer sites, with your workspace’s branding on cars and vans. Colleagues see it on their next Office refresh.
Parking shows saved vehicle choices for the selected teams. The garage has up to eight bays, and the small overflow lot draws up to three cars. Select the +N vehicles sign to open the full searchable vehicle list, including staff beyond the floor’s display limit. When there is no overflow, the sign reads Vehicles. The overflow lot sits to the right of the office; the vacation beach stays on the left. Cars belonging to staff on vacation, sick, or in the field leave their office parking spaces, including staff beyond the floor’s display limit. A car stays in the lot during its owner’s normal working hours, and outside those hours only while they are actively working, so the lot empties on nights and weekends. A vehicle keeps the same chosen model on the road and at its owner’s customer building.
The picker is available to every staff member who can open the Office, including people who cannot set a status. It is hidden on an office TV.
Working hours
Your normal working hours tell the Office when you are usually in. Set them in Working hours on Settings → Profile: switch on each day you work and choose a start and end time. Times use the time zone on your profile, or the workspace time zone if your profile has none. Select Use workspace hours to go back to the workspace business hours, which apply to anyone without their own hours. To change your hours, at least one day must be switched on.
Your reporting manager, a manager or lead of a team you are on, and workspace admins can also change your hours from your team member page.
Places and activities
Each person has a place (where they are) and an activity (what they are doing there).
| Place | When |
|---|---|
| Out | Approved out of office, vacation, company event, or company travel; they set their status to Away, Errand, or Sick; a Slack status that says they are sick; or Teams, their Outlook calendar, or Zoom shows them out of office and nothing shows them working (a running timer, a visit they are on or driving to, Teams or Zoom showing them active, or a status they set in Core such as Focus, Remote, Lunch, or Break). Approved time off and Away, Errand, or Sick always put them out |
| Customer site | They tapped Arrived on a visit and have not tapped Done; their calendar shows a busy event right now at a customer's address or site, or with the Onsite category; or they have an active scheduled visit, labelled Scheduled with arrival unconfirmed |
| On the road | They tapped On my way on a visit and have not arrived, or they are on company travel while working |
| Break room or lounge | They set their status to Lunch (a break-room chair) or Break (the lounge sofa), or their Slack status reads as lunch or a break. When one is full, people sit in the other |
| Phone booth | They are on a Zoom Phone call, Zoom shows them on a call, or Teams shows them in a call, and no meeting places them (see Calls and phone booths) |
| Meeting room | They are in a Zoom or Teams meeting or presenting, Teams shows them busy, or their calendar shows a busy event right now (in the booked room when the event books one); they are on a call during their own calendar meeting or a meeting they are invited to; or approved training time (the room's sign reads ) |
When more than one applies, the first row in the table wins.
People on vacation or otherwise out of the office sit in lounge chairs at the beach beside the left wall of the office, under a palm tree. Select a person or their name to see their full status, for example Vacation through Fri or Out of office today. The beach seats up to 12 people; select +N more to see and select the remaining colleagues.
People who set Sick or whose Slack status says they are sick stay on the compact infirmary board along the mailroom’s solid wall. Select a posted name for their full status, for example Out sick today. If the board fills, select +N more to see the remaining names.
| Activity | When |
|---|---|
| Presenting | Zoom or Teams shows them presenting |
| Call | Zoom or Teams shows them on a call |
| Meeting | They are in a Zoom or Teams meeting, or their calendar shows a busy event |
| Lunch or Break | They set that status, or their Slack status reads that way |
| Focus | They set Focus, or Zoom or Teams shows Do not disturb (Teams also Focusing or Urgent interruptions only) |
| Working | A timer is running. Their laptop shows the ticket or project if you can already see that time entry |
| Paused | A timer is paused |
| Idle | No timer, but they did something you can see in the last 30 minutes, Zoom or Teams shows them Available, or they turned off status sharing |
| Away | Nothing to go on, or they are out. Away, Be right back, Off work, and Offline in Zoom or Teams count as nothing to go on |
On the floor, a red light over a desk means something is waiting on that person, and your own name tag is gold. Remote (their own Remote status, or a calendar event marked Working elsewhere) and On call (approved on-call time) are badges on the person's card and in the list view, not on the floor.
An Away desk has an empty chair. You can still select its name to see the person's status. Activity and ticket alerts appear together, for example Lunch · 2 alerts; the alerts describe tickets that need attention.
Select a person with a red light or a waiting pin to see Needs attention. Each item shows its title, why it needs attention, and a link to open it. These links open the waiting item even when the person is working on a different ticket. Your own card shows your current attention queue; colleagues' cards show readable SLA issues and items from your queue that involve them. Other people's private inbox items are not shared.
Labels follow the seat: someone on a break shows as Lounge, and someone at lunch as Break room.
Long names, statuses, customer and client names, and team names are shortened on the floor. The full text is in the hover text, the accessible name, and the inspector.
SLA streak board
The Days without breaching SLA sign sits beside the Switchboard queue board, before the lounge TV. It counts completed days in your workspace's timezone; today and days with a recorded response or resolution breach do not count. An active breach resets the current counter to zero.
The header is red at 0 days, yellow at 1–10 days, and green at 11 days or more. Unavailable counts (—) keep a green header.
Best recorded is the longest streak found in retained SLA tracking, including resolved tickets. It is not an all-time record: deleted tickets and policy changes can remove historical evidence. The figures follow your SLA and company access, independently of the selected teams. Missing, incomplete, or unavailable history shows — rather than a made-up streak.
Select the sign, including when it shows 0 or —, to see why. An unresolved breached ticket holds the counter at 0, even while paused; pausing stops the clock but does not clear an existing breach. The details link to the contributing tickets you can read and show which SLA target was missed. A zero can also mean no full clean day has elapsed since tracking began or the latest recorded breach. A dash distinguishes loading, missing permission, unavailable history, and a failed read; it never establishes that there are no breaches. The panel shows up to 50 contributing tickets, gives the total when more exist, and links to the SLA dashboard. Wall TV display mode keeps the sign read-only.
Wall-mounted boards sit on solid wall. Windows remain in the unobstructed sections.
Trophy case
Select the trophy case on the west wall beside reception to see five-star Core ticket surveys. It opens on the past 30 days; choose Past 7 days, Past 30 days, or Past 90 days to change the period. Each review links to its ticket. The panel shows up to 50 reviews, newest first, with the total for the selected period. You need feedback access, and only surveys for tickets you can read appear.
The case stays decorative until opened. Survey details and counts never appear on the floor or office TV.
Project Room
The wooden Project Room beside the typing pool shows projects worked on in the past 24 hours by people on your selected teams. Up to four project boards appear on the floor. Select the room to see the recent project list, each project's status, and when work was last recorded. Select a project to open it.
Personal Internal projects, PTO and holiday projects, and each company's default ticket project are excluded. Work from people who turn off Office status sharing is also excluded. Your existing time-entry, project, and company permissions still determine what you can see. Changing the Office team selection updates the people and projects together.
Recent work updates on the next full Office refresh, within about 90 seconds while live updates are connected. Everhour imports contain a work date rather than an exact work time, so their placement in the rolling 24-hour window is approximate.
Meeting rooms
The floor has three meeting rooms, all labelled Meeting room. A room in use shows its meeting's title on its sign and at the top of its details when the meeting's details are shared. Long titles are shortened on the floor and shown in full when you hover over, focus, or select the room. A private meeting, or one without shared details, shows In a meeting. A room holding more than one meeting shows how many (for example 2 meetings), and approved training shows Training. A wall TV never shows meeting titles on room signs: there a room in use reads In a meeting or 2 meetings, training included.
People in the same meeting share a meeting room:
- Everyone whose Outlook calendar shows the event, with its details shared, as busy right now.
- Colleagues Teams or Zoom shows on a call, in a meeting, or presenting who organize or are invited to exactly one meeting already on the floor. Their attendance is not confirmed, so that meeting's title and end time never appear on their own status.
Private copies, free/busy-only copies, declined invitations, room resources, hidden attendee lists, and invitations to more than one meeting on the floor never group anyone. A presenter placed by Teams or Zoom keeps the room the event booked.
A meeting booked in a Microsoft 365 room shows that room's name only in its details: the person's Room row, the room's Room row, and the meeting's Location. When more meetings are on than there are rooms, the extra ones share the last room instead of joining another meeting's room. Statuses don't name a room; they read like Presenting until 11:30 AM.
Calls and phone booths
Someone on a plain call stands in a phone booth facing you with a handset to their ear, and the dot on their name tag becomes a small phone. Phone booths have a blue frame, a felt panel, and a desk phone, and PHONE BOOTHS is painted on the floor in front of them. When more people are on calls than there are booths, they share one.
Teams shows people in a Teams meeting as In a call. So a call during your own calendar meeting, or during the one meeting on the floor you are invited to, puts you in that meeting's room, drawn as an attendee and still marked On a call. A meeting you join during your own Out of office block counts too, unless it is private. A call with no meeting is a phone booth, and so is a call during a busy block with no invitees, room, or online meeting, such as time you blocked for ticket work.
If something is waiting on someone in a phone booth or a meeting room, the red light stays at their desk and their name tag keeps showing their status. Their person card still lists what needs them.
Customer sites
Across the full bottom edge of the office is a row of client buildings. When someone taps On my way or is onsite at a customer, that customer gets a building with its name on a sign on the side wall. Long names are shortened; hover or focus for the full name and who is there, for example 2 onsite · 1 on the way.
An active scheduled visit also places the person at the customer's building, labelled Scheduled. Arrival is unconfirmed until they check in, and scheduled visits do not increase the confirmed onsite count. The people summary shows these separately as scheduled in the field. An all-day visit covers the workspace's local day; a timed visit covers its start and known estimated duration. Time off and check-ins take priority.
Vehicles use each technician's chosen model. Cars and vans show your workspace's saved branding on the side; bicycles and motorcycles keep their original artwork. The wrap follows each vehicle in the garage, on the street, and at customer sites. Short names appear with the logo icon; longer names use a larger icon. When only a full logo is available, the wrap uses that logo. If an image cannot load, the vehicle shows a readable name or initials.
- Everyone at one customer shares one building. The people onsite stand apart outside it so their names remain visible. Up to two vehicles park in separate driveway spaces, using each technician's saved vehicle choice. Vehicles also appear while an active scheduled visit places someone there; those people remain labelled Scheduled until they check in.
- Someone on the way drives a truck along the street toward the building, tagged like Jakin → Acme. The truck is timed from On my way with the same straight-line estimate as the field map, and waits just short of the building until Arrived. With reduced motion the truck stays still.
- When a technician taps Arrived without On my way, you see them walk to the garage and drive off first. Their truck parks at the customer once it has left the garage.
- A customer from an Outlook event (busy, at a customer's address, or with the Onsite category) gets a building and the onsite person's preferred vehicle too. Its tooltip identifies it as a calendar site; it has no visit link. Outlook events that match no customer share one Customer site building.
- When there are more customers than buildings, the last building reads +3 more sites (with your number). Select it to list them; people at those customers show as tags beside it.
- Buildings keep their place while their customer stays active, including when an Outlook event and a visit to the same customer come together. The row is always there, so the floor view never jumps.
Select a building (its sign, or the building itself) to see who is onsite and on the way, when they arrived (for an Outlook building, since when the event has run), when the others should arrive, when their visits were scheduled, and Open visit for visit sites.
People on the road without a truck on the street (company travel, a customer in the +3 more sites building, or more than eight trucks at once) hang as a tag by their garage bay, for example Kai · on the road. Anyone without a bay of their own is tagged on the apron in front of the garage, never on a colleague's truck. When many people have no bay, the apron tags stack like the door board: eight rows, then the rest cascade in a small pile.
The docked list's Field tab also lists people onsite from their Outlook calendar, with a calendar icon, the pill Onsite, and Customer site when no customer matched. Choosing someone onsite there, or in search, selects their customer's building. Search also finds the customer named on someone's Outlook onsite event. If today's visits couldn't load, the tab says so above any people it still lists from their Outlook calendar.
Status key
One color per status is used everywhere in the Office: chips, the list view, map pins, and the key under the cards.
- Working: a timer is running on a ticket or project.
- Needs you: something waiting on you involves this person: a notification, an SLA, or an approval.
- Paused or idle: at work without a running timer: a timer is paused, or they were active in Core recently.
- Call or meeting: on a call, in a meeting, or presenting. On the floor, someone in a phone booth has a phone-shaped dot.
- Focus: focusing. Hold questions until they are done.
- Away: out, at lunch, on a break, or nothing from them in the last 30 minutes.
- In the field: on the way to a customer, at one (a visit or an Outlook onsite event), or on company travel.
Select an entry in the key, or the status pill in the inspector, to read what it means (click, tap, Enter, or Space). The dots also differ in shape, so they read without color: needs-you dots are diamonds, and paused dots are pause bars.
The top bar and cards
The top bar has search, the floor switcher ("9 of 14 in · 2 onsite · 1 on the road"), the elevator stops, the Live pill with the clock, the count of items waiting on you, and your own chip. Three cards sit under it:
- Open tickets: with today's change and the unassigned count.
- In today: people in out of everyone, with how many are onsite, on the road, at lunch, or on a break (for example "2 onsite · 1 on the road"). It counts staff in the selected teams, up to 1,000 people. If field data couldn't load, it says Field count isn't available, and the top bar shows no field counts.
- SLA on time: the share of SLA tickets resolved on time in the last 30 days. It needs permission to read SLA data; without it, or when the data can't be read, the card says SLA data isn't available. With no SLA tickets in that time, it says No SLA tickets in the last 30 days.
The floor draws up to 200 people. In a larger workspace, the docked list and search say Showing 200 of 250 people (with your numbers), and the list view shows everyone.
Staying up to date
The floor updates live, and refreshes everything every 90 seconds as a backup. When you come back to the Office (for example with Back, or after resizing the window), it catches up right away. Changing the team you see also counts as a refresh.
Select the Live pill (it shows the clock) to see when the floor last refreshed, how quickly each kind of change arrives, and a Refresh button:
- Changes made in Core (tickets, assignments, visit check-ins, statuses people set): within seconds.
- Zoom and Slack, if connected: within seconds.
- Teams and Outlook, if connected: checked every minute.
- Timers, time off, and inactivity: at the next full refresh, every 90 seconds.
The pill changes when the floor is not live:
- Reconnecting…: the live connection is down. Live updates are paused, and the floor refreshes every minute until it is back.
- Updated 10:42: the last refresh failed, so you are looking at the floor as it was at that time. The next refresh that works brings it back to Live.
- Session ended: you were signed out. Select Sign in to come back.
On a wall TV the pill is display-only.
Sometimes only part of the Office can't be read. That part says so, for example Couldn't load the queues. or Couldn't load today's visits., instead of looking empty. A count Core couldn't read shows — instead of 0, and a short list that only partly loaded shows its count with a plus, such as 3+. The next refresh that works fills them in. This applies to the floor and to the list view.
Ticket tracker
When you select someone working on a ticket, the ticket tracker appears at the bottom left of the floor. It shows the ticket's lifecycle: Received (with where it came from), Triaged, Assigned, In progress, Waiting on customer (only when it happens), and Resolved, which shows the SLA due time.
A step the ticket keeps coming back to, like each wait after a customer reply or a reassignment, shows once with a count (for example 3×). Select any step that happened to see every time it happened, who made the change (for Assigned, who it was assigned to), and when it ended. If a ticket changed hands without a record of it (for example when someone was offboarded), Assigned shows the current assignee with Time not recorded. A resolved ticket's Resolved history says whether it met or missed its SLA. A step's history opens in a small panel; press Esc to close it. Times from today show the time; earlier days show the weekday or the date (with the year for dates from another year). Steps the ticket skipped are dropped first when the history is long.
The card next to the strip shows the ticket's current status (for example Customer Note Added) and opens the ticket. The tracker isn't shown in the list view, on small screens, or on a wall TV (?display=1).
Setting your status
Open the status menu:
- In the Office: select your own chip at the right of the top bar, or press
S. - In the list view: select Set my status at the top.
- Anywhere else in Core: select Status beside the version number in the sidebar footer.
Only people who can set a status get the menu: staff with a team member record, with experimental features on. For anyone else, the chip in the Office only shows their name.
| Status | Lasts |
|---|---|
| Lunch | 45 minutes |
| Break | 15 minutes |
| Focus | 60 minutes |
| Errand | 60 minutes (you show as out) |
| Remote | Until midnight in your own time zone |
| Sick | Until midnight in your own time zone (your name hangs on the infirmary clipboard) |
| Away | Until you clear it |
You can add a note of up to 40 characters. The status ends on its own and your character walks back to the desk. Choose Clear status to end it early.
The same menu has the Share my status, Share subjects from other integrations, and Office sounds switches (see Opting out).
Automatic status
Zoom, Microsoft 365, and Slack can keep people's places up to date without anyone setting a status. Each source is optional and experimental, an admin connects it once for the whole workspace, and it only covers people who are matched to a staff member.
| Source | What it adds |
|---|---|
| Zoom | Zoom Phone calls and Zoom "On a call" (phone booth, or the meeting's room during their own calendar meeting or a meeting they are invited to); Zoom meetings and presenting (meeting room); Do not disturb (Focus); Out of office (Out); Available, Away, and Offline |
| Microsoft 365: Teams | Calls (phone booth, or the meeting's room during their own calendar meeting or a meeting they are invited to); meetings, conference calls, presenting, and Busy (meeting room); Do not disturb, Focusing, and Urgent interruptions only (Focus); out of office (Out) only while Teams shows them offline, and not when the only Out of office event on their calendar right now is an invitation someone else sent (with automatic replies on while they are signed in, Teams' normal status is used, and Away or Be right back reads as Away); Available, Away, Be right back, Off work, and Offline |
| Microsoft 365: Outlook calendar | Out of office events they organized (Out; an Out of office invitation someone else sent is ignored); Working elsewhere (the Remote badge); busy events at a customer's address or site, or with the Onsite category (customer site, labeled with the customer's name); any other busy event (meeting room, in the booked room when the event books one). Tentative and free events are ignored (an invitation you have not answered counts as tentative) |
| Slack status | A status that clearly reads as lunch (break room), a break (lounge), or out sick (infirmary clipboard) |
Zoom calls and meeting joins usually arrive within seconds. Teams presence and Outlook meetings are checked every minute, so a meeting usually shows within a minute of its start. A Slack status arrives only when Slack sends it; there is no backup check. An automatic Out never outweighs signs that someone is working (see Places and activities). A newer Slack Lunch or Break also takes precedence over an older Zoom Out status. Refreshing the same Zoom status does not make it newer. Every automatic status ends on its own within 10 minutes unless Core keeps hearing it, so nobody gets stuck in a meeting that is over. A Slack lunch or break lasts until the Slack status ends, or 45 minutes (lunch) or 15 minutes (break) when it has no end time, and never longer than 2 hours (lunch) or 1 hour (break). Out sick lasts until the Slack status changes or ends. With no end time set in Slack, it stays until the person changes or clears their status; with an end time, it never lasts longer than 14 days.
Meeting details and guests
Select a person or meeting room to see the current meeting's subject, organizer, invitees and their calendar responses, start and end times, duration, location, online status, and a plain-text description preview. Join and Outlook links appear when the calendar provides them. Up to 100 invitees and 2,000 characters of preview text are shown; larger meetings show the additional invitee count.
Microsoft 365 shares these details only for events explicitly marked normal, while the person shares their status. Private, confidential, personal, and unclassified events show only a coarse status. Hidden attendee lists stay hidden. Meetings with no readable calendar details keep their generic status.
Invited guests appear as people around the room's table. They are calendar invitees, not confirmed live attendees. Declined invitations and room resources do not create guest figures. Guests do not count toward staff totals or gain staff actions.
On the floor, the meeting title appears on the room. People show their names above their figures, without repeating the meeting title. Guests show a shortened display name, with Invited or Organizer on a separate muted line. When the calendar has no display name, or gives an email address as the name, the name is built from the address (for example abigail.moore@example.com reads Abigail Moore); an address inside a name is dropped. A guest with no usable name is labelled Guest. Guest labels have a dashed outline because an invitation does not confirm who came, and they shrink to a dot when the room is crowded. Guests take only free places in the room; when it runs out, the first guest's label shows how many more are invited (for example +6). Select the room to see every invitee's full name and address. Email addresses never appear on the floor or on the wall TV.
What Core keeps
Core keeps one temporary status per person and source. For non-private Microsoft 365 events, it also keeps the shared meeting details above. Source freshness expires within 10 minutes, separately from the event's actual end time. Ending the status, turning off status sharing, unmapping a person, or disconnecting the integration clears the stored details. Temporary status rows are deleted within a day.
Core does not store HTML meeting bodies, attachments, phone numbers, call counterparts, Zoom meeting topics, or raw provider status text.
Opting out
Both switches are in your status menu (see Setting your status). Share my status is also on Settings → Profile, under Office status sharing, for every staff member, with or without experimental features. Only you can change them.
- Share my status: turn it off and every source skips you, and any automatic status and meeting details already shown for you stop showing. See Opting out of status sharing.
- Share subjects from other integrations: on by default. Turn it off to hide meeting subjects supplied by status integrations other than the Microsoft 365 calendar (Zoom meeting topics, Teams presence, and Slack status don't include subjects today). Non-private Microsoft 365 calendar details follow Share my status and event privacy instead.
Who can connect
Owners, super-admins, and admins can connect and manage these sources: their roles include managing integrations, and Core checks that permission again on every connect, sign-in return, and change. Like the rest of the Office, the sources need experimental features turned on for the person connecting them (see Turning it on). Without it, the Office presence section, the Slack page's Office status from Slack card, and the Zoom and Microsoft 365 pages do not appear, and agents connected through MCP do not see these sources in their integration list.
Where to find them, with experimental features on:
- Owners and super-admins: Settings → Integrations → Office presence has a card for each source with its connection state.
- Admins: the Integrations settings tab is only for owners and super-admins, so admins open each page directly: Zoom, Microsoft 365, and Slack (the Office status from Slack card).
If a settings page can't read the connection, it says Couldn't load the connection. Refresh to try again. rather than showing the source as not connected.
Zoom
Early access: until Rooted's Zoom app passes Zoom Marketplace review, only Rooted's own Zoom account can connect. To use Zoom in your workspace, contact us and we'll help you install it.
- Open the Zoom page (see Who can connect) and select Connect Zoom.
- Sign in as a Zoom account admin and approve Core's access for your Zoom account.
- Core matches Zoom users to staff by exact email. Under People, check the matches, select Match by email for any new ones, and choose a staff member for any Zoom user Core could not match (no email, or an email shared by more than one person). Core never changes a match on its own.
- Use Test connection at any time.
One Zoom account can connect to one Core workspace. Core checks up to 200 matched people per workspace every minute.
If Zoom stops accepting Core's connection (for example, the app was removed in Zoom, or Zoom's authorization expired), Core stops checking Zoom within a minute, deletes the stored tokens and matches, clears Zoom statuses, and the page shows Zoom was disconnected with Connect Zoom to start again. Disconnect asks Zoom to remove Core's access (if Zoom does not confirm, Core tells you to remove the app in Zoom yourself), deletes the stored tokens and matches, and clears Zoom statuses. Connecting again matches by email again, so redo any matches you made by hand.
Microsoft 365
Early access: until Rooted finishes Microsoft publisher verification, Microsoft shows the app Core by Rooted as unverified when an administrator approves it. Contact us if you need help approving it.
- Open the Microsoft 365 page (see Who can connect) and select Connect with Microsoft 365.
- Sign in as a Global Administrator or Privileged Role Administrator and approve Core's read-only permissions for your organization.
- Sign in once more as a Global Administrator or Privileged Role Administrator of the same organization (not a guest) so Core can confirm which organization approved and that an administrator did. If your role is eligible in Privileged Identity Management, activate it first.
- Select Match by email, then map anyone else by hand under People.
- Use Test connection to see each permission as granted or not.
Core asks for four application permissions, all read-only:
| Permission | Used for |
|---|---|
User.Read.All | Listing directory users to match them to staff by email |
Presence.Read.All | Teams availability and activity |
Calendars.Read | Free/busy, show-as, privacy, times, location, and categories of current events, and whether the person organized each one, plus the subject, organizer, invitees and their responses, a plain-text preview, and meeting links, which Core keeps only for events marked normal. The invitees also let a colleague Teams shows in a call or meeting join the room of a meeting they are invited to. Microsoft's permission allows reading whole events in every mailbox; Core requests only these fields and never requests HTML bodies or attachments. An Exchange application access policy can limit it to some mailboxes |
Place.Read.All | The meeting room list, read once a day, so a meeting booked in a room shows that room's name in the Office |
One Microsoft 365 organization can connect to one Core workspace. If Microsoft stops accepting Core (for example, consent or Core's permissions were removed in Entra ID), polling stops within a minute, Core removes matches, statuses, and rooms for that organization, and the page says Microsoft 365 was disconnected; select Grant consent again to reconnect. A connection that is stored but turned off shows Reconnect needed; Grant consent again fixes that too. Disconnect stops polling and removes matches, statuses, rooms, and calendar change subscriptions; if part of that cleanup fails, the page says so and refreshes, and you can select Disconnect again. Your organization's consent stays in Entra ID until you delete Core by Rooted under Enterprise applications.
Slack status
Slack status is off by default.
- Connect Slack first (see the Slack guide).
- Open the Slack page, find Office status from Slack, and turn it on.
- Select Link accounts by email. Core links a Slack account when its email matches exactly one staff member and never changes an existing link.
Only a status that clearly reads as lunch, a break, or out sick counts, such as "Lunch", a coffee emoji with "back in 10", or "Out sick". Meetings, calls, focus time, vacation, travel, and every other status are ignored. Turning the toggle off, removing Slack, connecting a different Slack workspace, or uninstalling Core from Slack ends every Slack status in the Office right away. Turning it on can take up to a minute to take effect everywhere.
Slack status needs no new Slack permission: it uses the users:read scope Core's Slack app already has. No reinstall is needed for most workspaces: once Rooted updates Core's Slack app to send status changes, they reach existing installs. If statuses still do not show after you turn it on, select Reconnect Slack on the same card.
Visit check-in
Technicians assigned to a visit can tap three buttons on it:
- On my way: you show as on the road.
- Arrived: you show at the customer site. The visit moves to In progress when the first assigned technician arrives.
- Done: you head back. The visit is completed when the last assigned technician taps Done.
Each tap is recorded once, at the time Core receives it, so Done asks you to confirm first. Once someone has tapped, only a manager or admin can reassign the visit. If you arrived at a visit yesterday and have not tapped Done, it stays in Your visits, marked "Yesterday", for the rest of today.
Core does not record your location when you tap these buttons. Owners, admins, managers, and technicians can check in; members and observers cannot.
Mailroom
The Mailroom is at the front left of the floor. When a new ticket arrives, its robot receives an envelope, stamps it, then sends it through the tube. With reduced motion, it shows a still receipt instead.
Beside the robot, recent automated activity shows what was recorded, such as Assigned to Fay, Priority set to High, or Sender needs review, with a link to the affected ticket. When activity settles, the last recorded action stays visible. Select Mailroom or press P to open today's intake and recent activity; select an action's ticket link to open that ticket. The open panel refreshes when new tickets or automated actions arrive.
Keyboard shortcuts
| Key | Action |
|---|---|
| Arrow keys | Pan the floor (at the Bullpen, ← and → step between pods) |
Arrow keys, Home, End on a person | Previous or next person, or the first or last (Shift with an arrow still pans) |
+ / - / 0 | Zoom in, zoom out, fit |
1 to 3 | Elevator: the Big Board, the Floor, or the Bullpen |
4 | Open my desk (the Blotter) |
Q / G | Open the Switchboard (ticket queue) or the T-card rack (field dispatch) |
P / W | Open the mailroom or the watercooler |
People are one stop for Tab: once you are on a person, the arrow keys, Home, and End move between people. Esc, or closing a panel, puts focus back on the selection, or on the floor when nothing is selected.
Open my desk (Blotter) on the tool rail does the same as 4. Sound is off until you turn it on.
What waits on you
N steps through your queue in this order:
- Notifications that need your response.
- Your tickets that have breached their SLA, then those at risk.
- Core AI waiting for your confirmation.
- Unassigned tickets, if you can dispatch.
Customer replies appear once per ticket while its status is Customer Note Added or Customer Replied. Handled, closed, archived, merged, or inaccessible tickets leave this queue. Office also respects the Inbox's read, done, snooze, and Mark all read controls.
Your agents in the Office
If you connected an AI agent such as Claude to Core (Settings → Agents), it works from a desk in the typing pool. Only you see your agents, and you never see anyone else's. An agent appears while it is working for you (a tool call in the last 10 minutes) and leaves the floor when it goes quiet.
Its tag says it's yours and what it did: Your Claude · last: search tickets, or Your Claude · update ticket for a few seconds when a new call arrives. Agent writes run immediately, so nothing waits on your approval. When an agent changes something, a capsule travels through the tubes to your desk.
Agent activity reaches the floor on the next refresh, within about 90 seconds while live updates are connected. Select an agent's tag to open the typing pool: every agent you connected, idle ones included, when it last made a tool call, whether it can only read (Read only) or can also make changes (Read and write), and its last tool calls.
The Mailroom shows recorded ticket actions from workspace automations, Core AI, and scheduled work, with links to the affected tickets.
Core AI in the Office
When your workspace has an AI key, the Core AI button sits at the bottom of the tool rail on the right, and ⌘. (Ctrl+. on Windows) opens it as it does elsewhere in Core. When Core AI asks you to confirm something, the item waiting on you reads Core AI is waiting for your confirmation; opening it opens Core AI. While Core AI is working on your request, its helper sprite at your desk shows what it is doing. Core AI's helper is different from your connected agents: it appears beside your desk only while Core AI is answering you in this tab. In the list view, the Core AI button sits at the top, next to Set my status.
List view
/office?view=list shows the same people as a table grouped by place and team: name, place, activity, what they are working on, and how long. It is what the Office shows on screens narrower than 1024 pixels (phones, tablets, and narrow windows), and it is the view to use with a screen reader.
- The status key at the top spells out what each color means, and Status private marks people who keep their status to themselves.
- The In the field card splits the count into onsite and on the road, and people at customer sites are grouped by customer, with a count.
- On a phone, each person has one actions menu with their links.
- Updated shows the time of the data you see, with a Refresh button. While the list is on screen, it refreshes itself every minute, and Your visits today refreshes with it. If a refresh fails, or the page can't reload after you check in, the list stays as it was, Your visits today included, and reads Couldn't refresh. Showing the list from 10:41 AM. (with that time) until a refresh works. If only your visits couldn't refresh, the visits you had stay and the list says they may be out of date. If your session has ended, it says so and offers Sign in, which brings you back to the same view. If the Office is no longer available to you (experimental access was turned off, or your role changed), it says so and links back to the dashboard.
Press L, or the list button on the floor's right-hand rail, to make the list your default view; Show the floor switches back. The links under the docked list open the list once without changing your default. The floor remembers where you left the camera on each device.
Who sees what
Everyone who can open the Office sees each person's place and activity. Every active staff member appears, including people who have not turned the Office on for themselves. Detail follows the access you already have:
- Ticket or project on a laptop: owners, admins, and billing roles see everyone's; managers see people on teams they lead; everyone else sees only their own.
- Waiting items: you only see beacons for tickets you can already read.
- Automatic status: everyone who can open the Office sees the place and activity it produces, the name of a booked Microsoft 365 room (in details), and the customer's name for a calendar event at a customer. Non-private Microsoft 365 meeting details appear while the person shares their status; other integrations' meeting subjects appear unless the person turned them off.
- Agents: only the person who connected an agent sees it on the floor and what it did. Admins and teammates don't.
Opting out of status sharing
If you turn off Share my status, in your status menu or on Settings → Profile, colleagues see you idle at your desk, and so do you. Your timer state, your self-set status, and any automatic status from Zoom, Microsoft 365, or Slack stop showing, and those sources skip you until you turn sharing back on. Turning sharing off also ends any status you have set, and you cannot set a new one until you turn sharing back on.
The Office shows everyone on staff, including people who have not turned on experimental features, so the switch on Settings → Profile does not need them.
Approved time off and visits still show, because colleagues can already see those on the calendar and the dispatch board. People who can already read your time entries, such as admins, still see them on the Time Entries page.
Billing roles
Billing and Billing Admin users can open the Office, but they cannot read teams, schedules, or availability. For them:
- Everyone sits on the open floor instead of in team pods.
- Visits and the field map are empty, so technicians on visits appear at their desks. Only customer buildings from Outlook onsite events show across the street.
- Approved time off does not show.
They do see SLA counts and SLA warning lights, because SLA status comes with ticket access, and they see what people are working on, because they can already read all time entries.
Display mode on an office TV
Open /office?display=1 for a TV. The floor fits the screen, including the street and the client buildings, with the field map beside it. Names and TV numbers are larger, and the view moves to new beacons and completed tickets on its own. There is no status menu, look picker, vehicle picker, or Core AI on a TV. Agents don't show on a TV, and room signs never show meeting titles.
Nobody is there to press Try again, so a TV looks after itself: if the Office can't load at first, it tries again every 30 seconds and shows the countdown, and once loaded it reloads itself after 5 minutes without fresh data.
To set up a TV:
- Invite a dedicated user with the Observer role.
- As an owner, turn on Experimental Access for that user (see Turning it on).
- Sign in as that user on the TV and open
/office?display=1.
The Observer role can see places, activities, teams, visits, and time off, but not which ticket or project someone is working on.