Companies
Where to find it: Manage → Companies
A company is the top level of organisation in the dashboard. Almost every object (users, devices, playlists, layouts, contacts, service contracts, and projects) belongs to a company. When you log in, you’re working within your own company and any companies beneath it.
Companies are managed from the Companies page. The list shows every company you’re able to see: a senior administrator sees all companies, while a regular administrator sees their own company and the companies below it.

Before You Begin
Before creating or managing companies:
• Make sure you have permission to manage companies.
• Understand where the company should sit in your organisation’s structure (see How Companies Are Organised, below).
• Gather the company’s details: address, contact information, and logo.
How Companies Are Organized
Companies are arranged in a tree, where one company can sit beneath another as its parent. This structure decides who can see and manage what:
• An administrator at a parent company can see and manage the devices, users, and content of every company beneath it.
• A senior administrator can see everything, regardless of where a company sits in the tree.
A company with no parent sits at the top level. Top-level companies are usually direct clients or Omnially’s own organisations.
Tip Think of the tree like a folder structure: a company higher up can reach into everything filed beneath it, while a company lower down sees only its own area.
Company Details
Each company record holds a set of details used across the dashboard:
|
Detail |
Description |
|
Name |
Required. Must be unique within its parent company. |
|
Acronym |
A short code created automatically when the company is set up, used as the prefix on order numbers. Senior administrators can edit it. |
|
Address (Line 1 / 2) |
The company’s mailing address. This is separate from the site addresses used on projects. |
|
|
The company’s contact email. |
|
Website |
The company’s website address. |
|
Phone / Fax |
Contact numbers. |
|
Logo |
An uploaded image, shown in the company’s context where relevant. |
|
Custom footer |
Free text shown in footer areas, such as PDF exports. |
|
Support email |
Used wherever a support contact is shown. |
|
Hide users in listings |
When enabled, this company’s users are hidden from certain lists. |
What Lives Inside a Company
A company owns a range of resources, each managed from its own area of the dashboard:
|
Resource |
Where to find it |
Notes |
|
Users |
Manage → Users |
People who can log in. Each user belongs to exactly one company. |
|
Contacts |
Manage → Contacts |
People associated with projects, shared across that company’s projects. |
|
Devices |
Manage → Devices |
Physical hardware. A device belongs to one company. |
|
Service Contracts |
Manage → Service Contracts |
Contract types with tiers, applied to projects. |
|
Playlists |
Content → Playlists |
Media playlists owned by the company. |
|
Media library |
Content → Media library |
Files uploaded by the company. |
|
Projects |
Projects |
Installations the company is part of; each company sees its own view. |
|
Addresses |
Company menu → Addresses |
Shipping and mailing addresses, separate from project site addresses. |
Tip Because these resources belong to a company, they’re only visible within that company and the companies above it in the tree. A contact created under one company, for instance, isn’t visible to an unrelated company.
Managing a Company’s Lifecycle
Deleting and Recovering
Deleting a company doesn’t remove it straight away. It’s set aside and can be recovered from the company list using the context menu. Deleting an already-removed company a second time permanently destroys it.
Important You can’t delete your own company; a senior administrator must do that. And the second deletion is permanent, so recover rather than re-delete unless you’re certain.
Syncing and History
Company records can be kept in step with Omnially’s customer system: creating or updating a company queues it to sync automatically, and administrators with the right permission can trigger a manual sync from the context menu. Every change to a company is recorded, and that history can be opened from the Audit option in the context menu (where permitted).
How Companies Connect to Everything Else
A few relationships are worth understanding, because they explain why some things behave the way they do:
• Users belong to one company, and their role decides what they can do within that company’s area. Administrators can manage users in their own company and any company beneath it.
• Contacts are owned by a company and not shared with unrelated companies. The same contact can be linked to several projects within that company. Some contacts come from an external system and are read-only in the dashboard.
• Devices belong to one company, and the company’s plan decides which device types it can use.
• Service contracts are defined at the company level and then applied to projects, where each application tracks its own dates, tier, and units.
• Projects can be shared by more than one company at once, with each company keeping its own contacts, inventory, service contracts, and files for that project.
• Integrations are set per company and determine what ad-network content can flow through that company’s devices and playlists.
Best Practices
• Plan the tree first. Decide where a company sits before creating it, since its position determines who can manage it.
• Use clear, unique names. A company name must be unique within its parent, so choose names that are easy to tell apart.
• Match the plan to the need. Assign a plan that covers the device types the company actually uses.
• Keep company details current. Up-to-date addresses, contacts, and logos keep exports and support surfaces accurate.
• Recover rather than re-delete. A removed company can be restored; deleting it again is permanent.