Admin dashboard Settings

Tools

Tools let each member’s assistant and its jobs read the wikis and write to the member’s wiki, and let the assistant start and end the member’s meetings. Switched off here, a tool is off for every member.

Who changes itAdmins and owners
Applies toEvery member’s assistant and its jobs
StartsAll on, the meeting tools asking first
Takes effectThe next turn or job
In the admin dashboard: SettingsTools Open the dashboard
On this page

Wiki tools#

These work only while the knowledge wiki is on. While it’s off, the dashboard shows them as off, whatever their switches say.

FeatureDescriptionDefault
wiki_page

When wiki_page is enabled, the assistant and its jobs can read any page of the member’s knowledge wiki. The assistant can also read the team and organization wikis the member reads.

On
wiki_write_page

When wiki_write_page is enabled, a job can create or replace a page of the member’s knowledge wiki. It can’t change the wiki’s list of pages, its log or the journal, and the member’s feed says when a job writes a page.

On
read_okf_spec

When read_okf_spec is enabled, jobs can read the specification of the format wiki pages are written in. It holds nothing of your organization’s.

On

Meetings#

The assistant can start and end a member’s meetings, on their desktop. A meeting it starts has its own record and recap, as any meeting does, and records what the member’s recording default says: yours, or their own where Meetings lets them choose. When it asks first, the ask says what the meeting will record, so a member who says Yes knows whether a recording starts. Should you raise what it records before they answer, their Yes starts nothing, and the assistant has to ask again. To start a meeting, one of the member’s desktops has to be on; to end one, the desktop it runs on. Members see what you chose in their desktop’s Settings, as in this example.

FeatureDescriptionDefault
start_meeting

Whether the assistant can start a meeting on the member’s desktop: when they ask it to, or when what it has gathered shows that a meeting has begun, such as what’s said, or a call’s window in front where Desktop awareness records it. Ask only: the member is asked first, in the desktop app and by a notification with Yes and No, which say what the meeting will record, and nothing starts unless they say Yes within five minutes. Allowed: it starts without asking, and a notification tells them, and what it’s recording; with more than one of their desktops on, they’re asked all the same, and it starts on the desktop where they say Yes. Off: the assistant can’t start meetings.

Ask only
end_meeting

Whether the assistant can end the meeting that’s live on the member’s desktop: when they ask it to, or when what it has gathered shows that the meeting is over. Ask only: the member is asked first, on the desktop the meeting runs on, and it ends only if they say Yes within five minutes. Allowed: it ends without asking, and a notification tells them. Off: the assistant can’t end meetings.

Ask only
Allow override

When Allow override is enabled for a tool, each member chooses for themselves, in their desktop’s Settings under Your meetings and your assistant (Start meetings, End meetings): Ask first or Always allow. Until they choose, your choice applies. It can’t be enabled while the tool is Off.

Off

What isn’t a switch here#

The assistant also files jobs when a member asks in chat, which comes with Offer and run work. And when someone with the Team or Org role asks their assistant about the people they lead, it reads those people’s records; that comes with the role, not a switch here. See Roles and permissions.

Jobs don’t search the internet for MCP servers, the add-ons that connect AI assistants to other apps and services, and there’s no switch for it: the service doesn’t add MCP servers, so it doesn’t look for them.

Esc
↑ ↓ to moveEnter to open