10Duke Enterprise release 3 documentation is no longer being updated

Invite device clients

In 10Duke SysAdmin, you create new device clients for an organization by email invitation. You can also use invitations to add existing device clients to organizations.

With the invitation, you add a device client to an organization’s device client group. This grants the device client access to the organization’s licenses that the group is authorized to access.

The invitation can be sent, for example, to the device administrator. The recipient doesn’t need to be a registered user in 10Duke Enterprise, and you can send more than one device client invitation to the same email address.

The invitation recipient must accept the invitation on the physical device (hardware) on which your client application is running. The new device client is created in the system after the invitation has been accepted.

The invitation itself is not targeted at any specific device client: if the recipient accepts it on a device that is already registered as a device client in the system, this existing device client is added to the group specified in the invitation.

Before you start

Invite a device client to an organization

  1. In the left sidebar, go to IDENTITY > Organizations.

  2. In the organization table, select the organization to which to invite the device client, and select Actions > Manage device client groups.

    The organization’s device client group table opens.

  3. In the table, select the group to which to invite the device client.

    The device client will get access to the organization licenses that this group has access to.

  4. Go to the Members tab, and select Actions > Invite Member(s).

    On the side panel that opens, click Next after completing each step.

  5. In step 1 Email, define the email address and language for the invitation:

    • Recipient’s Email: Enter the email address where the invitation is sent.

      This can be any email address that the recipient has access to.

    • Choose a language for the email: Select the language for the invitation.

      The languages available depend on the email template setup in your 10Duke Enterprise configuration.

  6. In step 2 Details, define the recipient and sender names and a personal message:

    • Recipient’s name: Enter the recipient’s name shown in the invitation.

    • Your name: Enter the sender’s name shown in the invitation.

    • Device client name: Define a name for the device client, which is used if accepting the invitation creates a new device client in the system.

      Depending on your client application implementation, the recipient may be able to change the name when accepting the invitation.

    • Personal message (optional): Enter a short personal message.

      This message is added to the default email message. Depending on your client application implementation, it may also be shown in the window where the recipient accepts or declines the invitation.

      The maximum message length is 2048 characters.

      Any line breaks are ignored—the message is shown as one paragraph of text.

  7. In step 3 Summary, check that all the information is correct, and click Invite to send the invitation.

Next steps

You can track the status of the device client’s invitation to see when it has been accepted.

Is the recipient having problems with the invitation?

If a recipient is unable to accept an invitation for a device client, the first thing to check is whether the invitation is still valid. Depending on your 10Duke Enterprise configuration, an invitation may only be valid for a certain period of time.

A common case is that a recipient missed the email because it ended up in their spam folder. Sometimes an email may also be blocked by a firewall, or the email provider may change the structure of the email’s links and cause them to become invalid.

If needed, try resending the email invitation.

If the device client is using a custom URL scheme to open a welcome window from the invitation email, also confirm there are no issues with that implementation.