Company Access And Delegation

Create the company once. Request access once. Then invite employees into that approved company context.

Create The Company Once

A company should not be recreated many times by separate users just to request the same access again.

The company identity should be created once in Emiko App.
That company should request access to the relevant Partner.
After access has been granted, additional employees should be invited into the existing company profile.

Why This Matters

This model keeps responsibility and operation aligned.

The company that received access remains the accountable operating identity.
Employees act on behalf of that company, not through separate duplicate company setups.
Usage, permissions, and responsibility stay connected to the correct company.

Example: External Company Operating Under A Partner

A contractor creates one company identity in Emiko App and requests access to the harbor.

After approval, the contractor invites its employees into that company context. The approved company remains responsible for their use.

Example: Internal Staff Acting On Behalf Of The Partner

A responsible person creates the Partner company identity in Emiko App, requests access, and invites internal staff into the same company context.

This gives the Partner a clean and manageable structure for internal Emiko App operation without creating duplicate company identities for the same organization.

Primary Rule

Best practice is simple: request access with the correct company identity once, then invite the people who should act on behalf of that company.

Next Step

Confirm that each employee can sign in and see only the approved scope.

Check Login And Identity Troubleshoot Access