Skip to content
On this page

Workspace Settings

Workspace settings hold the choices one workspace makes for everyone in it, from its name to the periods its hubs count change over. Open Workspace settings in the sidebar, then pick a section from the list on its left; it lists only the sections you can open. Organization Settings covers what the whole organization shares.

Sections

SectionWhat it holdsShown toDocumented in
GeneralHow this workspace is named and shown across ProvenMapEveryone; only owners and admins can change it—
AI modelsWhich models chat and agents may use in this workspace, and the defaultEveryone; only owners and admins can change itChat
Setup guideThe floating checklist that walks you through ProvenMap. Each person has their own and turns it on or off for themselvesEveryonePlaybooks
ReportingThe hub periods, the look-back window, when quiet scheduled runs are flagged, how change periods are cut and kept, and when the briefing postsOwners and adminsReporting, below
AutomationsBoard moments and the briefing posted to SlackOwners and adminsAutomations
Agent access (changed 12 October 2026)MCP tokens that connect an AI agent to this workspace and everything in it, and the plugin connections bound to its app boardsOwners and adminsMCP Access
Danger zoneDisabling hides the workspace and its boards until it is enabled again; deleting removes it for goodOwners and adminsDeleting & Undoing

Reporting

Note

Owners and admins only.

Reporting sets how this workspace reports change: the periods its hubs count over, and how its change periods are cut and kept. One value applies to everyone in the workspace, and Save changes applies it.

Every member's hub offers the same periods, so a number on one person's hub means the same on another's.
FieldDefaultAllowed valuesWhat it changes
Periods offered7 days, 30 days1 to 4 periods, each 1 to 365 days, none repeatedThe windows the hub's period control offers, shortest first
Default period30 daysOne of the periods offeredThe period the control selects for someone who hasn't picked one
Look back30 days7 to 90 daysHow many days the activity strip on each app's tile on the root hub covers, and how far back a node's diary entries reach. A critical change raises a flag only for a period that ended inside it. The diary's row of weeks follows the period control
Scheduled runs gone quiet48 hours6 to 720 hoursHow long a repo that has run on a schedule can go without a run before its chip on the Bindings card reads Last scheduled run and the hub's attention queue gets a row for it
Change periodsWeeks (Monday to Sunday, UTC)Weeks, or Calendar months (UTC)The calendar unit /changes records change periods in. Periods already recorded keep their unit, so a change shows as a seam in the pictures
Read history back90 days7 to 365 daysHow far back a repo's first /changes reads its git history
Keep change periods730 days90 to 1825 daysChange periods older than this are deleted
Briefing scheduleEvery 7 days, on Monday, at 09:00 UTCEvery 1 to 31 days, at any hour in UTC; on a weekday when every 7 daysWhen an automation with Monday briefing ticked posts the week's changes from the root hub's diary. Where it posts is the automation

The last period offered can't be removed. Removing the period that is the default makes the shortest period left the default.

The hub period control

The control in a hub's header sets the period the hub's change cards count over. It offers the periods the workspace offers, shortest first. Each is a window back from now, so opening the hub changes nothing.

  • Your pick is remembered in this browser, and holds while the workspace still offers it. When an admin removes that period, the control falls back to the workspace's default.

What's next

Last updated October 27, 2026