Hubz.

Workspace / Members, roles and permissions

CRM team roles and workspace permissions

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

PRODUCT VIEW

See how it works.

A shared workspace does not mean everyone can perform every action. Hubz evaluates access in organization and workspace context through membership, existing roles, module entitlements and relevant action conditions. Permissions for connected providers and Business MCP are managed separately. Core security and access protections supporting daily team work are preserved across all plans.

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.

DETAILED FEATURE GUIDES

Explore the features in this module.

Release notesReview recorded product updates by version, date and change descriptions.Settings centerManage profile, organization, security, communication, data and usage settings within the relevant permission boundaries.PWA and connection statusUse browser-based installation on supported devices while keeping connection and update status visible.Organizations, teams and rolesReview the active organization, visible workspaces and existing member roles together.Plan and usageReview the active workspace's plan, status and available usage indicators.Platform workspacesAuthorized platform staff review workspace status, plan assignment and access decisions through controlled actions.Platform plan catalogAuthorized operators review plan names, active status, module access, limits and catalog price fields.Platform billing reviewReview recorded subscription and overdue payment information alongside the organization's current access policy.Platform operations and auditAuthorized operators review available service signals, safe error summaries, platform changes and read-only support metadata.

FROM NEED TO OUTCOME

Where this helps.

If account ownership, team data access or unused connections are unclear, shared work can become difficult to manage.

WHAT YOU CAN WORK TOWARDS

Match access to the work each teammate needs to do. Treat workspace access, provider connections and particular action permissions as separate decisions.

STEP BY STEP

How to use it.

  1. 01

    Define the workspace

    Establish which workspace holds the organization, team and customer data. Review membership separately where customer data needs to be separated.

  2. 02

    Organize members and roles

    Determine which work the team needs within the existing role structure. Consider plan modules alongside each user’s action permissions.

  3. 03

    Keep permissions current

    Regularly review connected accounts and access scopes. Update permissions or revoke a connection when responsibilities change.

INSIDE THE MODULE

What can you do?

FOCUS 01⊙
Security and team access
Scope●Permission○Review○
Define the workspace

Workspace membership

Manage user access within the relevant organization and workspace. Creating a brand profile does not create a separate CRM environment.

FOCUS 02▤
Security and team access
Scope○Permission●Review○
Organize members and roles

Existing team roles

Organize members using the available role structure. Review permissions needed for daily work, management and specific actions during setup.

FOCUS 03↗
Security and team access
Scope○Permission○Review●
Keep permissions current

Module access

Determine available modules from the plan and workspace entitlements. An accessible screen does not mean every action is authorized.

FOCUS 04◇
Security and team access
Scope●Permission○Review○
Define the workspace

Connection scopes

Manage external-account and Business MCP permissions separately. Workspace access does not replace the provider user’s consent.

FOCUS 05⌁
Security and team access
Scope○Permission●Review○
Organize members and roles

Browser and PWA use

Use Hubz in supported desktop and mobile browsers, installing it as a PWA where available. Daily CRM operations require an internet connection.

IN EVERYDAY WORK

What it looks like in practice.

Growing team

Responsibilities are reviewed as new teammates join.

Arrange access through membership and existing roles to match the shared workspace to responsibilities.

Agency

More content brands are added while different customers’ CRM data needs separation.

Keep brand profiles distinct from workspaces and review data and membership structure for the actual requirement.

Scenarios are illustrative; they are not customer testimonials or measured performance claims.

KNOW WHAT IS INCLUDED

Plans, permissions and limits.

Core account security, existing team roles and workspace settings are included in all plans. MCP connection management is part of Business.

  • Available roles and access requirements are reviewed together during workspace setup.
  • A PWA does not imply a native iOS/Android app or offline support for all actions.
Compare plans

YOUR QUESTIONS

About this feature.

01Is basic security only available in Business?

No. Existing account, role and access protections are preserved in all plans. Business adds broader operational scope, capacity and MCP access.

02Does every brand need a separate workspace?

A brand profile organizes content and visual rules. Workspace structure is reviewed separately where different customers need separate CRM data or memberships.

03Can I download a mobile app?

Hubz works in mobile browsers and can be installed as a PWA in supported browsers. It does not promise a separate native iOS/Android application or offline support for all CRM operations.

MODULES THAT WORK TOGETHER

Explore related modules.

01

Data management

Identify gaps in CRM records and manage migration and data organization around the workspace’s actual needs.

02

Integrations

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

03

MCP and AI connections

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