HUBZ / PRODUCT AREAS

Connections and security

Connect your tools and give teammates or Business MCP clients only the access they need.

Management

Integrations

Set up email, calendar, task-file and approved communication connections with the correct account, permissions and action scope.

Explore this module
Hubz.Workspace / IntegrationsDK
EXPLORE THE PRODUCT

Integrations

Sample view
◎Google Workspace mailAccount and permissionsDepends on setup
↗Google CalendarAccount and permissionsDepends on setup
⊙Drive for task attachmentsAccount and permissionsDepends on setup
◇Approved email deliveryAccount and permissionsDepends on setup
⌁Website intakeAccount and permissionsDepends on setup
01Define the need
02Connect the correct account
03Use the connection within scope
Interface illustration using sample data. The layout is simplified to explain the relevant feature.
Features in this area1+

Business

MCP and AI connections

Connect compatible clients to permitted CRM context, with separate review and authorization for private plans and communications.

Explore this module
Hubz.Workspace / MCP and AI connectionsDK
EXPLORE THE PRODUCT

MCP and AI connections

Sample view
◎
BUSINESS · MCP

MCP and AI connections

1Scope selectionDepends on scope
2Compatible client connectionDepends on scope
3Private-plan preparationDepends on scope
4Human reviewDepends on scope
5Connection and permission managementReview
Content → review → permitted action

An MCP connection alone does not grant permission to send email, launch campaigns or publish social content.

01Choose the connection scope
02Review the plan
03Approve actions separately
Interface illustration using sample data. The layout is simplified to explain the relevant feature.
Features in this area4+

Management

Security and team access

Arrange team access through workspace membership, existing roles, enabled modules and connection permissions.

Explore this module
Hubz.Workspace / Security and team accessDK
EXPLORE THE PRODUCT

Security and team access

Sample view
Workspace membershipExisting team rolesModule accessConnection scopesBrowser and PWA use

Security and team access

Workspace membershipManage user access within the relevant organization and workspace. Creating a brand profile does not create a separate CRM environment.Review ↗
Existing team rolesOrganize members using the available role structure. Review permissions needed for daily work, management and specific actions during setup.Review ↗
Module accessDetermine available modules from the plan and workspace entitlements. An accessible screen does not mean every action is authorized.Review ↗
Connection scopesManage external-account and Business MCP permissions separately. Workspace access does not replace the provider user’s consent.Review ↗
Browser and PWA useUse Hubz in supported desktop and mobile browsers, installing it as a PWA where available. Daily CRM operations require an internet connection.Review ↗
01Define the workspace
02Organize members and roles
03Keep permissions current
Interface illustration using sample data. The layout is simplified to explain the relevant feature.
Features in this area9+