Multi-organisation and reseller mode

Who asks for it

A holding's companies, a healthcare group's hospitals or a reseller offering screens to its customers all come with the same need: one server, but each organisation's screens, content and users kept apart. An editor in one organisation should not see another's content or deploy to someone else's screen by mistake.

How it could work with MIA

Today one MIA installation serves one organisation. It has Yönetici (admin), Editör and İzleyici (viewer) roles, unlimited users, and an audit log that records who changed what. Tags and locations let you group screens by branch. If organisations must be fully separated, a separate installation for each is possible today. Instead, organisation spaces on one server can be built for your installation: each organisation's folders, programs, screens and users would be kept apart, and a top-level administrator would oversee them all from one place. For a reseller, adding customers, screen quotas and reports per organisation could also be in scope. We would also discuss how licensing fits this structure.

What we need to know to scope it

• The number of organisations or customers, and the total number of screens
• Whether organisations share any content
• What the top-level administrator needs to see
• Who runs the server and where

With this we would suggest mapping your structure together first and deciding which separation you really need. Scope, timing and price are agreed for each project.