Simployer
Bring your people data from Simployer into MuchSkills. Your Simployer administrator gives MuchSkills read-only access, and we map the fields and run the sync. The set-up is part of your MuchSkills implementation.
- Who
- Your Simployer administrator, with our CTO
- How it connects
- Custom set-up, part of your implementation
- Sync
- Every 5 hours, or on demand with Sync Now
- Access
- Read-only
How to
How it works
MuchSkills reads from Simployer on a schedule. New starters, leavers, manager changes and department changes arrive at the next sync, with no manual work on either side. Nothing is written back to Simployer.
Before you start
- A Simployer administrator on your side, or your Simployer implementation partner.
- A list of who should be in MuchSkills: everyone, or a selection by country, company, department or worker type.
- Your field names. Simployer installations name custom fields differently, so have your field list to hand for the technical session.
Steps
In Simployer
Simployer has two HR systems, HRM One (formerly AlexisHR) and HRM Classic, and the steps differ. Follow the steps for the one you use; if you are not sure, your Simployer contact can tell you. Simployer documentation
- HRM One: create an access token. Sign in as a user with the Owner permission and go to Settings > Access tokens. Choose the Public API and generate the token. Copy it straight away: it is shown only once. The token stops working if that user loses the Owner permission or leaves, so create it from an account that will stay.
- HRM Classic: get access to the Admin Center. You need to be a system administrator in your Simployer tenant. If the Admin Center is not in the Global Menu of your Simployer Portal, create a support ticket with Simployer Customer Care and ask for access. Simployer says the Admin Center is free of charge.
- HRM Classic: create an API client. In the Admin Center at
https://admincenter.simployer.com, create a new API client named MuchSkills and select the HR Connect API. Then create a secret for the client and copy it: you can copy it only once. - Tell us who is in scope. Neither an HRM One token nor an HRM Classic client can be limited to read-only access or to some of your people, so the limit is applied when data arrives in MuchSkills: records outside your scope are ignored and not stored. Tell us which people should be in MuchSkills, and we agree the filter in the technical session.
- Note your connection details. For HRM One, the access token. For HRM Classic, the client ID and the secret. We agree a secure channel with you for sending them.
With MuchSkills
- Send us the connection details. The credentials and connection details from the steps above, your field list and your scope, through a secure channel we agree.
- Join the technical session. Your Simployer administrator and our CTO map the fields and test the connection together.
- Check a first sync. We sync a handful of people or one department. You check their names, managers, departments and any tags in MuchSkills.
- Widen the scope. We switch the sync on for everyone in scope. From then on it runs every 5 hours.
Check it worked
- Team/Org › Members lists the people in scope.
- The people in scope have an invitation to create their MuchSkills profile.
- Managers see their direct reports in My Circle.
Benefits
What you get
- Simployer stays the source of truth. People data is entered once, in Simployer, and MuchSkills follows.
- A skills layer on your HR system. Skills, certifications and project history sit next to the people records you already trust.
- Clean data for planning. Reporting lines, departments and tags arrive ready for filtering, gap analysis and Team Builder.
Important to know
Important to know
What syncs. Only name and email are required. Sync as many of the other fields as you can, because each one makes MuchSkills more useful.
| Field | Needed | Used for |
|---|---|---|
| First and last name | Required | Profiles, search, every view |
| Required | Matching and sign-in. Must be the address people sign in with | |
| Job title | Recommended | Profiles, roles, Discover |
| Manager | Recommended | Reporting lines, My Circle, reports. MuchSkills maps it from Simployer automatically |
| Department | Recommended | Departments and filters |
| Employee status | Recommended | Deactivating leavers |
| Location or country | Recommended | Filters and scoping |
| Profile photo | Recommended | Profiles and the org chart |
| Worker type | Recommended | Filtering, for example employee or contractor |
| Absence | Recommended | Availability in Team Builder and My Circle. Dates and percentages only |
| Other fields | Optional | Any field can become a filterable tag, for example legal entity, team or cost centre. Agree them with us first |
Data MuchSkills does not accept. These are blocked when data arrives and never stored, even if the source includes them: age or date of birth, salary or other compensation data, performance ratings, and political, religious or health data.
Who is included. Limiting what the integration user can see in Simployer is the preferred way, so nothing outside your scope leaves your system. The fallback is a country filter in MuchSkills; records outside it are ignored and not stored. Your security or compliance team decides which fits your rules.
Leavers are deactivated, not deleted. Project history and certificates stay on record.
Our IP addresses. MuchSkills always connects from the same two addresses: 13.51.77.53 and 16.170.107.61. If Simployer or your network limits access by IP address, add both to the allow list.
Common errors
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| Some people are missing | They are outside what the integration user can see in Simployer, or outside the scope filter | Check the integration user's permissions and the scope |
| Managers are missing or wrong | The manager is outside the scope, or has no manager set in Simployer | Check that every manager is in scope and that reporting lines are filled in in Simployer |
| A person appears twice | Their Simployer email differs from the address they signed up with | Align the email in Simployer, then contact support |
| The connection is refused | Simployer or your network limits access by IP address | Add 13.51.77.53 and 16.170.107.61 to the allow list |
| The sync stopped | The credentials expired, or the integration user was disabled or lost permissions | Renew the access in Simployer and send us the new details securely |
Frequently asked questions
Simployer is not listed in MuchSkills, or shows as Contact us. Can we still connect it?
Yes. Simployer is connected as a custom set-up rather than from a form, because every installation is configured differently. Email support@muchskills.com or use the chat, and we book the technical session.
Do we need middleware or an integration platform?
No. MuchSkills reads directly from Simployer over HTTPS. Your team only creates the read-only access described on this page.
Can we leave out some countries, companies or groups?
Yes. The preferred way is to limit what the integration user can see in Simployer, so only people in scope ever leave your system. If that is not possible, MuchSkills can filter by country as records arrive and ignore the rest without storing them.
Can we test with a few people first?
Yes. The first sync can be limited to a handful of people or one department. You check the result, then we widen the scope. There are no separate test tenants.
How often does it sync?
Every 5 hours. An Owner or Admin can also run a sync at any time with Sync Now.
What happens to people who leave?
They are deactivated at the next sync, never deleted. Their project history and certificates stay on record, which matters for compliance.
Do you import absence reasons?
No. If you sync absence, MuchSkills takes only the dates and the percentage of time away. Reasons such as sick leave are never imported.
How do we send the credentials safely?
Through a secure channel we agree with you in advance, such as a password manager share. Never by plain email.