2. ginlo Management Cockpit

_images/cockpit_01.en.png

2.1. Einleitung

ginlo Business is the secure instant messenger by ginlo.net GmbH. Sending messages with ginlo Business is completely secure and confidential thanks to end-to-end encryption. ginlo Business improves internal communication between colleagues and teams and thereby increases their productivity.

In one-to-one or group chats, users can confidentially exchange text messages, video and voice messages, images, files, and much more. The service complies with European data protection standards and is operated exclusively on German servers.

2.1.1. Management Cockpit

The Management Cockpit provides a platform for simple and intuitive user management and configuration of the ginlo Business app, all designed to meet your compliance requirements. The web interface makes it easy for IT administrators to distribute the app within a company and manage it centrally. Administrators can not only configure the functionality of the app, but also tailor its design and send messages to a broad audience. The innovative Management Cockpit also encompasses the following functions:

  • User and license administration

  • Channels and group management

  • Reporting dashboard

  • Security and compliance settings

  • App design configuration

This documentation is intended for administrators and aims to provide an overview of the ginlo Management Cockpit. It instructs them on how to prepare optimally for a rollout of ginlo Business to the larger company and gives best practices to effectively manage the use of the messenger.

2.1.2. Registration

As an IT administrator, you can register for the ginlo Management Cockpit on the ginlo website. There are two options for this.

  1. You order alicense, in which case a Management Cockpit account is created by default.

  2. You register for a free test account.

Both options require entry of personal data such as name, e-mail address and mobile number. Based on the provided data, you’ll receive an e-mail containing a personal browser certificate as well as a certificate password sent via text message (2-factor authentication via separate channels).

Once this certificate has been installed, the Management Cockpit can be accessed via the URL https://cockpit.ginlo.net.

Important

Following first-time login, you’ll automatically receive a Recovery Code by e-mail. Please keep it in a safe and secure location. If the regular password gets lost, it represents the only possibility for restoring the administrator account.

2.2. Users

ginlo Business can be rolled out and managed in different ways. The Management Cockpit can be used as an administration interface to create users and assign licenses manually or automatically. This chapter Users describes the manual process, while the chapter LDAP Data explains the integration of existing data systems to automate the process.

In addition, organizations with enterprise mobility management solutions (EMM) can automate the rollout using the existing EMM (see chapter EMM Rollout).

The first step towards a manual rollout via the Management Cockpit is creating users who will then be assigned licenses in a subsequent step. In the Users tab, click Create user data in the lower right. Enter the user’s first and last name as well as their e-mail address and/or mobile number. As an option, you can also add the user’s department. This data will later be visible in the user’s profile.

You can also assign optional keywords to associate the user with a functional area within the department. This is also helpful later when searching for a specific user. Save your entry.

Once a user has been created, a dialog opens to ask if you wish to assign a license right away. You can postpone this until later if desired, as described in chapter Licenses.

_images/cockpit_02.en.png

A Quick Create function is also available for creating several users at once. Simply click the empty cells of the last row of the user administration overview, enter the data, use the Tab key to switch cells, enter a pre-defined keyword and save the input.

The Import user data function allows you to import an entire directory of users into the Management Cockpit. A CSV import template has been provided to make this easier. To download it, simply click on the blue CSV Import & Export link in the upper right of the overview page, then click Simplified CSV for one-time user creation in the Select What to Import section. Once you’ve downloaded it and filled it in, click the gray Import user data button in the upper right to upload your data.

_images/cockpit_03.en.png

Important

Please note that the import template uses the comma-separated value format

“last name,firstname,email,mobile number,(keyword),(department)”.

The keyword and department fields are optional but helpful for user categorization.

You can edit individual users by clicking the corresponding row. Each user is assigned an 8-digit ginlo ID that functions as their identification. The user’s contact data, including mobile number and/or e-mail address, can be changed at any time, although the changes will not become permanent until verified by the user in the messenger app.

You can also assign a department or keywords. The user’s department will be shown in their profile and will be visible to all other messenger users, while the keywords are intended solely for internal organization and administration using the Management Cockpit.

Once activation is complete, details about the user’s devices will also be shown below the keywords (see also chapter Devices).

_images/cockpit_04.en.png

Important

  • Existing users that you reimport will not be overwritten. Only entries of new users will be imported from the template.

  • Users can be completely deleted from the Management Cockpit by clicking Delete user in the upper right.

  • When an administrator deletes a user, such as when the user has left the company, the entire account is deleted. In case the user has created a backup, it becomes unusable. The user’s license is also immediately locked, and the data record is deleted in the backend. The user immediately loses access to their communication. The messenger app resets automatically to the registration screen and the user can no longer back up their data.

