Skip to main content

Account vs Workspace

Purpose and Concepts​

The Nodus platform implements a hierarchical organizational model that enables efficient management of resources and access controls across various business units. Understanding this hierarchy is essential for optimal platform configuration.

Hierarchical Structure​

Nodus organizes resources in a two-tier hierarchical system:

  1. Account

    • The top-level organizational unit within the Nodus ecosystem
    • Serves as the primary billing entity
    • Contains and manages multiple workspaces
    • Consolidates administration of shared resources

  2. Workspace

    • Functional sub-accounts operating under the parent account
    • Isolated environments with dedicated resources
    • Configured for specific business units, brands, departments, or projects
    • Maintains independent configurations while inheriting account-level permissions

Role-Based Access Control​

The account/workspace model facilitates sophisticated permission management:

  • Account Administrators: Users with comprehensive access to all workspaces and account-level configurations
  • Workspace Administrators: Users with administrative privileges limited to specific workspaces
  • Workspace Users: Users with operational access to specific workspaces based on assigned roles
  • Cross-Workspace Roles: Specialized roles that span multiple workspaces for enterprise scenarios

Benefits of the Hierarchical Structure​

  • Organizational Alignment: Maps to your business structure for intuitive resource management
  • Resource Isolation: Maintains separation of data and configurations between business units
  • Consolidated Billing: Simplifies financial management with unified billing at the account level
  • Centralized Governance: Enables standardized security policies and compliance controls
  • Flexible Scaling: Accommodates organizational growth through addition of workspaces

Creating a New Account​

  1. Click New Account in the homepage
  2. Fill out the form
  3. Press Create

Creating a New Workspace​

  1. Click New Workspace in the homepage
  2. Fill out the form
    • Account
      • this is the account the workspace will belong to
    • Workspace Name
      • this is the name of the workspace
    • Workspace URL
      • this is the address of the workspace
  3. Press Create

Switching Between Workspaces​

  1. Use the workspace selector in the top navigation bar
  2. Select the desired workspace from the dropdown menu
  3. The interface will refresh to display the selected workspace context
  4. All operations will now execute within the selected workspace context

Managing Users and Permissions​

  1. Navigate to Account or Workspace settings
  2. Select "Users & Permissions"
  3. Add users via email invitation
  4. Assign appropriate roles based on responsibilities
  5. Configure custom permission sets for specialized access requirements

Use Cases​

Multiple Brands Under One Entity​

Scenario: A parent company manages multiple consumer-facing brands, each requiring separate data pipelines and analytics.

Implementation:

  • Create one Nodus account for the parent company
  • Establish separate workspaces for each brand
  • Configure brand-specific integrations and data flows
  • Implement cross-workspace reporting for executive oversight

Development and Production Environments​

Scenario: An organization requires separate environments for testing and production data pipelines.

Implementation:

  • Maintain a single Nodus account
  • Create dedicated workspaces for development, staging, and production
  • Implement consistent configurations across environments
  • Establish governance controls to prevent cross-environment contamination

Departmental Data Management​

Scenario: Different departments within an organization require isolated data environments with specific access controls.

Implementation:

  • Utilize a centralized Nodus account
  • Create department-specific workspaces (e.g., Marketing, Finance, Operations)
  • Configure department-specific data access policies
  • Implement cross-departmental data sharing where appropriate

Client-Specific Implementations​

Scenario: A service provider manages data operations for multiple clients.

Implementation:

  • Establish a primary Nodus account for the service provider
  • Create client-specific workspaces with appropriate isolation
  • Configure client-specific integrations and workflows
  • Implement standardized templates across client workspaces