Activation and configuration¶
Chapter for the Odoo partner
This page is written for whoever administers the organization's Odoo instance. If that is not you, it is enough to know that activation is done by your Odoo partner with AppToMe's support: go back to What gets synchronised.
The connector is an Odoo module installed in the customer's instance. It is not a service hosted by AppToMe: it runs inside Odoo, under the control of whoever administers Odoo.
Prerequisites¶
- Odoo 18, Community or Enterprise, vanilla is fine.
- The standard modules the connector needs are installed as dependencies: contacts, human resources and attendance, timesheets, fleet, projects and OAuth authentication.
- Odoo must be reachable from the internet over HTTPS, with the reverse proxy configured correctly to forward the protocol and host headers — otherwise logging in with an AppToMe account does not work.
- The organization must be enabled for synchronisation on the AppToMe side.
The connector requires no specific modules for Italian localisation: those remain the customer's choice, to be installed separately if needed for tax compliance.
The five stages¶
1. Installing the module¶
The module is obtained from AppToMe's public repository and placed among the instance's addons. After restarting the server, from the Apps section you update the list, search for Apptome Connector and install it.
2. Asking for the credentials¶
The connection credentials are specific to the organization and are issued by AppToMe support. They comprise the addresses of the AppToMe services and the keys for login and for synchronisation.
Treat them as passwords
The credentials apply to the whole organization. They must not be put in tickets, chats or repositories, and in Odoo access to the system parameters should be limited to admins only. If you suspect they have been exposed, ask support for rotation straight away.
3. Configuring the connector¶
From Settings → General settings → Apptome you fill in the addresses and keys received, enable login with an AppToMe account and enable data synchronisation. On saving, the connector updates the login provider and the scheduled actions by itself.
If one Odoo instance serves several organizations, the synchronisation configuration is per company: every Odoo company has its own addresses and keys, which must differ from each other.
4. First alignment¶
This is the stage requiring attention, and the only one where someone from the organization is needed: only those who know the people can say whether two similar records are the same person.
Registries — from Settings → Apptome → Bootstrap from Apptome the module downloads the volunteers and compares them with the contacts already present in Odoo, using tax code, email and full name. For every row you choose:
| Choice | When to use it |
|---|---|
| Link to existing partner | the person is already in Odoo — the most frequent case |
| Create new partner | the person does not exist in Odoo yet |
| Skip | the row has to be reviewed before deciding |
Then you confirm. The skipped rows can be picked up in a second pass.
Everything else — from Apptome → Synchronise from Apptome → Full synchronisation you start loading abilities, calendars, vehicles, patents, courses, shifts, activities, checklists and hours. The loading respects the dependency order between the data, so it must be launched after the alignment of the registries: the hours need the people already linked.
On an organization with years of history the full load can take a long time: put it at a moment of low use.
5. Verifying¶
Quick checks telling you whether the activation succeeded:
- Contacts → Apptome volunteers lists the volunteers, with no duplicates;
- Odoo's login page shows the Log in with Apptome button (visible when logged out);
- Apptome → Training → Patents obtained shows the patents with their expiry dates;
- the scheduled action Apptome — Synchronise contacts (hourly) is active;
- certifying the hours of a shift in AppToMe, the corresponding attendance appears in Odoo within a few minutes.
The last check is the one that counts: if it works, the whole chain works.
Enabling login with an AppToMe account¶
The connector does not create Odoo users by itself, and that is a deliberate choice: a management system must not fill up with users because someone pressed a button.
The volunteers synchronised become contacts, not users who can log into Odoo. Whoever has to access the management system must be enabled one by one, by linking their Odoo user to their AppToMe account. As a rule that concerns few people: staff and administration.
An account that is not linked and tries to log in receives an expired-invitation message. It is not a fault: it is the correct refusal of an unforeseen access.
Updates¶
The connector and AppToMe evolve together. After an important update of one it is worth updating the other too: some synchronisation errors come from versions out of step between the two sides.
Routine maintenance¶
- Keep active the scheduled action that sends the registries back to AppToMe.
- Check the diagnostics from time to time: that is where you see whether something has stopped.
- After a prolonged Odoo outage, relaunch the full synchronisation (or that of the single entry concerned) to recover what went past in the meantime.