2.3. Devices

At any time, you can get an overview of the devices via which your users access ginlo Business. To do so, you can export a CSV file that includes the following data:

  • Device name

  • ginlo Business version

  • First name, last name, and ginlo ID of the user

To export the CSV file, click CSV Import & Export in the Users tab. Then click Export all used devices into a CSV file in the Select What Data to Export section.

_images/cockpit_05.en.png

2.4. Licenses

Licenses can be assigned to users either immediately following the creation of individual users or at a later point in time. In the Licenses tab, click the green Assign license button in the lower right. A two-column o verview window then opens. Unassigned licenses and their period of validity are shown to the left; the available users and their respective statuses are shown on the right.

Tick the checkbox in front of the desired users and licenses and then associate them by clicking the green button to the lower right.

_images/cockpit_07.en.png

Important

As soon as a license is associated with a user, this newly created user is then automatically invited to download ginlo Business. The status visible in the overview then changes from gray **(User created)* to yellow (License assigned).

Users with an e-mail address receive an e-mail with a corresponding download link and additional information, whereas users with solely a mobile number receive their invitation via text message.

Ensure that all preparations for rollout have already been made before assigning licenses.

_images/cockpit_06.en.png

Once the user downloads the ginlo Business app from the Apple App Store or Google Play Store hey then register using their mobile numbers or e-mail addresses.

Alternatively, users can also register via ginlo Web Messenger. Here, registration only works with an e-mail address. After registration, they can add additional devices to the same account.

During registration, an invitation to join the company’s ginlo Business team is shown; this allows the administrator to manage the user’s app. For more on this, see chapter App Management. Once the user agrees to this, the user’s status in the license overview page changes to License active (green). If the license expires, the status on the overview page changes from green to License expired (red).

It’s also possible to revoke a user’s license. Click the three blue dots to the right of the user’s row in the license overview page and select Revoke license. Once you’ve confirmed by clicking Revoke license in the dialog box, the license is available for assignment to another user. While the previous user’s data is not deleted, the app will be locked for that user until a new license is assigned.

_images/cockpit_08.en.png

Shortly before the expiration of a license, both user and administrator will receive a notification of the upcoming termination. Within the Management Cockpit, the user’s respective row will be marked in red with a “warning triangle” to indicate the pending change to the user’s status.

A user’s license can be renewed in the license overview page. To do so, click the three blue dots in the corresponding row of the license and select Renew license. Select the desired license from the pop-up window and execute the renewal. If no additional licenses are available, you can request as many new licenses as desired by clicking the gray Order new license button in the upper right. The new licenses will be available immediately and invoiced accordingly. In Settings, you can find your order history at the bottom of the page.

2.5. Contacs

ginlo Business offers various features for convenient contact management compliant with data protection regulations. There are three different contact directories that can be used to find other users among colleagues and business partners.

2.5.1. From the address book

This directory is based on the contacts stored in the local address book on the user’s smartphone. After registration, every user decides individually if they grant the app access to their contacts to identify ginlo users among them. If access is granted, contacts are hashed and then matched with existing user accounts.

No contacts are stored outside the app or passed on to third parties. If the user denies access to their address book, the other two contact directories are still available; besides it’s also possible to search for a specific user by mobile number, e-mail address, or ginlo ID.

The administrator can prevent access to device address books by enabling the option Activate restricted user group in App settings (see below).

2.5.2. E-mail Directory

The e-mail directory can be used if the user has added their business e-mail address to their profile and verified it. This directory includes all users from the same verified e-mail domain.

2.5.3. Company Directory

Once a user has accepted the team invitation (and thus allowed the administrator to manage their account), they have access to the company directory. It includes all users from the same Management Cockpit that have also accepted the team invitation.

A new user will be automatically added to the company directory and will be visible for their colleagues as soon as they have registered their account. Users in the company directory are marked with the green label “Internal” and are considered trusted. In the user profiles, all data entered by the administrator (last name, first name, mobile number, e-mail address, department) can be viewed.

The administrator can change the name of the company directory in App settings > Contact guidelines. In addition, they can restrict communication to users within the company directory using the option Activate restricted user group. Chatting with external ginlo users is then no longer possible. Existing chat with contacts outside the company directory will be disabled, i.e. users can no longer send messages to or receive messages from external users.

_images/cockpit_09.en.png

