Skip Navigation

When should I use an enterprise configuration?

Planning your configuration is essential whether you are a small or large organization. You must consider which user roles, security policies, user base size, and content are common to all organizations and whether they need to be centralized by using enterprise alerting, user, and content management.
Enterprise configurations are generally for large, complex implementations with multiple locations that need to segment end users. Small groups find it easier to manage user bases with one or more standalone organizations. The following table compares the use of a standalone organization, multiple standalone organizations, and enterprises with suborganizations.
Setup
Standalone organization
Multiple standalone organizations
Enterprise with suborganizations
Advantages
  • Best for one geographic site
  • Lowest up-front cost
  • One-time configuration of common content and settings
  • Import users once
  • Best for multiple sites or regions
  • Delegate user management to administrators
  • Unique configurations by location
  • Distinct operations per site
  • Works with
    AtHoc Connect
  • Shared configuration between organizations
  • Centralized user views
  • Alerting of enterprise users
  • All the benefits of multiple organizations
  • Works with
    AtHoc Connect
  • Alert folder restrictions are not inherited from one organization to another
Disadvantages
  • Difficult to manage operator permissions
  • Hard to separate team operations
  • Harder to implement
    AtHoc Connect
    effectively
  • Hard to maintain multiple configurations and consistency
  • Requires duplicate effort for entity configuration and security policies
  • No central user management or alerting between peer organizations
  • Users that move between sites have to re-enter profile information
  • Hard to manage personnel accountability
  • Migration can be complex
  • Device configuration is not inherited
  • Some stand-alone features not available on the enterprise