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 activity strip's window and when quiet scheduled runs are flaggedOwners and adminsReporting, below
AutomationsBoard moments posted to SlackOwners and adminsAutomations
Architect accessMCP tokens for an architect agent, and the plugin connections bound to the workspace's 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's hubs report change. 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 beside Since last visit, shortest first
Default periodSince last visitSince last visit, or one 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
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

The last period offered can't be removed. Removing the period that is the default sets the default back to Since last visit.

The hub period control

The control in a hub's header sets the period the hub's change cards count over. Those are Shipped, on every hub, and the System scorecard, on the root hub. It offers Since last visit, then the periods the workspace offers.

  • 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.
  • Since last visit counts from your previous visit to that hub, remembered across devices. Reopening a hub within 30 minutes counts as the same visit. On your first visit to a hub, it counts the shortest period offered.

What's next