2.6. Groups

A key component of instant messenger communication involves discussion between participants of groups. You can promote quicker and more efficient collaboration within departments and teams by creating group chats within the Management Cockpit to bring users together.

Users that have been assigned to a group by an administrator automatically receive an invitation to join the group. Particularly for new employees, this can accelerate onboarding significantly and help employees find the right colleagues more quickly.

To create a new group, click the green Create new group button in the lower right of the Groups tab. Enter a group name (e.g. “Marketing”) and, as an option, a group image to be shown to the members. You can then select group participants from the existing users. In the right part of the window you can search for users by name or keyword and then select the desired user(s) via the checkboxes next to their row.

Note

A group can have up to 100 participants.

Save the new group by clicking the green button in the lower right. As an administrator, you have the option at any time to delete the group or to add or delete specific users. You do not have the ability to read the content of group communication, or to send messages to the group. If you want to send broadcast messages from the Management Cockpit to your users, please use the Channels. For more on this, see chapter Channels.

_images/cockpit_10.en.png

Important

  • As soon as you add newly created users to a group, they will automatically be invited to register a ginlo Business account and assigned to the group.

  • Changes to the group picture and name are immediately visible to all members of the group.

2.7. Channels

Channels allow administrators to centrally send messages, images, and files to a defined group of recipients, as well as to inform up to 1,000 employees quickly and throughout the company about new developments. External RSS sources can be integrated as well.

To create a channel, click the green Create new channel button in the Channels tab. The process is similar to that of creating groups: Enter a channel name and, as an option, an image and select the users who should receive the channel. In addition, you can also assign write access to channels for selected individual users. These users then function as authors, with rights to send messages to the channel from the app. These messages are also displayed in the Management Cockpit. Other users cannot respond within a channel. As soon as the new channel has been saved, an invitation is automatically sent to all users defined as members.

_images/cockpit_11.en.png

Create a new message by clicking the row for the desired channel within the channel overview page. Enter your message, including an image if desired. A preview is shown on the right side to allow you to check what will be shown to the users — text and images will be shown in one joint message. The selection function also allows you to attach files from your computer. These cannot be combined with message texts, however, and must be sent separately.

If you add a link, be sure to enter the complete URL, including https://, to ensure that smartphones will parse it correctly.

Once you’ve created your message, you can either send it immediately or use the drop-down menu below the image selection function to define a desired delivery date and time. Select a desired date and time in the future and click the gray Send button. Messages assigned a date and time in this way will not be sent immediately, but rather on a time delay. From a technical standpoint, the message is sent immediately to the server, but is not delivered to the user until the specified date and time.

This allows for the creation of a simple editorial schedule for delivery of messages, such as a newsletter created over the course of a week for delivery on the weekend. The time of delivery is shown alongside time delayed messages. You also have the option here to delete messages that have already been sent to the server but not yet delivered to the final recipients. Please note that this only applies to time-delayed messages sent using the Management Cockpit.

Click on the blue Edit channel link in the upper navigation bar to edit the channel name or image, add new users to a channel, delete existing users, or assign write access. You can also delete the entire channel.

_images/cockpit_12.en.png

The channel overview page provides a quick view of which channels have been created and how many users have been assigned to each channel. Invited users are those you’ve added to the channel. Users who have registered their account and accepted the team invitation are automatically counted as Joined. Users who haven’t yet completed their registration or haven’t yet accepted the team invitation are counted as Outstanding. This ensures that no unauthorized users have access to confidential content within channel communication.

_images/cockpit_13.en.png

Besides sending messages manually, you can also specify RSS sources. Their content will then be sent automatically. This allows you to integrate external content providers (e.g. publishers, websites), but also internal content sources (e.g. HR news, IT alerts, intranet notifications) in the messenger.

To do so, create a new channel. In addition to a name and image, enter the external RSS source as a URL including https://. Click Check to verify that the RSS feed works correctly. Feeds based on the 2.0 specification are supported. During the check the latest content of the feed is imported and shown in the channel preview. In the next step users can be assigned as described above. They will then receive automated invitations to the channel.

When sending confidential content from internal RSS sources, e.g. alerts, you can use VPN/IP filtering to ensure that only your employees can access the content. To do so, please get in touch with our Customer Care at b2b-support@ginlo.net. Before rolling out an RSS channel to all users, we recommend you check the message layout and frequency in the messenger app.

_images/cockpit_14.en.png

2.8. App Design

