Sites
Run several operating units, such as plants, under one contract.
Sites let one company run several operating units under a single contract. The company that holds the contract is the parent. Each operating unit is a Site: a company of its own, with its own users, automations, scripts, templates, dashboards, apps and Shop Floor.
Sites are part of the Enterprise license. Your DataMagik account team sets them up for you.
What a Site shares with its parent
- License. A Site has no license of its own. It uses the parent's license and has every feature the parent has. When the parent's license changes, every Site changes with it at the same moment.
- Usage pool. Documents, script runs, API calls and storage from the parent and all of its Sites count against one shared allowance. Quota and billing notices go to the parent.
- Storage. A Site's files are kept in the parent's storage, in a separate area for that Site.
What a Site keeps to itself
- Its users and their roles.
- Everything it builds: automations, scripts, document templates, dashboards, apps, lookup tables and Shop Floor setup.
- Its operational alerts. Automation failures, Shop Floor escalations and approvals stay with the Site that owns them.
Sites and Locations
A Site is a separate company. A Location is a plant or warehouse inside one company: one Plex PCN, with its credentials and time zone, used by Shop Floor, Shipping, DataMagik Mobile and Asset Health.
- The parent and each Site have their own Locations. A Site's Shop Floor setup starts empty and belongs to that Site.
- Plants you already run as Locations in the parent stay Locations.
See The plant model and Getting started with Shop Floor for setting up Locations, and Connectors for connector groups, which are something else again: the connectors at one physical place.
Switching between Sites
The company switcher in the top navigation bar lists the parent and its Sites together, so you can move between them the same way you switch companies. Deactivated Sites are not listed.
In DataMagik Extend, each company can have a Plex PCN. On a Plex page with that PCN, Extend switches to the matching company or Site by itself. If no company has that PCN, or more than one could match, Extend stays where it is. An administrator sets the PCN on the Security Settings page of the parent or of the Site; to set a Site's PCN, switch to that Site first.
Who can work in each Site
Roles apply per company. A role given in one Site applies in that Site only; it is not copied to the parent or to other Sites.
- Parent administrators are administrators in every active Site. A parent administrator is a person whose home company is the parent and who has DataMagik - Security there. Someone who holds Security in the parent only through access from another company, such as a consultant, does not become an administrator in the Sites.
- Everyone else needs access to a Site and a role in it.
Parent administrators manage this under Admin → Sites: people. The page shows everyone in the parent and its Sites, with their roles in each company. From there you can:
- Change someone's roles in one Site. Their roles in other companies stay as they are.
- Invite someone to a Site with the roles they need there. To invite a person who is not yet in DataMagik, add them in the parent's user manager first.
- Remove someone from a Site. This removes their access to that Site and their roles in it. Their home company is never changed.
Enterprise Viewer
Enterprise Viewer is a role for people who need to see the whole company, such as executives. It is given at the parent only. An Enterprise Viewer reads summaries across the parent and its Sites, such as usage, without signing in to each Site.
Usage across the family
The parent and its Sites share one plan. Documents, automation API calls, storage and Shop Floor workcenters from every company count against the same limits.
- In the parent, the Usage Dashboard shows a Shared pool card. Open Usage by Site from it to see how full each limit is, how much each company used, and this month's Site fees.
- In a Site, the Usage Dashboard shows that Site's own numbers and how full the shared plan is. Only parent administrators see the split by company.
- Quota alerts at 80% and 95% go to the parent's administrators. Use past a limit is billed to the parent as overage; nothing is blocked.
Plex access in a family
As soon as a company has a Site, Plex access rules are always on for the parent and for every Site:
- SQL access roles decide which Plex databases, tables and PCNs each user can query.
- Plex API access decides which DataMagik roles can use Plex data sources and the Plex API from scripts.
A Site can only reach the plants it owns. A parent can reach the plants its Plex logins cover.
When your first Site is created, people who could use Plex before keep that access:
- Everyone at the parent is given the Full Access SQL access role, so nobody loses access. Your administrators can then narrow it.
- Every DataMagik role at the parent is allowed Plex API access.
- The new Site gets a Full Access role, ready to assign to its users.
If your administrators had already set up SQL access roles or Plex API access, or turned these rules on themselves, nothing is changed. Creating more Sites later never undoes changes your administrators made.
While your company's own Plex access setting is off, people and roles added later are set up the same way: a new user (added, invited through single sign-on, or given access from another company) gets the Full Access role, and a new DataMagik role is allowed Plex API access. A user who belongs to no DataMagik role cannot use Plex data sources or the Plex API from scripts until they are given one. If your administrators turn the setting on, they assign access themselves under Admin → SQL Access Roles and Admin → Plex API Access.
Pricing
Each Site has a monthly fee, set by your license tier. A Site is billed for every month in which it was active at any point, including the month it was deactivated.
Creating a Site
Your account team creates Sites for you. Each new Site starts as an empty company and joins your family from the current month. The number of Sites you can have is part of your agreement; ask your account team to raise it.
Deactivating a Site
A Site can be deactivated, for example when a plant closes. While a Site is deactivated:
- its users cannot sign in to it;
- its schedules, triggers, kiosks and agent triggers are paused;
- its API keys and connected apps are refused;
- file-gateway logins to it are refused.
Nothing is deleted. Its data and files are kept, and it can be reactivated at any time, which resumes everything. Sites are never deleted.
If Sites are removed from your license
Existing Sites keep working. You cannot add new Sites until Sites are added back to your license. Your account team will contact you to resolve it.