Create or Switch Organisations

Create a separate organisation for each business, customer environment, or operating boundary that needs its own members, credentials, devices, marketplace activity, and settings.

Create an Organisation

1. Open Organisations, or select Create organisation from the Home page when no organisation is selected.
2. Select New Organisation.
3. Enter the organisation name.
4. Select Create Organisation.
5. Back in Your Organisations, select Go to Dashboard beside the new organisation.

Creating an organisation also creates its linked Infuse-IoT Cloud organisation. Both use the same organisation ID, which is shown under Organisation settings > Developer tools.

Organisation names can include letters, numbers, spaces, and hyphens. Keep the name recognisable to your team because it appears in the console, organisation picker, and invitation emails.

Switch Organisations

Use the organisation menu at the top of the sidebar when you belong to more than one organisation. Search Your organisations and select the one you want, or select Browse all to open the full organisation picker. The menu also has a Create shortcut for a new organisation. Switching changes the active organisation context for dashboard pages, access management, API credentials, marketplace instances, and product-specific resources.

Infuse IoT, Marketplace, Access management, and Organisation settings all operate within an organisation. If no organisation is selected, the Home page marks these areas Organisation required and asks you to select or create one first.

Before changing users, credentials, marketplace listings, or device settings, confirm the active organisation shown in the organisation menu.

When To Create Another Organisation

Create another organisation when teams need a hard boundary for ownership, access, credentials, or customer-facing activity.

Common reasons include:

• separating production and testing resources,
• separating two legal entities,
• managing a customer environment independently,
• keeping provider and developer operations under different account owners,
• giving a partner controlled access without exposing unrelated resources.

Do not share API credentials between organisations. Create credentials inside the organisation that owns the resources the integration needs to access.