ONYX1 Office
Assistants show only your own work; the owner confirms a two-step code or passkey to open other requests in Office.
On this pageFind a task
ONYX1 Office is a digital office team that does office work for you: a Chief of Staff and five specialists. They work from your ONYX1 data. You can ask a connected assistant to pass on a request, or send one from the animated Office page. ONYX1 keeps the request and result in your business record.
The team runs on an Office server that the ONYX1 team sets up for you. Settings → ONYX1 Office links ONYX1 to that server. The owner and admins can open it. Only the owner can change Office settings; an admin sees the status at the top of the page.
Find a task
- Set up the Office server, pair the Office mini or check the Office fleet.
- Write business rules and job descriptions, or see what is on the settings page.
- Choose a team member for each role or give each team member a key.
- Send a request from the Office page, connect Claude, connect Microsoft 365 or set up standing orders.
- Turn on autonomy so the team does routine work on a schedule, within caps you set (owner only).
Who can use it
Everyone in your workspace can ask the team for things through a connected assistant, whatever their role. You do not need to be an owner or admin. What changes from person to person is what they get back:
- Assistants show only your own work. You and every other role, including the owner, can use an assistant only to look up your own requests and results. A request from someone else is reported as not found. In a supported browser, the owner can read another person's request and result text in Office after setting up two-step sign-in, confirming with an authenticator code, backup code or passkey (Face ID, Touch ID or Windows Hello on supported devices), and opening the eyelid. Passkeys may not work inside the ONYX1 iPhone or Android apps; use an authenticator or backup code there. An authenticator or backup code works everywhere. If the page says “That code was just used. Wait for the next one.”, wait for the next authenticator code. Only the most recently accepted code is remembered, so A, then B, then A can be accepted within 90 seconds; that is the limit of this replay guard. The text hides when the owner selects Hide, after a minute without activity, when the tab is hidden, when the window loses focus, or when the five-minute confirmation expires. Generated files for another person's request remain private to that requester, even when the owner opens the request. Work in which the team read someone's own Microsoft 365 stays private to that person, even from the owner (see What connecting allows).
- You get only what your role can see in ONYX1. The team cannot show you anything you could not open yourself. For example, a crew member's daily brief has their own jobs and hours, with no invoices, quotes or leads. Nobody's brief has profit figures. Anything your role cannot see is left out of the brief, so a missing section does not mean zero.
- The owner reviews the team's requests for a yes, and an admin can decide ones on their own work. In Office, another person's ONYX1 approval details are behind the same owner eyelid as their request text. For an unexpired, pending board approval on another person's work, a fresh, opened owner can select Approve or Decline after reading the stored details, then select a separate confirmation button. Declining requires a reason. The owner must confirm two-step sign-in to open the eyelid. Assistants show approval items only for your own work; an owner also gets a count of other pending, unexpired ONYX1 board approvals and a direction to review them on the Office page. An admin can approve or decline requests on their own work. Claude refuses if you ask it to decide an approval you cannot decide. Only you can see and decide an email from your own mailbox or a calendar invite for your own calendar that is waiting for your approval.
To ask through an assistant, connect it to ONYX1 with your own login (see Connect an AI assistant). If you use Claude, see Connect Claude. When Animated Office is on, you can send a request from its page without connecting an assistant. Only the owner can change Office settings.
The Office page
Office in the sidebar shows your digital team. When ONYX1 Office is shown for the workspace, everyone can open it, whatever their role. On a phone, open More and choose Office.
The illustrated Office is off by default. Only the workspace owner can switch it on or off. In Settings → ONYX1 Office, find the Animated Office card. Select Enable Animated Office to turn it on or Turn off Animated Office to return to the plain team and request panels. This changes how the page is presented; it does not change who can see work or what the team can access. In either view, another person's request text stays behind the owner's eyelid until the owner confirms two-step sign-in.
With Animated Office on, the page shows a pixel-art office with six role buttons. Each button shows the role's recorded state: Working, Waiting on approval, Idle, Offline or Not set up. The caption explains what the scene means: Illustrated activity. Status comes from your visible requests. A scene is an illustration of recorded work, not a live view of a person or their computer.
Working and waiting roles move to their own computers. Idle roles continue through breakroom routines in the lounge and kitchen. New visible work can appear as a packet that briefly opens, then settles back to a compact marker after a few seconds. Opening the page does not replay old work as a new arrival. These movements do not start work or change a request's state.
Select a role to open its details in the scene's inset panel. It shows what the role does, the latest work visible to you (select it to open the request details in a panel on the right), and Send request. Owners and admins also see Schedule work. Selecting either action opens its existing form in the same inset, with that role already selected (see Standing orders).
Requests, Correspondence and Proposals are tabs on the page, directly under the scene. Requests and Correspondence show how many items are listed, and Proposals shows how many are waiting for a decision. A tab with nothing in it shows no count. On a phone, Correspondence reads Emails, and the tabs stay at the top of the screen as you scroll the list. Proposals appears only when you have access to it. Select View request on a request to open its details, approvals, result and any files you can access in a panel on the right, or full screen on a phone. Close the panel to return to the list. The owner can reveal another person's request, result and approval text after opening the eyelid. Generated files, their names and their links are available only to the requester. Work involving another person's Microsoft 365 remains private to its requester.
Camera controls
The room turns up to 15° to either side of centre and zooms from its fitted 1× view to 2.5×. Click or tap a role without dragging to open its details; dragging over a role moves the view. These camera gestures work only over the artwork, not the toolbar or an open panel or form.
Mouse and trackpad controls
With no inset panel open, drag horizontally over the artwork with the left mouse button to turn the room. Hold Control and drag vertically with the left mouse button to zoom around the point where you started. Hold Shift and drag with the left mouse button to pan, or drag with the right mouse button. Panning works at the fitted 1× view. Hold Control while scrolling the mouse wheel over the artwork to zoom; without Control, the wheel keeps its normal scrolling behaviour.
Touch controls
On a phone, swipe horizontally over the artwork to turn, pinch to zoom and swipe vertically to scroll the page.
Keyboard controls
When no inset panel is open and the scene is focused, press the left or right arrow key to turn, + or - to zoom, or 0 to reset the room to its fitted view. With no panel open, the camera remains usable when motion is paused.
Motion
Motion is on by default, and your preference is saved in this browser. The toolbar icon shows whether animation is running; its accessible label reports your saved on/off preference and the action to change it. When the preference is on but animation is paused, its accessible description explains why. Select the button to toggle your saved preference. Your device's reduced-motion setting takes precedence. Motion pauses when that setting is on, the browser tab is hidden, the browser is offline, or ONYX1 has announced an Office server outage. Role states describe recorded work, not live presence.
Sending from the page uses your signed-in session and current role permissions. ONYX1 checks that the ONYX1 Office add-on and AI & integrations module are enabled. If your workspace requires two-factor sign-in, complete it before sending. The form can send only while your browser and the Office server are online. If you go offline or sending fails, your draft stays in the open form and is not queued. If the form says, “Your request reached the team, but ONYX1 could not record it. Tell an owner or admin before sending it again,” follow that instruction. If ONYX1 cannot confirm whether a request was sent, the form says, “We couldn’t confirm whether it was sent. Check Requests before trying again.” Check Requests before you retry.
If Animated Office is off, or the scene cannot load, Office falls back to the plain, flat team, request feed and request details. Existing workspace panels remain available according to your access. The same visibility rules apply in either view. Everyone can open only work visible to their account:
- Showing your requests. Everyone sees only their own request text by default. Role states use only work visible to that person.
- Showing everyone’s requests, except work that uses another person’s own Microsoft 365. The owner can open another person's text with the eyelid after confirming an authenticator app or backup code. The requester's name, department, kind, status and time remain visible while the text is closed. Work in which the team used another person's own Microsoft 365 stays invisible to the owner (see What connecting allows).
The plain team and request panels
- Your team. The Chief of Staff sits at the top of an org chart with the specialists under it. Each one has a ring and a label that says what it is doing: Working, Waiting on approval, Idle, Offline or Not set up. The ring pulses while a role is working or waiting, and stays still if your device is set to reduce motion.
- Who is doing what. The latest requests, five at a time (use Previous and Next to see more), each with the role it went to, whether it is still working, and when it was made. Another person's request title is replaced by a closed-eyelid bar for the owner until it is opened with two-step sign-in; other roles see only their own requests.
- Scheduled work. Owners and admins also see the Standing orders card below the team and request feed, under the heading Scheduled work, where they set up recurring jobs for the team (see Standing orders).
Select a role to open its details: what it does, what it can use, how it uses your Microsoft 365, your own recent requests to it, and, for owners and admins, your standing orders sent to it. Select View request on a request to open its detail. It shows what you asked, who it is assigned to, its current status and progress, recorded activity, approvals, result and any file links you can open. For another person's masked request, progress uses a general team message and does not show blocker text or task-engine details. The owner can reveal another person's request, result and approval text with the eyelid. Generated files, their names and their links stay private to the requester. A masked request can still show who asked, its kind, status and time. The owner's own requests stay open. Work involving another person's Microsoft 365 stays hidden from the owner.
The roles:
- Chief of Staff: Takes broad requests, splits them up and hands each piece to the right specialist.
- People & Office Administrator: Looks after people and office admin: customers, jobs, tasks, timesheets, leave and compliance.
- Operations Coordinator: Keeps jobs, crews, equipment, vehicles and safety paperwork on track.
- Sales & Marketing Coordinator: Follows up leads and quotes, and drafts customer messages and content.
- Finance & Business Analyst: Reads invoices, quotes and money owed, and points out what to chase.
- Chief Legal Officer: Reads Resources for legal questions, ONYX1 records and NZ laws it can check, within your access. Cites sources and flags expired documents. Not legal advice. For Resources with indexed text, the Chief Legal Officer cites the document title, page or text chunk and part, with the last-updated date. It notes if the document is expired. For New Zealand laws, it cites the law title, provision, version date and source URL.
For the questions and tasks you give it, any of the six ONYX1 Office roles can list, search and read indexed text from Resources visible to the person who asked. Ask Office to list available documents when you want titles and categories without searching document text. For questions about business documents, each role searches Resources first. Ask the Chief of Staff what a visible SOP or pre-start document says and it can answer from Resources you can access. Requests to implement or review an operational process go to Operations; legal judgement, contract review or compliance work goes to Legal.
When the Office can read indexed text, the answering role cites the document title, page or text chunk and part (for example, “Page 1, part 1 of 2”), with its last-updated date. It says when the document is expired. For a PDF with selectable text, it reads up to 600 pages and up to 400,000 characters of text per document. If a document is longer than either limit, or reading fails part-way, the Office keeps the text it already read, and the document's index note says which page reading stopped at. Each read is limited to 12,000 characters. Image files and scanned PDFs can be found only by their title or file name; their contents are not indexed. For an external link, it can search the title and web address but does not open the linked page. See Company documents in Resources.
A few things worth knowing about the recorded states:
- Waiting on approval can show a little late. ONYX1 is not told when an approval is decided, so it clears when the work finishes or after a day.
- Working clears by itself two hours after a request was made if no answer has come back, so a cancelled request does not stay marked as working.
- Offline appears during an announced outage. For owners and admins, a role with no team member chosen stays Not set up. The Offline state clears when ONYX1 records that the server is back.
- Not set up is shown to owners and admins only. It means no team member has been chosen for that role yet (see Choose a team member for each role).
The role state is a summary of work visible to you, so it can take a refresh to catch up with a change made elsewhere. Office refreshes every 30 seconds while the page is on screen and your browser is online. Opening a request checks that request's status again with the Office server; if the server is unavailable, the saved status is shown. When the tab becomes visible or a connection returns, unseen changes settle into the first fresh view instead of playing as new activity.
Before you start
- ONYX1 Office is a paid add-on, so it is not part of any plan. ONYX1 switches it on for your workspace. If ONYX1 Office is missing from Settings, it is not on for you yet, or an owner hid it (see Show or hide features). To get started, email support@onyx1.app.
- Your workspace also needs the AI & integrations module, which comes with the plan, not the add-on (see Plans and what each includes). Without it you can still use this page, but Claude cannot sign in, Claude's address refuses every request, and team member keys stop working. The add-on does not switch it on.
- The ONYX1 team sets up your Office server and fills in the Office server address for you in Settings → ONYX1 Office. They give you the other two things you need: the Office company id and the Office key. Have them ready. Only the owner can do the setup steps below.
Office settings
Settings → ONYX1 Office shows, from the top: a status line with Connection, Office release and Last update; the Connect Claude to ONYX1 Office card; Agents; Business rules; Office email handling; Routines; Animated Office; and Setup. Only the owner can change Office settings. An admin sees the status line, the Connect Claude card and the sentence "Only the owner can change ONYX1 Office settings.", and keeps using the Office page as before.
Office email handling shows one line, such as "Email handling is off." or "Email handling is on · client emails handled (billing to the mailbox owner, other to the mailbox owner) · 2 internal domains · 1 website form address". Select Edit to change it, then Save Office email settings or Cancel. Routines holds Autonomy and a read-only list of your standing orders, with a link to manage them on the Office page.
When setup is working, Setup shows one line, such as "Connected · 6 roles · office-0.1.5". To change pairing, the connection, keys or role choices, select Change setup. ONYX1 asks you to confirm, because Office may stop working until setup is finished. When something in setup needs attention, Setup opens by itself and lists what is wrong.
Business rules and job descriptions
Under Agents, each team member has a job description of up to 2,000 characters. Under Business rules, write rules for the whole team, up to 4,000 characters, for example "Always copy the owner on client emails about money" or "Never book work on Sundays". Select Edit, write the text and select Save. To remove it, clear the box and save.
The team reads them at the start of its next task; you do not need to restart anything. They follow them unless they conflict with ONYX1's safety rules. They never give a team member a tool it does not have, and never skip an approval. Each save is recorded in the Audit log by what changed, without your text.
Access on the Mac mini
The Office team runs under one macOS user account. An agent's macOS sandbox can limit its process to its own work folder, private temporary files and a shared folder that ONYX1 has verified. These controls are best effort within that account. They do not give each role a separate macOS identity or stop another program running as that user from opening files the account can access. ONYX1 leaves workspace isolation and Mac capabilities off until their checks pass on the target mini.
A role is marked Ready only after a live Office role process is refused when it tries to read a business file outside its work folder or the verified shared folder, and its ONYX1 delivery check passes. A separate sandbox check is not enough. If that proof is missing, the role stays blocked. The live Office process check has not passed yet, so setup remains blocked.
The current fail-closed profile also blocks direct connections to hosted Claude. ONYX1 must configure an approved local model route and complete the live ACP check before setup can be marked Ready.
The installer does not enable Keychain-only access to the Office maintenance credential. ONYX1 must verify the installed service identity before enabling it. Contact support before moving or deleting the Office install folder.
The shared OneDrive folder stays off until ONYX1 verifies its exact synced folder and enables it for your setup. When enabled, agents can read it but cannot send files by writing directly into its Drop folder. Ask for a file through Office and use the ONYX1 Resources link in the result; ONYX1 checks your access when you open it. Printing is unavailable until ONYX1 connects its approval check; after that, approval must match the exact file and printer. Email sends through Office still need your confirmation of the exact message.
Pair the Office mini
Only the owner can pair the Office mini. In Settings → ONYX1 Office, open Setup (select Change setup and confirm if it shows one line), then find Pair the Office mini. The panel says No Office mini is paired yet., Office mini is paired. or Office mini needs to be paired again.
- Select Create pairing code. If this mini was paired before, select Create a new pairing code instead.
- Copy the code with Copy pairing code. Enter it in the Office install flow within 10 minutes. The code is shown once; creating another code replaces it.
- On the Mac mini, open Terminal and run
node ~/onyx1-office-install/office-self-update.mjs enroll. Enter the pairing code when asked. The mini stores its update credential in the login Keychain.
A mini set up before signed updates existed can be paired and scheduled in one step from a fresh install bundle. See Set up updates on an existing Office mini.
To disconnect a paired mini, select Revoke pairing. The mini needs a new pairing code before it can check for updates again.
Check the Office fleet
The owner and admins see the Office release and Last update at the top of Settings → ONYX1 Office. Only the owner can select Update now, which sits there too. The owner finds Office fleet status, with the role table, in Setup, below Pair the Office mini. The card shows the Office release, the Office server version and compatibility, and Last check, the time the mini last reported its status. Until the mini first reports, the card says The Office mini has not checked in yet.
The role table lists each role's Catalog status, Last refresh, Runtime tools and Next action. Read Next action for the step to take:
- Current: no action is needed.
- Needs refresh: select Update now when the role is idle.
- Pending: wait for the role's current work to finish; its refresh is waiting.
- Offline or Unknown: check the Office connection and wait for its next status check.
- Recovery required: contact support@onyx1.app before the role is used again.
Under Runtime tools, Delivered means ONYX1 confirmed the role's tools in a recent run. Pending check means ONYX1 will check after that role's next real run. Needs attention means the last run did not confirm its tools. Not checked means there is no run to confirm delivery yet. Follow Next action when a role needs attention.
Select Update now to queue the approved Office update. This does not let you choose a release. The mini checks every 15 minutes and once daily at 03:00 local time, then applies the update when it is online. A busy role waits until its current work finishes. While ONYX1 is waiting to pick up your request, the button says Update queued.
While an update is in progress, the status line at the top says Office paused during update. ONYX1 queues new Office work until the update finishes and the role is healthy, then starts that work. If a run finishes without ONYX1 tools available, makes no ONYX1 tool calls, and returns no result, ONYX1 starts one fresh run when the role is healthy.
Fleet status is also visible in the ONYX1 platform console. Fleet alerts do not send email or push notifications.
Connect your Office server
- Open Settings → ONYX1 Office and open Setup.
- Under Office server connection, check that the Office server address is filled in, then enter the Office company id. The ONYX1 team fills in the address for you. If it is blank, contact support@onyx1.app rather than typing one.
- Paste the key into Office key. (Once a key is saved, this field is replaced by Office key saved and a Replace key button. See below.)
- Turn the switch on. While it is off, Claude cannot use your Office server: the office tools answer that the digital office is switched off. Team member keys stop working too, and ONYX1 refuses their calls and records them, until you turn it back on.
- Select Save.
The key is write-only: ONYX1 never shows it again. Once a key is saved, the field becomes a read-only line that says Office key saved, with a green tick beside it and a Replace key button. Nothing more needs entering. To change the key, select Replace key, paste the new one into the box that appears and select Save, or select Cancel to keep the saved key. When you save other changes without replacing the key, ONYX1 keeps the saved key.
After you select Save, a green message confirms it: Saved., or Saved. The new Office key is saved. when you pasted a key. If the Office key saved line is showing and you have changed the address or the company id, a notice under it says the saved key will be removed when you save, because ONYX1 never sends a key to a different server. After you save, the field goes back to an empty box so you can paste the key again; the message says Saved. The Office key was removed because the address or company id changed. Paste it again to reconnect. Paste the Office key again in the same save to avoid that.
If the switch is Off when you save, a note under the buttons says ONYX1 Office stays off until you turn the switch on. Turn it on, then select Save. Saving the connection does not turn the Office on by itself.
Saving a new address, company id or key sets the connection back to Not checked, because the last result described a different server. Changing the company id also clears the role choices, because a team member in one company means nothing in another.
If ONYX1 refuses the address, the message says why. An address needs to start with https://, be a public address (not localhost or an internal network address), have no username or password in it, and have nothing after a ? or #.
Test connection
Under Connection status, select Test connection. It stays unavailable until an Office key is saved, and it tests the saved connection, so save any changes first. ONYX1 checks six things and shows the result of each as OK, Check, Failed or Not checked. If ONYX1 cannot reach your Office server, the three checks that need it show Not checked. Before you test, a step you have not finished yet shows To do.
The pill at the top summarises the result:
- Online: your Office server answered, asks callers to sign in, and knows your company.
- Needs attention: your Office server answered, but it is not safe or ready to rely on. For example, it is still starting, it is running without sign-in, or it does not accept your key or company id.
- Offline: ONYX1 could not get a usable answer.
- Not checked: nothing has been checked since the connection was last saved.
Last checked is the time of the latest check, in New Zealand time. Last working is the last time a check came back Online. A check is a test you run, a request from Claude that reaches your Office server, or the automatic check ONYX1 makes every ten minutes (see Get told when your Office server goes offline), so the pill and these times move on their own. A request that fails can turn the pill to Offline or Needs attention. Select Test connection to confirm it has recovered.
What each line means
If a line fails and the fix is not something you can do from this page, contact support@onyx1.app.
- Your Office server is reachable fails when ONYX1 cannot reach your Office server, it takes too long to answer, or it reports that it is unhealthy. Check that the address is right, then contact support. It shows Check when the server is still starting, has not finished first-time set up or reports an unexpected status. Contact support to finish it.
- Your Office server asks callers to sign in shows Not checked until your Office server is running normally. It fails with "Your Office server is running without sign-in." In that state anyone who can reach the address could act as the server's administrator, so ONYX1 does not count the connection as working, and Claude cannot hand out work or decide approvals until it is fixed. Contact support.
- Company found fails when your Office server does not accept the key, the key is not allowed to use that company, or the company id does not exist. Check the company id, or ask the ONYX1 team for a new Office key, then save and test again.
- Team connections pass on who asked fails when a team member's ONYX1 connection on your Office server does not pass on which task and person each request is for. ONYX1 refuses every request from that connection, so that team member gets no ONYX1 data until it is fixed. The line names the connection. It shows Check when ONYX1 finds no ONYX1 connection yet, when all of them are switched off, or when it could not read the list. Ask the ONYX1 team to fix it, then test again.
- Six roles mapped to agents fails when no role is chosen, or when a chosen team member no longer exists on your Office server. It shows Check when only some roles are chosen. A department whose role has no team member cannot be given work. See Choose a team member for each role.
- Agent key issued for each role shows Check until every role has a key. It does not stop the connection working, but a team member without a key cannot read your ONYX1 data.
The two lines about roles and keys do not need your Office server, so they are filled in before you test.
Get told when your Office server goes offline
While your connection is switched on, ONYX1 checks your Office server about every ten minutes, so you do not have to remember to test it. If it does not answer two checks in a row, ONYX1 tells you once, which is usually within 10 to 20 minutes of it stopping. A single missed check is ignored.
- Who is told: every active owner and admin, each with an in-app notification, an email and a push alert by default. The alert says Your Office server is offline, and it opens Settings → ONYX1 Office. In Settings → Notifications, under Staff, the two rows are Your Office server went offline and Your Office server is back online.
- When it is back: the first check where the server answers after an alert sends one Your Office server is back online notification, in-app by default. You get nothing when a short blip clears before the alert.
- What to check: the computer running your Office server is on, signed in (a restart can leave it at the login screen until someone signs in), and connected to the internet. Then select Test connection.
- What does not count: a server that answers but Needs attention is not offline, so it does not send this alert. ONYX1 does not check a connection that is switched off or has no Office key saved.
An owner or admin can turn either alert off, or add email and push to the recovery one, in Settings → Notifications, under Staff.
Choose a team member for each role
Only the owner can do this, in Setup. The six roles are Chief of Staff, People & Office Administrator, Operations Coordinator, Sales & Marketing Coordinator, Finance & Business Analyst and Chief Legal Officer. The People & Office Administrator also looks after the people side of the office (leave, timesheets, tickets and licences), the Sales & Marketing Coordinator also drafts marketing content for your approval, and the Chief Legal Officer gives you information about the legal side of running your business, with the source of each point. It is information, not legal advice, and it tells you when you need a lawyer. It finds laws by title or alias in its local built-in list and can read the latest text of those laws, citing the provision and version date. It cannot search for laws by topic. Earlier versions of laws in that list are available once ONYX1 switches them on; if it cannot check a requested law or version, it says so. If your Office was set up with the older Marketing role, ONYX1 shows these six roles instead: work handed to Marketing now goes to the Sales & Marketing Coordinator, and the Chief Legal Officer needs a team member and a key like the other roles. Ask the ONYX1 team to move your Office across. Each team member also has a personal first name, set by the ONYX1 team when your Office is set up (for example, Elena for the Chief of Staff). The team member introduces themselves by that name, and the lists below show it with the role, as in "Elena · Chief of Staff". The role stays as their title, and ONYX1 uses the title to find the right team member for each role. Save the connection first: the role list stays unavailable until a connection exists, and Refresh agents needs your company id and key. Then, under Agent roles and keys:
- Select Refresh agents. ONYX1 lists the team members on your Office server. It keeps the one you saved for a role while the server still lists it. For any other role it picks the likely team member by matching their title or name to the role name.
- Check the choice beside each role. Choose Not mapped to leave a role empty.
- Select Save mappings.
ONYX1 does not guess when two team members fit one role equally well, so that role stays empty for you to choose. Until you select Refresh agents, each list shows only the saved team member, as Saved agent and the start of their id.
Prepare website enquiries
If your workspace uses Website enquiries, you can choose an ONYX1 Office role to prepare new leads. An owner or admin sets this in Who gets told under Settings → Website enquiries. The selected role must have a team member mapped under Agent roles and keys in Setup on Settings → ONYX1 Office. This website enquiry workflow runs as the owner and is separate from per-person email correspondence.
The hosted form and widget do not display the saved privacy statement URL or a built-in privacy notice, and they do not ask visitors to tick a consent box. Privacy wording you add to Form sub-line appears to visitors. ONYX1 receives the details submitted through the form and records the enquiry. Before an owner or admin turns on website enquiries for the hosted form or widget, they set the secure privacy statement URL and confirm the policy statement in Your enquiry form.
If the business has ONYX1 Office switched on and a team member mapped to this role, the Office team can read the enquiry to prepare a summary. Every clean enquiry creates its own lead. A submitted email, phone number or street address can suggest an existing customer; a matching street address can suggest a site. These are unverified suggestions: they do not show that the enquirer represents that customer, and ONYX1 never selects one automatically. The Office team can update only the lead created for that enquiry. A possible duplicate from the last 24 hours is linked for an owner or admin to review. ONYX1 does not combine or change the existing lead automatically.
If the owner has connected Microsoft 365 and the enquiry includes an email address, ONYX1 Office can prepare one plain-text reply draft to the enquirer's address in the owner's own Drafts folder. The team never sends it. A person reviews the draft before sending. This is not an in-thread Reply All draft.
Review a job proposal
Only the owner or an admin can review proposals. Open Office and find Job proposals. With the animated scene on, it is under the Proposals tab below the scene. Select a proposal to open it in a panel on the right (full screen on a phone) and read the original enquiry, which is shown as untrusted text, and the Office summary. Check the source details against the proposed customer, site, job and quote.
Customer and site suggestions come from matching fields in the public enquiry and are unverified. They do not show that the enquirer represents the suggested customer, and ONYX1 never selects a customer or site automatically. Choose Create a new customer or Pick an unverified customer suggestion. Type part of a suggestion into Search customers or scroll the list. Search only filters these suggestions; it does not verify them.
For each suggestion, check which enquiry field matched, the customer name and the displayed contact details and ID. To use an existing site, first choose the customer, then select Pick an unverified site suggestion. Check the full site address, customer name, matching address and site ID. For existing choices, the review shows the customer name and ID and the site address and ID that approval will use. New customer and site IDs are created on approval. A site must belong to the selected customer. If you have not verified the link, create a new customer or site. Check the job details and each quote line. Every To price line needs a price or must be removed before approval.
If your workspace requires the pre-work safety pack, complete its attestations and upload both required PDFs in the review. These are the same safety inputs used when creating a job. Review the schedule date, team and crew as suggestions. People with pending or approved leave, or an overlapping assignment, are unavailable for the proposed crew window. You can edit the suggestions or untick the schedule or crew. If you keep the date but leave out crew, the date may be booked without an assignment so a dispatcher can add crew. If a booking gate blocks the date, both remain suggestions and the job stays unbooked.
Read the consequences, save any edits, then tick the confirmation for the saved review and select Approve and create job. Approve and create job and Decline stay switched off until what they need is done, and a line beside them says what is missing: choose the customer and site and complete the required fields, save any edits, tick the confirmation, or write a reason to decline the proposal. The confirmation applies to the exact saved values; changing a value means saving the edits and confirming the new review. Approval creates the selected customer and site when needed, a job and a draft quote. It does not send the quote or contact the enquirer.
If the accepted-quote gate or pending safety-document approval blocks booking, the job stays unscheduled and unassigned and the proposal shows Applied, dispatcher follow-up. If the required pre-work safety pack is incomplete, approval creates no customer, site, job or quote. The proposal links to the job and quote when approval creates them. When booking is allowed, a date with an assigned crew shows Applied, scheduled and assigned. A date booked without crew shows Applied, scheduled, crew needed.
To decline a ready proposal, enter a reason and select Decline. Declined or expired proposals create no customer, site, job or quote, and the lead remains available for follow-up. If a proposal is Stalled, needs a person, select Stop proposal to end the stalled chain and return the lead to follow-up.
Give each team member a key
Only the owner can do this, in Setup. Each team member reads your ONYX1 data through their own key, not a shared one, and each role has one key. A key can use only the ONYX1 tools its role needs, and never a tool that needs the Read + money / sensitive actions level. It cannot use the MCP resources or prompts endpoints, only tools. Separate keys also mean you can replace one without disturbing the others.
A key does not give the team member any access of its own, and it does not matter who created it. The team always works with the permissions of the person who asked: when a team member works on a request, ONYX1 finds out who made that request and lets the team member use only the ONYX1 tools that person's own role can use, narrowed to the role's tools. Work that ONYX1 did not hand to the team gets no ONYX1 data at all.
Beside each role, the page shows Key created with the date, or No key yet.
The Chief of Staff and People & Office Administrator can also use day_hours to read recorded time for one New Zealand day. Each entry includes a linked job number and title when the requester can view that job, plus clock-in and clock-out in New Zealand time, lunch and worked minutes. Open entries show as "still clocked in" and have no final worked-minute total. The report includes each person's day total. It flags a day for missing lunch when the person's closed entries exceed the configured threshold (four hours by default), no closed entry records lunch, and there is no unpaid gap between shifts that counts as lunch. It also flags overlaps between entries (including entries still clocked in), jobs the person was not assigned to that day when the requester can view them, and missing clock-outs. If a linked job is hidden from the requester, it gives a generic assignment flag without showing job details. It has no pay or cost rates.
The requester's permissions still apply: a requester who can review team timesheets gets the team report, while other requesters get only their own entries. It returns at most 50 people and 200 entries and says when data is omitted. Day totals and flags may be partial when entries are capped.
- Beside a role, select Create agent key.
- Select Copy token. ONYX1 shows the token once and cannot show it again.
- Follow the steps shown under the token to add it on your Office server. If the ONYX1 team looks after your Office server, ask them how to hand the token over.
- Select I have saved it.
To replace a key, select Replace key and confirm. The old key stops working straight away, so that team member cannot read ONYX1 until the new token is added on your Office server. If you lose a token, replace the key. To take a team member off ONYX1 altogether, select Remove key and confirm. The key stops working straight away and the role shows No key yet. Removing a key is recorded in the Audit log.
Team member keys also stop working while the connection is switched off, when no connection is saved, and when ONYX1 has not switched ONYX1 Office on for the installation. In each case ONYX1 refuses the call and records it.
Creating or replacing a key, and every tool call a team member makes, is recorded in the Audit log. The Actor of a team member's tool call is the person who asked, because the team member worked with that person's permissions. It shows as AI assistant followed by the tool's name (for example "AI assistant · find jobs"), with the role and the person at the start of the detail, for example Agent (finance) for Tama · find_jobs(query=<5 chars>) → ok. Request text is recorded as a length, not the words. A call ONYX1 refuses because it cannot tell whose request it is has the action mcp.agent_refused, and its Actor is the owner or admin who created the key. The detail ends in the outcome, such as ok, denied, invalid or error. The role is written as chief_of_staff, office_admin, operations, customer_sales, finance or legal. Entries from before the Marketing role was retired show marketing. Filter by Action mcp. or set Entity to AI assistant to see them. Calls Claude makes start with AI instead of Agent.
Connect your Microsoft 365
If your business uses Microsoft 365, each person can connect their own account so ONYX1 Office can work with their mail, calendar and documents when they ask. Connecting is optional. ONYX1 Office works with your ONYX1 data without it, and needs it only for a person's own mail, calendar and documents. ONYX1 has to switch Microsoft 365 on for your installation first. Until it has, My account and Settings → ONYX1 Office say so.
There are two steps, and they are done by different people.
Approve ONYX1 Office for your organisation (once, by an administrator)
A Microsoft 365 administrator approves ONYX1 Office once for the whole organisation. The owner opens Settings → ONYX1 Office, opens Setup and finds Microsoft 365, and uses the address under Approve for your organisation. If you are not the Microsoft administrator, send them that address. They sign in to Microsoft, review what is being approved and accept. Nobody's account is connected by this step.
If the owner or an admin is signed in to ONYX1 when the administrator accepts and Microsoft sends them back, ONYX1 notes the approval. In Setup, Microsoft 365 then shows the owner a green tick, Approved for your organisation, with who it was and the date, and the address moves behind Show approval address. Keep that address in case it ever needs approving again. If Microsoft sends the owner back with an error, ONYX1 notes nothing and Setup says Microsoft did not complete the approval. If ONYX1 cannot confirm the approval, the owner's Setup only says each person can connect once your Microsoft administrator has approved it. An admin who returns from Microsoft sees only the status line, with no Microsoft message.
The tick also shows while at least one person is connected, because that proves the approval works. In that case it has no name or date, and the page shows how many people are connected. The tick is only a note for your team: Microsoft enforces the approval when each person signs in, and nothing in ONYX1 depends on the note.
Connect your own account (each person)
- Open My account and select Settings.
- Under Microsoft 365, select Connect Microsoft 365.
- Sign in to Microsoft with your own work account. Microsoft always asks which account to use. Because your administrator has already approved ONYX1 Office, this is usually one click with no further questions.
The Microsoft account has to use the same email address as your ONYX1 sign-in. If it does not, ONYX1 does not connect it and tells you which email to sign in with; you can also ask your owner to update your ONYX1 email. Each Microsoft account can be connected to one person in your workspace only.
My account then shows the account you connected. Everyone connects their own account, whatever their role. Nobody can connect an account for someone else or use another person's connection. The owner and admins can see only that a person has connected and which account (see See who has connected); they cannot see anyone's mail, calendar or documents. If your older connection does not include calendar write access, My account says Reconnect Microsoft 365 to let Office send invites. Select Reconnect and accept the updated Microsoft permission. Your existing mail and calendar tools remain available while you decide.
If Microsoft 365 is missing from My account → Settings, ONYX1 Office is not on for your workspace. If it says Microsoft 365 is not switched on for this installation, email support@onyx1.app.
What connecting allows
When you ask, your digital office team can read and search your email, read your calendar, and find documents in OneDrive and SharePoint. It can write drafts in your own mailbox and create events on your own calendar. It sends an email only after you confirm the exact message. It can reach only what you can already open in Microsoft 365, so it cannot see a mailbox, calendar or document you cannot. Claude itself does not read your mail: the team members do the work you hand over.
There are limits on what the team can read:
- Email: it reads the first 8000 characters of a message and the names and sizes of its attachments, never the attachments themselves.
- Documents: it can find any document you can open. It can read plain-text files (such as .txt, .csv, .md and .json), Word .docx files and PDFs with selectable text, up to 1 MB each. It cannot read scanned or image-only PDFs, Excel spreadsheets or macro-enabled Word files.
- Calendar: it reads events in a window of at most 31 days.
What each team member can do with Microsoft 365 depends on its role:
- The Chief of Staff and the People & Office Administrator: email, calendar, documents, drafts and calendar invites.
- The Sales & Marketing Coordinator: email, documents, drafts and calendar invites, but not reading the calendar.
- The Operations Coordinator: calendar, documents, drafts and calendar invites, but not reading email.
- The Finance & Business Analyst: documents and drafts, but not reading email or the calendar.
- The Chief Legal Officer: email, documents and drafts, but no calendar invite tool. It can write a draft email but cannot ask for one to be sent.
Calendar invites
The Chief of Staff, People & Office Administrator, Operations Coordinator and Sales & Marketing Coordinator can ask the team to create an event on the calendar of the person who made the request. The connected account is the organiser. Give the event a title, NZ start and end time, and at least one attendee. You can also include a location, a plain-text body of up to 8000 characters, and a link to one job or customer you can access. There can be up to 20 attendees.
An attendee is treated as internal if their address belongs to an active person in your workspace or their email domain is listed under Office email handling in Settings → ONYX1 Office. The domain list still applies when email handling is switched off. If every attendee is internal, ONYX1 creates the event and sends the invites straight away. If anyone is outside, the event waits for you to approve the exact title, NZ times, location, attendee list and body. It is not created until you approve it.
Ask Claude what is waiting for your approval. The invite stays in ONYX1 while it waits for your approval and appears with its event details in the same list as pending email sends. Only you can see and decide it. When you reject it, no invite is sent. If Microsoft refuses an invite outright, ONYX1 Office says nothing was created and closes the request; ask Office again with the corrected details. If Microsoft does not confirm whether an approved event was created, ONYX1 keeps it available to retry with the same event id. Approve that same item again and check your calendar before making a separate event.
The event details are kept in ONYX1 so the exact event can be shown for approval and retried safely. The Audit log records each new request and whether the event was created, rejected, refused by Microsoft or left unconfirmed. It includes attendee counts on request and successful creation records only. These invite records never include the title, attendee addresses or body. ONYX1 Office does not reschedule or cancel calendar events.
Sending email
When you ask the team to email someone, it writes a draft in your own Drafts folder and asks you to confirm it. Nothing is sent until you do.
- Ask Claude "What is waiting for my approval?". The email is listed with the Microsoft account it comes from (yours), who it is to, the subject, the full text, the names of any attachments, and any recipients outside your organisation.
- Ask Claude to approve or reject it. Claude reads the exact email back to you first, with every recipient, and sends it only when you confirm that exact email.
A few rules apply to every email:
- It is sent as you. It goes from your own mailbox and appears in your Sent Items.
- Only you can confirm it. The owner and admins cannot see or confirm an email from your mailbox, and you cannot confirm anyone else's. You do not need the owner's yes for your own email, which is separate from the approvals described under Connect Claude.
- An edit needs a new confirmation. If you change the draft in Outlook after Claude read it back (the To, Cc or Bcc recipients, the subject, the text or the attachments), ONYX1 does not send it. Claude reads the new version back and you confirm that one.
- It is sent once. If Microsoft does not confirm that an email was sent, ONYX1 does not try again by itself. Check your Sent Items before you ask for it again. If a send is still unfinished after about ten minutes, ONYX1 marks it as failed, not confirmed, and tells you to check your Sent Items.
- Rejecting sends nothing. The draft stays in your Drafts folder.
- Confirming needs the right level. Claude can confirm an email only on a connection set to Read + money / sensitive actions. If your Microsoft 365 connection has expired you can still reject an email, but you cannot confirm it until you reconnect. The email stays waiting for your decision, and Claude tells you to reconnect in My account.
- There are limits. The team cannot attach files, and it will not ask to send a draft that has Bcc recipients. If you add Bcc recipients in Outlook yourself, the read-back lists them and the email goes out only if you confirm it. A draft can have at most 40 To and Cc recipients between them, and the team writes plain text of at most 8000 characters. It sends only from your own mailbox, never a shared one. If you attach a file in Outlook yourself, its name is shown when you are asked to confirm.
Each request and each send is recorded in the Audit log with who it was for and how many people it went to, and never the subject, the addresses or the text.
This describes the Microsoft 365 tools you ask an Office team member to use. It is separate from the opt-in correspondence inbox below. For these tools, ONYX1 does not keep a separate copy of the email, calendar or file content they read. What the team reads is passed to the team member doing your task, and anything the team writes into the result it gives you is kept with that work in ONYX1, like any other result. A request in which the team read your email, calendar or files (or wrote a reply to one of your messages), and its results, can be seen only by you in ONYX1: not by the owner and not by an admin. Because the owner cannot see that work, the team does not raise owner approvals inside it. Requests are processed on your company's Office server, so whoever administers that server could see the team's working records.
For an email you are asked to confirm, ONYX1 keeps its To and Cc recipients, its subject and the first part of its text (up to 2000 characters) so it can ask you, and it reads the full draft from Microsoft again whenever it shows it to you and when it sends it. ONYX1 also stores the address and identifier of the account you connected and the protected sign-in that lets it act as you. No one else can see that sign-in in ONYX1 or on a screen. Connecting and disconnecting are recorded in the Audit log, which shows who did it and when and never any mail, document or sign-in details. When someone uses the AI to delegate work, ask the team, search business records or help, use Microsoft 365, or write a result or a hand-off, the Audit log shows only the names and lengths of text passed, such as query=<22 chars>, never the words.
Office email correspondence
This is a separate, opt-in workflow. The owner turns on Allow Office email handling for this workspace in Settings → ONYX1 Office, under Office email handling (select Edit). Each person then selects Opt in to Office email handling under Office email correspondence on My account. If you want Office to check your Microsoft 365 Inbox, connect your own account. You can also opt in to verified forwarded email without connecting Microsoft 365; see Bring website and email enquiries into Leads. For setup and review steps, read Review business email.
The owner can also tick Handle client emails that aren't about a job and pick who gets the follow-up tasks under Billing client emails go to and Other client emails go to: the Sales & Marketing Coordinator then makes a follow-up task, linked to the customer, for a trusted known client's email that is not about a job, and saves a Reply All draft when the email came through a connected Microsoft 365 Inbox. See Review business email. Email with clear complaint or legal wording, such as "formal complaint" or "my solicitor", stays in Needs review.
When Office handles email for you, ONYX1 stores the message text and details it needs to classify and work on the message. It does not store attachment files. The message is handled using your own ONYX1 account and current role. You can see your own message summary and Office actions in My correspondence and on a linked job. In ONYX1, only you can see those message details; owners and admins see content-free workspace status. The Office server reads the message for the team to handle it, so its administrator may be able to inspect the team's working records.
Owners and admins also see Workspace processing status across the team. It shows who handled each message, its classification, work status and number of actions. For another person's message, it does not show the sender, subject, message text or draft content.
When Office saves a Reply All draft for a message in your Microsoft 365 Inbox, it is saved in your own Drafts folder in the original thread. Review the draft in Outlook and send it yourself. ONYX1 does not send it automatically. A forwarded email does not get an Outlook reply draft. ONYX1 purges stored message content, attachment names, mailbox and Graph identifiers, private correspondence notes and action payloads 365 days after receipt, or earlier if the linked enquiry, job or customer is deleted or the message is classified as not an enquiry.
Tasks and variation records created from an email follow their own retention rules. Content-free provider-event and duplicate-match hashes remain until 365 days after receipt only to prevent a retry or another opted-in Inbox copy from restoring purged content. Active cost-approval flags follow their own retention rules.
Owners and admins see customer cost-approval flags on a job’s Correspondence card. After recording the customer’s applicable approval in the usual job record, tick I have recorded the customer’s applicable approval in the usual job record. and select Clear flag. The job activity history records who cleared the flag.
See who has connected
The owner can see who has connected under Settings → ONYX1 Office → Setup → Microsoft 365, Who has connected. It lists each person's name, the Microsoft account they connected and whether it is connected or needs reconnecting. It never shows mail, documents or sign-in details.
Reconnect or disconnect
- Needs reconnecting: a connection can expire or be ended in Microsoft. My account then shows needs reconnecting, and the team cannot use your Microsoft 365 until you select Reconnect and sign in again.
- Disconnect: open My account → Settings and select Disconnect under Microsoft 365. ONYX1 deletes the stored sign-in straight away and ONYX1 Office stops working with your mail, calendar and documents. You can connect again at any time. Disconnecting removes only ONYX1's copy of your sign-in. The organisation's approval stays in Microsoft until your administrator removes it there.
Connect Claude
Settings → ONYX1 Office has a Connect Claude to ONYX1 Office card, right below the status line. The owner and admins both see it. Until Test connection shows Online, the card only says that the address appears there once it does. When your Office server is Online, the card shows a Ready pill, the address Claude connects to (https://onyx1.app/api/mcp/office), a Copy address button and the steps:
- In Claude, open Settings, then Connectors, and choose Add custom connector.
- Name it ONYX1 Office, paste the address and add it.
- Sign in to ONYX1 if asked, then choose a level under What this AI may do and select Approve & connect.
The card also reminds you that approving or declining the team's requests from Claude needs the Read + money / sensitive actions level. The steps are the same as for claude.ai in Connect an AI assistant and ask it how to use ONYX1.
This is a different address from the one for your own ONYX1 data (/api/mcp). Settings → AI & integrations explains both when your workspace has ONYX1 Office, and links here. The ONYX1 connector gives Claude your own ONYX1 data. ONYX1 Office hands work to your team. Add the one you need, or both as separate connectors.
Claude then has six tools for your team. Between them it can:
- give you a daily brief
- hand a piece of work to a department
- ask a department a question
- check on work already handed over
- list the approvals waiting for you
- approve or decline one of them: an approval on your own work; reject an email the team wrote in your own mailbox, which only you can decide (see Sending email); or reject a calendar invite with an outside attendee on your own calendar, which only you can decide (see Calendar invites). The owner sees only a count of other pending board approvals in the assistant and reviews their details on the Office page after confirming two-step sign-in and opening the eyelid.
When you hand over work or ask a question, Claude tells you which team member has it, for example "Noah, the Finance & Business Analyst". Claude waits for the answer, checking again for a minute or two, and gives it to you in the same reply. If the job takes longer than that, Claude tells you it is still being worked on and to ask again in a minute or so. Ask Claude for the status of that work and it gives you the answer once it is ready.
Everyone can use these tools, and each person gets only their own work and what their role can see (see Who can use it). What Claude can do depends on the level you choose when you approve the connection:
When the requester has the required access, the Office team can read and add notes on leads, private job notes and site notes. Each note shows ONYX1 Office and the role that wrote it. Staff cannot edit or remove these automated notes. Crew progress updates remain human-only and are not available to Office.
- Read only: the daily brief, work status and the list of approvals. Handing work over and asking a question are refused.
- Read + everyday actions: also hand work to a department and ask a question.
- Read + money / sensitive actions: also approve or decline a team's request for a yes, if your role may decide it (the owner, or an admin on their own work), confirm or reject an email from your own mailbox, and approve or reject a calendar invite with an outside attendee on your own calendar.
Standing orders
A standing order gives a member of your Office team a job on a schedule, for example the Chief of Staff's "Give me a brief of today: jobs on, anything overdue, anything waiting on me" every weekday at 7:30 am, or the Finance & Business Analyst's list of overdue invoices every Monday. Owners and admins can set them up from the Office page. With Animated Office on, select a role, then Schedule work. With the plain view, use Scheduled work below the team and request feed. For the owner, Settings → ONYX1 Office lists the workspace's standing orders under Routines and links to them. Admins manage theirs on the Office page.
Add a standing order
- In Scheduled work, select Add standing order. Optionally select a template under Start from a template: Daily brief, Outstanding timesheets, Quotes untouched for 14 days, Overdue invoices or Equipment and vehicles due soon. A template fills in the team member, how often, the day and time, and the words, and you can change any of them. A template is greyed out until a team member is chosen for its role.
- Choose who it goes to in Send to: Chief of Staff, People & Office Administrator, Operations Coordinator, Sales & Marketing Coordinator, Finance & Business Analyst or Chief Legal Officer. A role shows (not set up) until you choose a team member for it under Agent roles and keys and select Save mappings. Until then, you cannot pick it in Send to; see Choose a team member for each role.
- Write what they should do in What should they do? (up to 4000 characters).
- Choose How often: Every day, Weekdays or Once a week. For Once a week, also choose the Day.
- Set Time (NZ). The time is New Zealand time, and it stays the same time on the clock when the clocks change.
- Select Add standing order.
Edit a standing order
Select Edit next to one of your own orders. The drawer opens with its current team member, instructions and schedule. Change the fields you need, then select Save changes. The order uses your changes the next time it runs.
Each person can have up to 10 standing orders, on or off. A new order first runs at its next scheduled time. If you add one after today’s scheduled time has passed, it waits until the next scheduled time. If you switch an order back on after its scheduled time has arrived, it waits until the next scheduled time. Switching it on does not repeat work for a scheduled time that has already arrived. Each order in the list shows who it is sent to. Select Switch off to pause an order and Switch on to start it again. Delete asks you to confirm, and work it has already started carries on.
How it runs
- It runs as you. A standing order is handed to the team member you chose the same way as a request you make through Claude, and it can use only what you could open yourself. The work shows up as your own work.
- Your access is checked each time. Just before every run, ONYX1 checks again that you are still an active owner or admin. If you are not, the order switches itself off and the card shows Off with the reason. ONYX1 also checks that the workspace and ONYX1 Office are ready: the workspace is in good standing and has accepted any updated terms, you have set up two-factor sign-in if your workspace requires it, ONYX1 Office and the AI & integrations module are switched on, the Office server connection is on with an Office key saved, and someone is chosen for the role the order is sent to. If one of those is not right, that run is skipped, the order stays on, and it runs again at its next time once the problem is fixed. An order never runs with access you no longer have.
- A run without recorded work is not made up later. During the 10 minutes after a scheduled time, ONYX1 checks whether the order can run. If a safety or readiness check stops it before ONYX1 records work, the Audit log records the run as skipped. If ONYX1’s Office server check fails before work is recorded, the Audit log records the run as failed. Neither outcome gives ONYX1 work to start later.
- Recorded work may still start later. Sometimes ONYX1 records work but cannot start it straight away. During a later Office health check, ONYX1 may try to start that same work while it can still be started. For your own order, Last run shows the scheduled time for that run. The card says Waiting for the result while a result is pending. The next scheduled time starts a separate run.
- You are told when the result is ready. When the team member finishes, you get a notification, Your standing order has a result, in ONYX1 and as a push notification if you have those on. It does not say what the result is. Open the card and select Read the last result. The card keeps only the result of the latest run. Only the person who set the order up gets this notification. Its In-app and Push switches in Settings → Notifications, under Staff, are workspace-wide settings that an owner or admin changes for everyone.
Who sees what
- You see and manage your own standing orders. An admin does not see anyone else's.
- The owner sees everyone's standing-order rows, marked Set by the person's name. Another person's instruction and result stay behind the eyelid until the owner has confirmed two-step sign-in and opened it. The owner can switch someone else's order off or delete it while the text is hidden, but cannot edit it, including who it is sent to, or switch someone else's back on.
- Only you can read the result of your own order by default. The owner can read another person's result after opening the eyelid, unless the team member used someone's own Microsoft 365 to produce it. Then only that person can read it (see What connecting allows).
- If you remove a person from the team and they have no linked records at all, their standing orders are deleted with them. Anyone with records, including any whose standing order has already run, is deactivated instead. Their orders stay until their next scheduled time, then switch themselves off.
If a standing order switches itself off
A standing order switches itself off only when the person who set it up is no longer an active owner or admin, either because they were removed or deactivated, or because they lost the role. The card shows Off with the reason under the order:
- "The person who set this up can no longer sign in to ONYX1.": the person was deactivated or removed.
- "The person who set this up is no longer an owner or admin.": the person needs the owner or admin role again, or the order should be deleted.
Once the person is an active owner or admin again, they select Switch on. An owner can delete any order instead.
If a run is skipped
When something is wrong with the workspace or ONYX1 Office at the scheduled time, that run is skipped and the order stays on. This covers a billing hold, updated terms waiting to be accepted, ONYX1 Office or the AI & integrations module being off, the Office server connection being off or having no Office key, no one chosen for the role the order is sent to, and two-factor sign-in not set up. No result arrives for a skipped run, and the card shows no error. Once the cause is fixed, the order runs again at its next scheduled time. To fix it, see Before you start, Connect your Office server and Choose a team member for each role.
Autonomy
Autonomy lets your Office team do routine work on a schedule without anyone asking each time. ONYX1 starts each run itself at the time you choose, and the run works as you, within the caps you set. Autonomy is off until you turn it on.
Only the owner can see or change autonomy. Admins and other roles cannot. It is in Settings → ONYX1 Office, under Routines, in Autonomy, and it appears once ONYX1 has switched ONYX1 Office on for your workspace.
Before you start
- ONYX1 Office and the AI & integrations module must both be on for your workspace.
- Connect your Office server, pair the Office mini, and choose a team member for the Chief of Staff role. See Connect your Office server, Pair the Office mini and Choose a team member for each role. The routine keeps the Chief of Staff team member chosen when you add it. If you later choose a different one, runs are refused with the reason Not started.
- If your workspace requires two-factor sign-in, set it up on your own account. Each run works as you, so your account must be ready.
Turn on autonomy
- In the Autonomy section, find Morning brief: your Chief of Staff prepares a brief of the day before work starts, at 7:00 am on weekdays, New Zealand time. Select Add routine. The routine is added switched off.
- Change the routine if you need to: Time (NZ), the Days it runs (at least one), Cap per run (NZD) and Cap per month (NZD). The caps start at 5 NZD a run and 50 NZD a month. The run cap cannot be more than the monthly cap, the monthly cap can be at most 1,000 NZD, and it cannot be lower than what the routine has already spent this month.
- Tick Run this routine on its schedule, then select Save routine.
- Select Switch autonomy on. This is the switch for your whole business: while it is off, no routine runs, whatever each routine's own setting says.
The time is New Zealand time, and it stays the same time on the clock when the clocks change. ONYX1 checks for due routines every 5 minutes, so a run can start a few minutes after the time you set. Adding the routine also adds a standing order for it, owned by you. That order does not appear in Scheduled work; the routine runs it.
What runs
At each scheduled time, ONYX1 hands the Chief of Staff the routine's instruction, as you: "Give me a brief of today: jobs on, anything overdue, anything waiting on me. Do not send, post or pay anything." The work and its result show up as your own work in ONYX1 Office.
Before every run, ONYX1 checks again that:
- autonomy and the routine are both on, and the routine is not hard-stopped
- ONYX1 Office, the AI & integrations module and your Office server are on and answering
- the Office mini is ready for the Chief of Staff, and the Chief of Staff's team member is active
- you are still the owner, with two-factor sign-in if your workspace requires it
- the month's spend, plus anything held for runs in progress, plus one more run cap, stays within the monthly cap
If a check fails, nothing runs and the routine tries again at its next scheduled time. Most refusals show in Last 10 runs as Did not run with the reason. While autonomy is off or the routine is hard-stopped, its scheduled times simply pass with no entry. A time that ONYX1 could not start within 15 minutes is skipped, not made up later.
Caps and spend
- Cap per run: when a run starts, ONYX1 sets this amount aside from the month's budget. ONYX1 checks the run's cost before each step it takes and stops the run once its cost reaches the run cap.
- If your Office server reports that a run used your business's own Claude account, ONYX1 does not charge for that usage. When that run ends, ONYX1 records no cost for it, gives back the amount set aside, and the routine keeps running on its schedule.
- When a run reports a cost, ONYX1 records it in NZD. If the reported cost cannot be read or converted to NZD, or your Office server sends nothing about the run's usage, ONYX1 counts the whole run cap and hard-stops the routine.
- Cap per month: a run does not start if the month's spend, plus anything held for runs in progress, plus one more run cap, would go over it. The month restarts at midnight UTC on the 1st, which is midday or 1:00 pm on the 1st in New Zealand.
- The routine shows This month: what it has spent, anything held for a run in progress, and its monthly cap.
- A run also stops at 15 minutes, or when it reaches its step or usage limit.
Hard stop
The routine shows Hard-stopped when a run's cost reaches its run cap, when a finished run's cost goes over what was set aside, or when a finished run that did not use your own Claude account has no cost ONYX1 can read in NZD. Nothing runs until you select Clear hard stop. Clearing it does not reset the month's spend, so a routine at its monthly cap still does not run.
Run now
Select Run now to run the routine once straight away. It goes through the same checks and caps as a scheduled run and does not change the schedule. Selecting it twice on the same page starts one run. Run now is greyed out while autonomy is off, or while the routine is off or hard-stopped.
Turn autonomy off
Select Switch autonomy off. No routine starts while it is off, and a run already in progress is refused at its next step. To stop one routine only, untick Run this routine on its schedule and select Save routine.
Limits
A run uses the Chief of Staff's team member key, so it has the same limits as other Office work: it cannot send email or use tools that need Read + money / sensitive actions. See What the team cannot do. The morning brief is told only to read and report.
Last 10 runs
The list shows each recent run: Scheduled or Run now, when it started, what happened (for example Running, Done or Did not run, with the reason), and its cost. While a run is working, the cost shows as "up to" the amount held for it. A finished run on your own Claude account shows Uses your own Claude account instead of a cost.
Create a document
Ask your connected assistant to create a file from information the team has read for you. For example, ask, “Create a PDF of my timesheets.” For a personal-timesheet PDF, the People & Office Administrator can use your own current-week rows. If you are exempt from submitting timesheets and have no sheet for that week, there is no timesheet to show. You can also ask for an investigation summary PDF with its source references.
The team can create PDF and Word documents, Excel workbooks, and flyers as PDFs or PNG images. Excel workbooks need a table. Documents use your company name and accent colour when available. Standard documents print source labels and references. A flyer uses recent building-wash jobs in the requested area and before-and-after photos only when the caption names the stage and the job is marked to share photos with customers. It shows web source labels and domains. Full citation URLs and ONYX1 source history appear on the Office request detail.
Your result includes the file name and a private ONYX1 Resources link. ONYX1 checks that the signed-in person is the requester each time the file is opened. The file is not shared with other team members, emailed or sent outside your business.
Files can be up to 20 MB, PDFs up to 100 pages, and tables up to 50,000 rows in total. An Excel worksheet can contain at most 50,000 rows, including its headings and source references. If a document is too large, too long or has too many rows, ask for a shorter document or fewer rows.
Things to ask your assistant
- "Give me my daily brief." Everyone gets today's and tomorrow's jobs, their own hours this week and what the team is doing on their work. Roles that can see them in ONYX1 also get what happened in the last 24 hours, money owed and overdue invoices, quotes gone cold, the lead pipeline and approvals waiting in ONYX1. It has no profit figures.
- "Ask the finance team which invoices are overdue and who we should chase first." A question gets an answer back without changing anything.
- "Hand this to operations: draft next week's crew plan for the Mt Wellington job." Your assistant sends a broad or multi-part request to the Chief of Staff, who splits it up between the specialists.
- "What is the status of that work?" A short request may finish in the first reply. If it is still queued or working, your assistant shows who has it and the current progress. Use the request ID from that reply with
get_work_statusto check again. An assistant can look up only your own work, including when you are the owner. Treat the work as finished only when the status is Completed. The final reply includes the summary and any file links you can open. For work you send to Office, ONYX1 requests an in-app completion notice for the person who asked. Saved notification settings determine whether it appears; a push notice also needs push enabled and a registered device. Open the notice to read the result in Office. - "Reply to Priya's email about the roof and say we can start Monday." If you have connected Microsoft 365, the team writes the reply as a draft in your Drafts folder and asks you to confirm it. Nothing is sent until you do (see Sending email).
- "What is waiting for my approval?" An assistant shows approvals for your own work. The owner also gets a count of other pending board approvals and reviews their details on the Office page after confirming two-step sign-in and opening the eyelid. An admin can decide requests on their own work. Only you can see and decide an email from your own mailbox or a calendar invite for your own calendar that is waiting for your approval.
Prepare a building-wash flyer
Ask your connected assistant, for example: "Make a building-wash flyer for Auckland property managers." ONYX1 uses building-wash jobs and matching service-area proof you can see, and current company certifications when available. It uses before-and-after photos only when their captions name each stage and the job is marked to share photos with customers. The flyer shows public web source labels and domains. The Office request detail shows the full citation URLs and ONYX1 source history. ONYX1 creates a PDF and PNG and returns private Resources links that only you can open.
Open both files and check the evidence and wording. Ask your connected assistant to revise them if needed. The flyer workflow does not email, print, post or publish a file. Get the owner's approval before sharing or printing the final version.
What the team cannot do
ONYX1 enforces some limits whatever the team is asked to do. The team can never get you more than you could open yourself: a crew member's request is answered from their own jobs, hours and gear, and an admin's request cannot reach anything only the owner can see. If you ask for something your role cannot see, the team member is refused and says so.
A team member's key can use only the tools listed for its role, never a tool that needs the Read + money / sensitive actions level, and cannot use Claude's address. For example, the Chief Legal Officer's key can read in ONYX1 (jobs, sites, quotes, invoices, tickets and licences, safety documents and Resources documents), read public New Zealand legislation, and read mail and documents in Microsoft 365. It can leave a draft in your own Drafts folder and append notes to leads, jobs and sites. Those notes are append-only: staff cannot edit or remove them. It cannot otherwise change ONYX1 business records (jobs, customers, quotes, invoices, tasks and so on) or take business actions, and it cannot send an email. Like every team member, it records its own hand-offs, results and approval requests as part of the work it is asked to do.
The team is also set up to raise an approval request before it sends anything to a customer, publishes anything, spends money or makes a change that is hard to undo. The Sales & Marketing Coordinator is told that publishing always needs your approval, and the Chief Legal Officer is told that it gives information, not legal advice. Those are instructions on your Office server, not limits that ONYX1 enforces, so read each request before you approve it.
What a team's request for a yes says (its title, summary, recommended action, risks, business impact and expiry) is kept in ONYX1 and shown from there, not copied to your Office server. The owner can review another person's ONYX1 board approval on the Office page after confirming two-step sign-in and opening the eyelid. For a pending, unexpired approval, the owner first reads those stored details, chooses Approve or Decline, then confirms that choice in a separate step. Declining requires a reason, which appears on the work item. The decision is bound to the details shown, so a change requires a fresh read-back. The owner cannot use this page to decide an email or calendar invite; only that mailbox owner can decide those. After the owner decides a board request, or an admin decides one on their own work, the requester's team is notified; if that fails, the decision still stands and the screen says so.
Before Claude approves or declines a board request, ONYX1 reads the request back and runs it only when Claude confirms that exact request within five minutes. For a decline, the read-back includes the reason. It shows the same title, summary, recommended action, risks, business impact and expiry that the decision checks. For older approvals without stored details, it shows the available detail from the Office server. If the request changes after the read-back, the confirmation stops working and ONYX1 reads the new version back instead.
Claude lists and decides only the requests ONYX1 raised for your team's work. An approval made directly on your Office server is not shown, and anything that is not one of those requests is refused and left to be decided on your Office server. ONYX1 also refuses a request that has expired or whose expiry it cannot read. An expiry is read as a date, for example 2026-10-10, which lasts to the end of that day in New Zealand, or as a date and time. A date and time with no time zone is read as New Zealand time. ONYX1 does not raise an approval request if its expiry is at or before the current time.
Team member keys do not work on Claude's address. ONYX1 refuses the call and records it in the Audit log.
Mention ONYX1 Office in your privacy policy
If your team uses ONYX1 Office, add these sentences to your business privacy policy. Name the AI service your team uses if it is not Claude.
We use ONYX1 to manage our jobs and records. Our team uses AI tools with ONYX1, including Claude, to help with that work, so the AI provider may process your details, including outside New Zealand.
If something goes wrong
- ONYX1 Office is missing from Settings: the add-on is not on for your workspace, or an owner hid it. See Before you start.
- The page says "ONYX1 Office is part of your account, but ONYX1 has not switched the Office server connection on for this installation yet." ONYX1 has to switch that on for you. Email support@onyx1.app.
- Saving says "ONYX1 Office isn’t switched on for your account.": the add-on is not on for your workspace.
- Saving says "Only the owner can change ONYX1 Office settings.": ask the owner to do it. Admins can see the status but cannot change Office settings.
- Test connection shows Offline: check the address, then contact support.
- You got Your Office server is offline: the computer running your Office server is probably off, restarted and waiting at its login screen, or offline. Check it, then select Test connection. ONYX1 tells you again only after it has been back online.
- Connect Claude to ONYX1 Office shows no address: select Test connection. The address appears when your Office server is Online.
- Claude cannot hand work to a department: that department's role has no team member. Choose one, as described above.
- The ONYX1 sign-in window for Claude shows Can't connect with AI & integrations isn’t on your workspace’s plan. The workspace does not have the AI & integrations module. An owner can change the plan in Settings → Plan & billing.
- Claude's address or a team member's call is refused with
not_entitled: the workspace is missing the AI & integrations module or the add-on. - Claude says an approval is not one it can decide, or that its expiry cannot be read: contact support, or ask the team to raise a fresh request.
- Claude says it cannot find work or a team's request for a yes that you know exists: assistants look up only your own work, even for an owner. Ask the person who handed it over. The owner can review another person's ONYX1 board approval on the Office page after confirming two-step sign-in and opening the eyelid. They must read the stored details and confirm a separate Approve or Decline choice. Generated files for another person's request stay private to that requester. Work in which the team read someone's own Microsoft 365 remains private to that requester. Only you can see and decide an email from your own mailbox or a calendar invite for your own calendar that is waiting for your approval.
- Claude says only the owner or an admin can decide a team's request for a yes: the owner can decide it, or an admin if it is on their own work. Only you can see and decide an email from your own mailbox or a calendar invite for your own calendar that is waiting for your approval.
- Claude says an approval has expired or is no longer pending: someone has already decided it, or its expiry has passed. Ask the team to raise a fresh request.
- A team member's call is refused with "agent keys are switched off for this workspace": the connection is off, not saved, or switched off for the installation. See Connect your Office server.
- A team member's call is refused because ONYX1 cannot tell whose request it is: the task was not handed over through ONYX1, the team member was started some other way (for example by someone commenting on the task on your Office server), the task has already finished, the person who asked is no longer active, or they have not set up two-factor sign-in that your workspace requires. Ask Claude to hand the work over again. If every call from one team member is refused, the Team connections pass on who asked line of Test connection will say why.
- Test connection is unavailable after you changed the address or company id: ONYX1 removed the saved key when you saved. Paste the Office key, select Save, then test again.
- Connect Microsoft 365 ends with "We could not connect Microsoft 365": try again. If it keeps happening, ask your Microsoft administrator to check that ONYX1 Office has been approved for the organisation (see Connect your Microsoft 365).
- Claude says an email was not sent because the draft changed, is no longer in your Drafts folder or is not a draft any more: ask Claude to read the email back again, or ask the team to write it again.
- Claude says Microsoft did not confirm that an email was sent: check your Sent Items. ONYX1 does not send it again by itself.
- Connect Microsoft 365 tells you to sign in with the Microsoft account for your ONYX1 email: the account you chose uses a different email address. Sign in with the account that uses your ONYX1 email address, or ask your owner to update your ONYX1 email. If it says the account is already connected to someone else in your workspace, each Microsoft account can be connected to one person in your workspace only.
- Claude says to connect Microsoft 365 in ONYX1 first, or that the connection has expired: you have not connected it, or it needs reconnecting. See Connect your own account.
- Connect Microsoft 365 says the sign-in link had expired or was already used: select Connect Microsoft 365 again. A link works once and for about ten minutes.
- Claude says it is not permitted to use a tool: the connection's level is too low for that tool. Disconnect it in Settings → AI & integrations and connect again at a higher level.