ginlo Business is a modern communications tool, and as such can be customized to match your corporate design (CD) guidelines. Your logo and the color scheme in the app can be changed from within the Management Cockpit. This improves acceptance among employees and turns the app into “your” corporate instant messaging platform.

_images/cockpit_15.en.png

The customization process is available under the App Design tab, beginning with an option to upload your corporate logo via the Select image button. In the window that opens, select the logo in PNG format and click Open. Your logo opens in a preview. You can use the scroll wheel of the mouse to enlarge or reduce the section and drag the logo to position it. The blue border shows the maximum size of the logo, but it does not have to be completely filled. Once you’ve applied your changes, the logo is displayed in the preview next to the Select image button as well as in the design preview on the smartphone.

In a second step, you can configure the color scheme for the app. The precise value can be entered in RGB (Red-Green-Blue) or hexadecimal format. For precise color settings, please contact your corporate communications department.

Note

Changes only affect managed accounts. They usually become active after 5 minutes, but at the latest after 1 hour. They are visible after closing and restarting the app.

2.9. App Settings

To ensure that ginlo Business satisfies your company’s compliance and security requirements, you can use the App Settings tab to configure factors such as contact guidelines, password guidelines, password complexity, and media guidelines. The app settings components of ginlo Business are based on Android for Work (Android 5.0 and newer) and Managed App Configuration (iOS 8.0 and newer), to ensure secure and quick app configuration.

The password guidelines serve to protect the application and its data. You can either trust the users to choose an appropriate protection setup for the app or enforce stricter security at the Management Cockpit level, e.g. a password prompt each time the app is started. If you also define password complexity criteria, then users must satisfy those rules when selecting a new password within the app. The media guidelines serve to control local saving, sending, forwarding, exporting, and sharing of communication with other apps.

_images/cockpit_16.en.png

Important

  • The settings only apply to user accounts managed by the administrator.

  • The users must have accepted the team invitation displayed within the app before the settings you’ve defined here can take effect.

  • Saved changes usually become active after 5 minutes, but at the latest after 1 hour.

  • Please note that your settings, such as media guidelines, restrict the functionality of the app.

2.10. App Management

Before the administrator can manage an account, the user must first give their consent. Once a user is assigned a license, the automatic processes for “onboarding” the account begins running in the background. Depending on what data for the user has been provided, the invitation is sent via e-mail or text message.

After registration, the user is queried through a pop-up window whether they accept the invitation to join the company’s ginlo Business team and thus give their consent to assign account management rights to the administrator. If the user is already using the app, then the query is issued when the license is assigned. If the user clicks Accept, the user status changes to License active and the administrator can manage the account.

From that point forward, changes to app settings and app design are applied automatically for this user, as are assignments to groups and channels. Channels can then also be received as messages from the Management Cockpit.

_images/cockpit_18.en.png

If the user declines the team invitation, the account remains outside the messenger management system and a “warning triangle” appears next to the user state License assigned. The administrator can manually re-send the team invitation via the Edit User function. To do so, click :petro:`Re-send request`. The user will then see the pop-up window again.

For security reasons, the user must actively consent to app management rights before the administrator can manage the account.

_images/cockpit_17.en.png

Important

Once the user is subject to administrator control via the app management system, the administrator has permission to delete the account and all its communication data, such as after the employee leaves the company. The application then resets back to the registration screen

2.11. Dashboard

The Dashboard tab offers an effective method for control of the Management Cockpit, using anonymized data for effective reporting and to establish transparency in instant messaging usage. You can find statistics regarding user activity within your firm, data on administered groups and channels as well as a summary of the Message Mix.

The drop-drop menus in the upper right can be used to select between Daily (DAU) and Monthly Active User (MAU), as well as a time frame between 1 week, 1 month, and overall time frame. A DAU reflects a user active in the past day, while MAU reflects the number of users during the last 31 days. Data up to the day before is included.

_images/cockpit_19.en.png

Activity displays the current number of active users (user status License active) and their distribution between the Apple iOS and Google Android operating systems. The charts under Activity show the number of sent messages and the number of users active at a specific date and time. The Administered Groups area contains a list of all groups created by the administrator, including group name, number of users and number of messages within the reporting period.

Clicking an individual group displays a line graph alongside the list, showing the number of messages within the group during the selected period.

_images/cockpit_20.en.png

A pie chart to the left of the Groups list shows the size of the respective group (in yellow) based on the number of messages compared with all other administered groups. Groups created by users are displayed together with the number of messages from the same time frame. Due to the nature of private encryption, data on group names and number of participants is not available.

