Hubz.

Administration / Active organization and membership roles

Workspace membership, team roles and permissions

Review the active organization, visible workspaces and existing member roles together.

PRODUCT VIEW

See how it works.

Review the organization and workspace you are working in, together with member roles and permissions. The company environment a user is working in, the membership granting access and permitted actions are assessed together. Organization settings show the active company, current role and visible workspaces. Team members and roles have their own permission conditions. Personal profiles, organization email branding and platform operator powers are distinct.

Hubz.Workspace / Organizations, teams and rolesDK
EXPLORE THE PRODUCT

Organizations, teams and roles

Sample view
Active organizationVisible workspacesExisting role modelBrands and data boundaries

Organizations, teams and roles

Active organizationSee the current company and the user's role in that context without mixing memberships across organizations.Review ↗
Visible workspacesReview organization environments authorized for the user. Visibility does not mean everyone can access all customer data.Review ↗
Existing role modelUse available roles such as owner, administrator, member, billing or viewer under their respective action rules.Review ↗
Brands and data boundariesDistinguish organization email identities and social brand profiles from data access boundaries. Creating a social brand does not create a CRM organization.Review ↗
01Verify the active context
02Review members and roles
03Act within permissions
Interface illustration using sample data. The layout is simplified to explain the relevant feature.

FROM NEED TO OUTCOME

Where this helps.

Someone belonging to several organizations can act in the wrong customer environment without noticing the active context. A role name also does not mean every action is allowed.

WHAT YOU CAN WORK TOWARDS

Check the active organization and membership before acting. Organize team access through existing roles and module rights without presenting a brand record as separate data isolation.

STEP BY STEP

How to use it.

  1. 01

    Verify the active context

    Check the company you are working in and visible workspaces, keeping personal accounts and organization environments distinct.

  2. 02

    Review members and roles

    Assess existing members and roles in the team view you are authorized to use, matching new access needs to actual responsibilities.

  3. 03

    Act within permissions

    Complete membership or role actions within current rules. Role names do not automatically enable plan features or provider permissions.

INSIDE THE MODULE

What can you do?

FOCUS 01⊙
Organizations, teams and roles
Scope●Permission○Review○
Verify the active context

Active organization

See the current company and the user's role in that context without mixing memberships across organizations.

FOCUS 02▤
Organizations, teams and roles
Scope○Permission●Review○
Review members and roles

Visible workspaces

Review organization environments authorized for the user. Visibility does not mean everyone can access all customer data.

FOCUS 03↗
Organizations, teams and roles
Scope○Permission○Review●
Act within permissions

Existing role model

Use available roles such as owner, administrator, member, billing or viewer under their respective action rules.

FOCUS 04◇
Organizations, teams and roles
Scope●Permission○Review○
Verify the active context

Brands and data boundaries

Distinguish organization email identities and social brand profiles from data access boundaries. Creating a social brand does not create a CRM organization.

IN EVERYDAY WORK

What it looks like in practice.

User working across organizations

You belong to two business environments and need to create a task.

Check the active organization so the work is recorded in the correct customer environment.

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

KNOW WHAT IS INCLUDED

Plans, permissions and limits.

Existing membership and basic role safeguards apply in every plan. Member management requires the relevant authorized role.

  • A general custom-role designer, SSO and unimplemented enterprise identity features are not promised.
  • Separate customer data environments depend on workspace and membership design, not the number of social brands.
Compare plans

YOUR QUESTIONS

About this feature.

01Does a social brand create a separate CRM environment?

No. A brand profile organizes content rules and social accounts. It does not create a separate organization, subscription or CRM data isolation boundary.

02Can every member change roles?

No. Membership and role actions are restricted by current permission rules. Your workspace role and the action scope are checked separately.

RELATED WORKFLOW GUIDES

You may also need these features.

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.

MODULES THAT WORK TOGETHER

Explore related modules.

01

Customer relationships

Keep contact details, company relationships and past conversations in one shared record.

02

Social Studio

Organize brand rules, content preparation, review, calendars and connected social accounts in a shared workspace.

03

Security and team access

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