Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry AtHoc
  3. 7.19
  4. Plan and Manage Enterprise Organizations
  5. Enterprise management overview
  6. Manage common content with inheritance
  7. Inherited content and settings in the enterprise or super enterprise

Inherited content and settings in the enterprise or super enterprise

The following objects can be defined at the super enterprise or enterprise organization, and are inherited by each sub enterprise and suborganization. Some objects must be configured to be inheritable before they are inherited.

User attributes

You can find user attributes in the User Attributes section on the Settings screen.
  • Attributes are inherited by lower-level organizations, except for Emergency Community and Organization Hierarchy, which exist at the suborganization level.
  • Attributes defined at the system or enterprise can be viewed, but the only fields that can be modified are the Page Layout options. For the Page Layout options, you can decide whether the attribute appears on the Self Service My Profile page and the User Details page in the
    BlackBerry AtHoc
     management system. If you opt to have it appear, you can decide how much information is displayed: Basic Info, Physical Addresses, or Advanced Information.
  • All aspects of attributes defined at your organization level can be modified with the exception of the attribute type and the organization the attribute is associated with.

Organization code

You can find the organization code in the Enterprise Features section on the General Settings screen. Click
Check Readiness
 beside Enterprise Features. The system checks for user uniqueness (no users have the same username or mapping ID). When the check passes, select the Enable check box next to the
Enterprise Features
 field to enable enterprise aware mobile registration. When enabled, enterprise aware mobile registration enables users to sign on from a mobile device using the enterprise organization code, or the organization code for any suborganization.

Alert folders

You can configure alert folders in the Basic section on the Settings screen.
  • Alert folders created in a super enterprise or enterprise organization are automatically inherited to their sub enterprises and suborganizations.
  • Alert folder names must be unique within a super enterprise or enterprise organization.
  • Alert folders that are inherited by a sub enterprise or suborganization are available only to operators who have permissions to view or manage them.
  • Operators only see alert folders if they have the required roles in their organization to manage alert folders. Inherited alert folders respect the assigned roles of the current operator in the current organization.
  • Inherited folders cannot be edited or deleted by an inheriting organization.
  • If an operator attempts to delete an alert folder that is in use in an inheriting organization, a warning message is displayed. The operator has the option to download information about the inherited alert folder to view and resolve any dependencies before deleting it.

Alert Templates

Alert templates are not inherited by default. To configure an alert template as inheritable, click the
Inheritable
 option in the Alert Template section of the alert template. When an alert template is configured to be inheritable, the following alert template sections are inherited:
  • Alert Template details
  • Content. Locale and bilingual alerting settings are inherited based on suborganization settings.
  • Personal device targeting
  • Duration schedules
  • Settings
  • Delivery templates
The following alert template items are not inherited:
  • User targeting by groups, by users, or by advanced query
  • Organization targeting
  • Mass device targeting
  • Recurrence schedules
These alert template items are inherited only when the inheriting organization has the features or settings enabled:
  • Delivery locale. Only organizations that have the selected delivery locale active inherit the alert template.
  • Mobile Publish settings
  • Bilingual alerting
  • Device targeting
Organizations that inherit an alert template cannot delete the template, but can modify it when using it to send an alert. Inheriting organizations can duplicate, export, and import inherited templates. Any edits made to the template in the parent organization are updated automatically in the inheriting organizations.

Alert placeholders

You can configure alert placeholders in the
BlackBerry AtHoc
 management system. Click
Alerts
 >
Alert Placeholders
 to access the Alert Placeholders manager.
  • Placeholder names must be unique. If you attempt to create a placeholder with the same name as a placeholder in an inheriting organization, an error message appears.
  • For Date, Date Time, or Time type placeholders, the date and time formatting configured in the inheriting organization is used.
  • Alert placeholders created in a super enterprise are automatically inherited from the super enterprises to the sub enterprises and suborganizations.
  • Placeholders created in an enterprise organization are automatically inherited from the enterprise to the suborganizations.
  • Inherited placeholders cannot be deleted in an inheriting enterprise or suborganization.
  • Placeholders that are deleted in a super enterprise or enterprise organization are automatically deleted in any organization that inherited the placeholder.
  • Placeholders that are in use in a sub enterprise or suborganization cannot be deleted from the parent organization.
  • Inherited placeholders cannot be edited or deleted from the inheriting organization.

Security policies

You can configure security policies in the System Setup section on the Settings screen.
If you need to define unique security requirements for a sub enterprise, enterprise, or suborganization, configure them in the Security Policy page for that organization level, so that the change impacts only that organization.

Delivery templates for the
BlackBerry AtHoc
 desktop app

You can configure delivery templates for the desktop app in the Basic section on the Settings screen.

Audio files

You can configure audio files in the Basic section on the Settings screen.

Devices

You can configure devices in the Devices section of the Settings screen.
  • Devices are defined at the system level using the Device Configuration Tool on the
    BlackBerry AtHoc
     server.
  • Administrators can enable or disable a device for each suborganization.
  • Administrators can specify whether the contact information for the device is required for each suborganization.

Feature Enablement

You can enable or disable features from the System Setup section of the Settings screen.
Feature enablement can be defined at the System Setup level, or at the super enterprise, enterprise, sub enterprise or suborganization level and are inherited down the organization hierarchy.

Organization subscriptions

You can enable organization subscriptions from the General Settings section of the Settings screen.
  • Organization subscriptions can be enabled at the super enterprise or enterprise level.
  • Enterprise Administrators and Organization Administrators can overwrite the inherited organization subscription settings by including or excluding specific organizations in a super enterprise or enterprise organization.

User move

You can enable user move from the General Settings section of the Settings screen.
Enterprise Administrators and Organization Administrators can overwrite the inherited user move settings by including or excluding specific organizations in a super enterprise or enterprise organization.