Documentation

Mistake on this page? Email us
Docs › Setting up your account › Signing up or logging in to Device Management Portal

Signing up or logging in to Device Management Portal

Tip: If you were invited to join an existing team on Device Management Portal, your invitation email will take you to a login page, and you don't have to follow the instructions below. You may still want to look at the suggested content in the further reading section.

If you want to use Device Management, you can sign up or use your existing Mbed account as a free tier Device Management account. You can upgrade that account to a commercial one without losing any existing data. For information about upgrades, contact the Arm sales team.

Mbed.com and native Device Management accounts

There are two account options for Device Management services:

  • An Mbed.com account, which is available to anyone registering to Portal through the website. You are then the administrator of a new team.

  • A native Device Management account, which you can get by:

    • Contacting Arm and requesting one. You are then the administrator of a new team.
    • Getting invited to join an existing team (the team's administrator can invite you).

    If you're invited to join a team, you may find that the team uses a third-party identity provider (IdP), such as Google. You must sign in with that identity provider. If you are experiencing issues, please talk to your team administrator about changing account types.

Users and teams

You can join multiple teams without having to set up multiple users. However, you can only be logged in to one team at any one time, and can only see the devices belonging to the team you're logged in to. If you are a member of team A, and you want to work with the devices of team B, ask team B's administrator to invite you to that team.

Signing up to Device Management with an Mbed.com account

Note: When you sign up, you become the administrator of a new team. If you want to join an existing team, ask that team's administrator to send you an invitation instead of signing up. (Don't worry if you've already signed up - you can be a member of more than one team.)

To use Device Management Portal, you need to sign up to an account:

  1. Go to the signup page.

  2. Fill in your details.

  3. Click Sign up.

    You receive an activation email.

  4. Use the email link to log in and verify your account.

    You are taken to an activation page.

  5. Click Activate Pelion Device Management account.

    The page shows your new status.

  6. The activation page gives you three options: find hardware, try the tutorial or access Device Management Portal.

    You can also go directly to Device Management Portal and choose the Log in with account.mbed.com option.

To add others to your new team, see the team management section. See further reading for more resources.

Logging in

If you already have an account and want to log in, there are several options, depending on your account's identity provider:

  1. Go to Device Management Portal.
  2. Choose the login option that matches your account's identity provider:

    • The default login option is a Pelion Device Management (native) account, Log in with email and password.

    • If you are using an Mbed.com account, click Log in with another provider > Log in with account.mbed.com. You are taken to the Mbed login page.

    • If your team uses a third-party identity provider, click Log in with another provider, and select your identity provider. You can also click Log in with team SSO, but you must know your team name to use this option.

      Tip: You can access the team login page directly by adding team/team-name to the Portal's URL. For example, https://portal.mbedcloud.com/team/myteam.

Switching teams

If you are a member of multiple teams and you access all those teams using the same user account (email address), you can switch between teams without logging out and back in. Click the current team name on the top of the navigation bar, and select a new team.

Note: You cannot switch between teams that use a different identity provider; you have to log out and back in.

Further reading

Next