_images/cockpit_21.en.png

Channels work similar to groups, with a listing of all channels available together with users and messages as well as a relative distribution indicated through a pie chart. Beyond this, there is the option to click a channel to view the top 5 broadcast messages. The ranking reflects the conversion rate, meaning how many users opened an image or file or clicked on the link. There is also data in the Message Mix section showing the total number of messages sent during the reporting period. This reflects the sum of individual messages, group messages and channel-based messages.

_images/cockpit_22.en.png

2.12. Recovery Code

When a user forgets their account password, it is possible to use the recovery code to unlock the messenger. Admins can deactivate this function at any time in the App Settings of the Management Cockpit. If the recovery code feature is enabled, users can request the code on their own, so it will be sent to them automatically (self-service mode). Alternatively, you can force manual administrator approval within the Management Cockpit.

_images/cockpit_24.en.png

By default, the self-service mode is enabled. In the messenger, the user can select Forgot your password? to automatically receive the recovery code via SMS or e-mail. If the Force recovery code via administrator option is activated in App Settings, then the administrator will receive an e-mail with the user’s recovery code request. At the same time, a “warning triangle” is shown in the Management Cockpit next to the user’s name to inform the administrator that action is needed.

Important

If the recovery code feature is disabled and a user forgets their password, all data on the device is permanently lost because the cryptographic key to this data is protected with the password and the recovery code. This setting can be useful to ensure that administrators cannot access user data even if they have access to both the device and the Management Cockpit.

_images/cockpit_23.en.png

To respond to a recovery code request as an administrator, use the Edit User function. For users with a verified e-mail address, the code can automatically be sent from the Management Cockpit. Click Send Recovery Code to do so.

For users without a verified e-mail address, the administrator can view the code so as to provide it by phone, for example. In the messenger app, the user must enter the recovery code and then enter a new personal device password.

Any password complexity criteria defined in the App Settings of the Management Cockpit apply. After defining a new password, the user can access the chat overview again and use the messenger app as before.

Important

The Recovery Code function is only available to users who are under the oversight of an administrator. The user must hence have previously accepted the team invitation. Otherwise there are no options available for unlocking the app and a full reset is required, which causes all chat content to be lost.

2.13. LDAP Data

In addition to the simplified import process via CSV for one-time user creation, you can also import data to the Management Cockpit using automated processes, e.g. from an LDAP directory. In contrast to the simplified process, the LDAP update allows you to automatically create, edit, and delete users. In addition, users can be automatically assigned to groups and channels. If the respective groups or channels don’t exist yet, they will be created as part of the import.

In addition to an LDAP directory, any other system can also be used as a source system if the user data it provides corresponds to the defined data structure. In the Download area of our website at https://www.ginlo.net/en/business/support/downloads/, you can find detailed guides for the two-step process consisting of an LDAP export (“Management Cockpit - LDAP Interface”, currently available in German only) and Cockpit import (“Management Cockpit - LDAP Import”).

_images/cockpit_25.en.png

