Companies represent the highest level of organization in xMatters. As an xMatters super administrator, you can create, modify, and manage Companies through the xMatters web user interface.
In a multiple-Company deployment, some system components are common to the xMatters infrastructure and controllable only by the Super Administrator. These components are not Company-specific, and include Nodes, Device Engines, Protocol Providers, and Clusters. Other features viewable only by the Super Administrator include Component Status Reports, Scheduled Jobs, and Clear Runtime History. Where appropriate, this document identifies whether components are Company-specific in the section introducing and describing each component.
In an xMatters deployment with multiple Companies, each xMatters Java Client <agent_client_id> must be unique across the deployment (i.e., not just unique across a Company), because agent client IDs are not qualified by Company. This restriction is the responsibility of the host Company, and is not enforced by the xMatters application. If this restriction is violated, external service requests and messages may not be routed properly.
| Note: | The number of Companies available in an xMatters deployment is controlled by your licenses. |
| Note: | When you add a new Company to a multiple-Company deployment, xMatters automatically creates the default out-of-box Event Domains, script packages, Sites, and other required settings for the new Company. |
In multiple-Company xMatters deployments, all Users, Groups, Teams, Team templates, and Dynamic Teams are Company-specific. However, identifiers are only unique within a Company, not across the entire deployment.
For example, each User within a Company must have a unique User ID, but a User in one Company might have the same User ID as a User within another Company in the same deployment.