Contractors and Vendors Need an IHG Sponsor, Not Employee Self-Registration

IHG’s current Network ID instructions give corporate contractors and vendors their own account-provisioning route.

They are told to contact their IHG Corporate contact, who can arrange for the Network ID to be created through MyID.

That is meaningfully different from hotel-employee onboarding.

An external user should not create or represent themselves as an IHG employee simply because a project requires access to an IHG application.

The Business Relationship Comes Before the Account

A contractor Network ID exists because an approved IHG business relationship exists.

The sequence should be:

IHG business need

↓

internal IHG sponsor/contact

↓

Network ID request through MyID

↓

appropriate application permissions

The technology account follows authorization.

It does not create authorization.

Why IHG Uses a Sponsor Model

External users can require access to sensitive hotel, operational or corporate systems without having a normal employee record.

A sponsor provides the organizational context:

Who is this person?

Which company do they work for?

Why do they need IHG access?

What application do they need?

How long should access be necessary?

Those questions are especially important for temporary projects.

A Contractor Network ID Is Not a General Vendor Account

Different IHG systems support different external-user models.

For example, IHG Procurement currently presents a distinct supplier login alongside the hotel-user path.

That means a supplier conducting procurement business does not automatically need the same identity model as a corporate contractor accessing an internal application.

The correct account depends on the service.

Start With the Destination Application

Before requesting a Network ID, identify what the external person actually needs.

Possible examples:

internal corporate application;

hotel technology project;

data or reporting access;

procurement;

implementation project;

support function.

Then determine whether the application uses:

a sponsored Network ID;

supplier access;

its own external identity;

another approved mechanism.

Creating an unnecessary internal account increases administrative overhead.

MyID Is the Provisioning Layer

IHG’s current Network ID registration documentation explicitly tells corporate contacts to use MyID when creating Network IDs for corporate contractors and vendors.

MyID therefore provides the account-management side of this relationship.

The contractor may later use Merlin or a specific application.

The sponsor uses the administration process.

Network ID Does Not Mean Unlimited Merlin Access

Once an identity exists, application permissions still need to follow the user’s role.

A technology vendor helping deploy one application should not automatically receive access to unrelated hotel systems.

Think of the process as two approvals:

Identity: this external person is recognized by IHG.

Authorization: this person can use these specific systems.

The distinction protects both IHG and the external organization.

Third-Party Access Is a Security Issue

IHG’s current public information-security policy states that employees receive mandatory annual training covering subjects including password and email security, vendor relationships and secure data transfer.

The same logic matters for contractors.

Access to an internal platform can expose:

hotel information;

personal information;

commercial data;

configuration;

other protected records.

The fact that a user works for an approved vendor does not make uncontrolled data sharing appropriate.

Contractors Should Use Their Own Identity

A vendor should never use:

a hotel manager’s account;

another consultant’s Network ID;

a shared departmental password;

an employee account created for convenience.

Shared credentials destroy accountability.

If several consultants need access, the sponsor should follow the approved provisioning route for the people who actually need it.

Transfers Between Projects Need Review

A contractor who finishes Project A and begins Project B may still have an active Network ID.

That does not automatically mean the permissions from Project A remain appropriate.

Access should be evaluated against the new business need.

The same principle applies when the contractor:

changes employer;

changes responsibilities;

finishes the engagement;

moves to another IHG project.

Hotel Contractors and Corporate Contractors May Differ

IHG’s current public registration guidance specifically documents the route for corporate contractors and vendors.

A contractor working directly for a franchise owner or local hotel may have a different relationship.

The property or IHG contact should determine the correct route rather than applying the corporate contractor instruction blindly.

Suppliers Have Another Relationship Again

IHG Procurement’s current environment shows why terminology matters.

It distinguishes:

hotel users

from

suppliers.

A supplier account exists for procurement business.

A sponsored Network ID exists for internal workplace access.

A person might interact with IHG in both contexts, but the accounts serve different jobs.

When the Contract Ends

The sponsor organization should have a process to remove access that is no longer required.

External users are especially likely to have time-limited roles.

A completed project should therefore trigger review of:

Network ID status;

application permissions;

shared files;

data access;

external integrations.

Contractor Access Checklist

Before requesting access:

1. identify the IHG sponsor;
2. identify the exact application;
3. determine the required identity type;
4. create the Network ID through the approved route if needed;
5. assign only required permissions;
6. configure required authentication;
7. test access;
8. review access when the engagement changes;
9. remove unnecessary access at the end.

The key principle is simple:

a business relationship authorizes the account; the account does not create the business relationship.