For continuous LDAP synchronization, a REST API is available. Users are not only created automatically, but also assigned licenses, groups, channels, and keywords. If any of the items to be assigned don’t exist yet, they will be created via the interface (for details, please refer to the guide “Management Cockpit - LDAP Interface” at https://www.ginlo.net/en/business/support/downloads/, currently available in German only.)

The variety of features allow for easy, individualized integration of a user directory service (e.g. LDAP, AD), simplifying user management within the company. At the same time, the update interval can be set from within the company’s own infrastructure. For successful authentication against the interface, please enable LDAP synchronization via API in the Cockpit Settings.

_images/cockpit_26.en.png

Afterwards, a certificate is generated and sent to the registered administrator via e-mail. The corresponding certificate password is sent via SMS. Basic authentication serves as a second authentication channel. You can view all relevant access data in Settings. The following image provides an overview:

  • Username: first part of basic authentication

  • Password: second part of basic authentication

  • User certificate fingerprints: fingerprint of the public certificate to verify the authenticity of the certificate you’ve received

  • Valid until: End date of certificate validity

  • Monitoring URL: URL to monitor the statuses of the last 10 imports. No authentication required.

_images/cockpit_27.en.png

2.14. EMM Rollout

You can not only roll out the app via the Management Cockpit, but also roll out and register it via existing enterprise mobility management solutions (EMM). Compatible EMM solutions must support the AppConfig standard and thus also support Android for Work (for Android 5.0 and above) and/or Managed App Configuration (for iOS 8.0 and above).

Warning

Before starting the roll out make sure that there are NO other ginlo Business accounts active that use the email adresses you plan to use. If there are, this will lead to problems with your EMM rollout.

If you have such accounts please contact the ginlo support to have them removed before starting your EMM rollout.

To assign licenses to users and manage app design, groups and channels, please use the Management Cockpit. To configure app settings (password policy etc.), you can use either the Cockpit or the EMM. Please note that app settings in the EMM may overwrite rules defined in the Cockpit. This is why we recommend you define these settings either only in the Cockpit or only in the EMM.

If you want to roll out a large number of users, we recommend automated EMM registration via the existing EMM solution. This approach has the following advantages:

  • Rollout via the existing EMM solution into the secure EMM container on the device

  • Quick user registration based on LDAP data speeds up the process

  • Fewer sources of error for the user, e.g. rejection of the team invitation that is required for app management

  • Automated assignment of licenses via the backend

  • Automated import of user data into the Cockpit

Here’s how to perform an automated EMM rollout (using MobileIron as an example):

  1. In the Management Cockpit Settings, enable Automatic EMM registration. For a quick rollout, also enable Enforce quick registration on the terminal.

    Note

    If you enable quick registration, registration is fully automatic, without the need for admin or user intervention in the process. However, you should not use this feature if there are already managed devices in your company with ginlo Business installed as these existing user accounts will be overwritten during rollout.

    Furthermore, a prerequisite for the EMM rollout is that the company domain, e.g. @example.com, in the Cockpit matches your registered domain in the EMM.

    _images/cockpit_28.en.png
  2. Copy the security token displayed. Add the token to the “EMM Rollout Plist”, which you can find at https://www.ginlo.net/en/business/support/downloads in the “MDM Documentation” section. Make sure to also copy the {} brackets correctly into the string. The Plist with the token is later needed to map the EMM to the Cockpit.

    _images/cockpit_29.en.png
  3. As an option, you can configure the app design in the cockpit before the rollout so that users will see it directly when registering. If you want to keep the standard design, you can now log out of the Cockpit. The rollout continues in the EMM.

  4. Open the EMM. If you haven’t done so already, create users based on LDAP data including last name, first name, and e-mail addresses. This data is later used for automatic app registration, i.e. users don’t have to enter and verify it manually. Assign one or more labels to the users, so you can distribute the app to various groups of recipients.

  5. Go to Policies & Configs > Configuration and create a new configuration profile. Use Managed App Config for iOS or Android Enterprise for Android. Add the Plist including your ginlo Business security token to the profile. Assign the configuration profile to the labels you’ve created.

  6. Go to Apps > App Catalog, click Add, and search for the ginlo Business app in iTunes/Google Play. When importing the app, you can, as an option, define App Configurations directly in the App Catalog, e.g. password and media guidelines.

  7. Distribute the app to your labels. The app will then be rolled out to the EMM container. Users only need to tap the app icon to start the registration and select Create Account.

  8. The automated app registration accesses the LDAP data (last name, first name, e-mail address) and the security token, accepts app management in the Cockpit, downloads the company’s e-mail directory, and assigns the user a valid license. If required by the app settings, the user must set a personal password for the app container. If a password is not required, the user can skip this step and set a password later in the app settings.

  9. When you log in to the Management Cockpit the next time, (only) the registered users will be automatically imported from the EMM process. You can now start to create groups and channels and assign users.

2.15. Representatives

The Management Cockpit of a company can be managed by multiple administrators. The “owner” of the Cockpit – the first administrator created – can go to Settings > Administrator and create additional representatives. To do so, click Edit representative and select Create a new representative in the bottom right. Enter the representative’s last name, first name, mobile number, and e-mail address.

Note

  • The e-mail address must be able to receive e-mails with attachments (certificate for Cockpit access as a P12 file)

  • The mobile number must be able to receive SMS (certificate password).

Upon certificate installation, the representative can access the Cockpit as well and create, edit and delete users, groups, and channels. However, they cannot create additional representatives.

_images/cockpit_30.en.png

There’s no limit to the number of representatives. For practical reasons, however, we suggest you create not more than 3. In the representative overview, you can see the date and time of activation as well as last login.

The “owner” can deactivate or delete an active representative from within the respective detail view. When a representative is deactivated, access to the Cockpit is blocked. The user data, however, are kept in the Cockpit, so they can be reactivated as a representative at any time.

Upon deletion, the representative is deleted from the system and marked accordingly. To readd the user as a representative later, you have to reenter their data and the entire process must be completed again.