When a company needs to operate under a Partner, the company should normally be created once in Emiko App. That company then requests access to the Partner and delegates daily use to its own employees from inside the same company profile.
A company should not be recreated many times by separate users just to request the same access again.
This model keeps responsibility and operation aligned.
A harbor is a Partner. A contractor company creates its own company identity in Emiko App and requests access to the harbor. After access has been granted, the contractor can use the harbor services inside the allowed scope.
If the contractor wants employees to use those services on behalf of the company, the contractor invites those employees into the contractor company profile. The employees then act on behalf of that contractor company. Responsibility stays with the contractor company that received access from the harbor.
A Partner may also want internal staff to use Emiko App in a controlled company structure. In that case a responsible person creates the Partner company identity in Emiko App, requests access, and then invites internal staff into that company profile.
This gives the Partner a clean and manageable structure for internal Emiko App operation without creating duplicate company identities for the same organization.
Best practice is simple: request access with the correct company identity once, then invite the people who should act on behalf of that company.
The next step is to explain where Emiko is used, how users sign in, and how Emiko Console and Emiko App fit together.
Public revision 21/05/2026