Employee registration and attachment

Access to the Mobilic API services requires an account.

Creating an account via Mobilic interface

Registering on Mobilic website can be perfom from the following links:

• https://mobilic.beta.gouv.fr/signup/admin to create accounts corresponding to real users on the production environment

• https://sandbox.mobilic.beta.gouv.fr/signup/admin to create accounts on the sandbox environment

There are 3 steps to complete registration:

1. the manager creates his individual account and registers his company (from the links above).

2. the manager invites his employees by entering their email addresses in his company console.

3. the employee creates his individual account by following the instructions contained in the invitation email.

Creating an account via API

Please refer to the dedicated page:

pageAttaching employees to the company

Attaching employees

User accounts are linked to the person who holds the account, regardless of their company or profession (mobile worker or manager). Thus, a person who changes company still keeps one and the same account. The belonging (variable over time) of a person to a company is represented by an attachment. An account can have several attachments over time, as the person moves from one company to another. An account can also be attached to several companies simultaneously, to accommodate the frequent case of sister companies that may occasionally pool their workers.

By default the working time recorded by a mobile worker account will be associated with the company to which it is attached at the time of the activity. If there are several simultaneous attachments, the main (unique) attachment will prevail in the absence of further details.

For security reasons the attachment of a person to a company must be approved by both the company and the employee. This is done in the following order:

1. The company (i.e. a Mobilic user who has administrative rights for this company) makes a request to attach the employee by API, specifying a start date of the attachment (and optionally an end date).

2. The attachment request is registered but remains inactive until it is approved by the employee.

3. The employee account approves the attachment request by API. The old attachments are eventually terminated if needed.