Introducing Centres: control exactly who in your team sees what
Divide your workspace into named Centres, give each team member scoped access to only the record types and modules they need, and manage it all from a new Settings → Centres panel.
What's coming to Hub: Centres
Hub is introducing Centres — a new way to divide your workspace so that different teams or functions only see the records, modules, and data that are relevant to them. This is a significant step forward for workspaces with multiple departments, client groups, or operational areas that need to stay focused without getting in each other's way.
Deployment note: The Centres feature is currently in a preparation release. The Settings → Centres panel and centre switcher are included in this build, but workspace activation — which enforces scoped access across the platform — is not yet available. Activation will be released separately once remaining backend steps have been verified. Existing workspaces keep their current workspace-wide behaviour until activation is explicitly enabled.
What are Centres?
A Centre is a named division within your workspace. You can create as many as you need — for example, one for Sales, one for Operations, one for each client account. Each Centre has its own access rules that specify which object types and modules its members can work with.
Rather than giving every team member access to everything in your workspace, you assign them to the Centres that are relevant to their role. A member only sees the records and tools their Centre grants them.
Viewer and editor roles within each Centre
For each Centre, members can be assigned as Viewers (read-only) or Editors (read and write). You can configure access at the level of an entire object type — such as all Contacts or all Projects — or scope it down to specific modules within a type.
This means a team member can be an editor for one record type in one Centre and a viewer for a different type in another, giving you fine-grained control without needing to create separate workspaces.
A new Settings → Centres panel
Administrators now have a dedicated Settings → Centres page where you can:
- Create, rename, and archive Centres
- Assign viewer and editor memberships to workspace members
- Configure ownership and sharing for whole object types or individual modules
- Review recent authority changes — an audit trail of who changed what
Member settings link directly to Centre access, so you can jump from a team member's profile to the Centres they belong to without losing your place.
A centre switcher in the workspace sidebar
Members who belong to more than one Centre will see a centre selector below the workspace selector in the sidebar. Selecting a Centre narrows the working view to the record types and modules that Centre grants access to — making it easy to switch context without having to remember what belongs where.
Selecting a Centre doesn't grant extra access — it just focuses what's visible. Permissions remain exactly what the Centre defines.
What changes when a Centre is active?
Once workspace activation is available (in a future release), enabling Centres will apply scoped access enforcement across:
- Record queries and mutations
- Dashboard and activity feeds
- Tasks and notifications
- Reports and Finance
- Marketing, Forms, and Inbox
- AI tools and the Hub connector
Shared resources that a member cannot access will not appear in their results. Restricted reports will not return partial company-wide totals for records outside the member's scope.
Existing workspaces will not be affected until an administrator explicitly activates Centres. Until then, everyone continues to see and do exactly what they do today.
Invitations and new members
When you invite someone to your workspace, you can assign them to one or more Centres as part of the invitation. Centre roles are applied atomically when the invitation is accepted — so new members land in the right scope from their very first login.
Removing a member from the workspace also removes their Centre grants automatically, so there's no risk of a former member retaining scoped access.
Centres have been a frequently requested capability for teams that share a Hub workspace across distinct functions or client groups. We'll share more detail on activation timing and the migration path as the remaining backend steps are completed.
More improvements are in progress. We'll keep you updated as they roll out.