Namely
Bring your people data from Namely into MuchSkills. Your Namely 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 Namely 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 Namely 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 Namely.
Before you start
- A Namely administrator on your side, or your Namely implementation partner.
- A list of who should be in MuchSkills: everyone, or a selection by country, company, department or worker type.
- Your field names. Namely installations name custom fields differently, so have your field list to hand for the technical session.
Steps
In Namely
Your Namely administrator will recognise these settings. Access roles and field group bundles differ between Namely sites, so the exact bundles depend on how yours is set up. Namely documentation
- Create a dedicated user for the integration. Add a Namely user that will own the access token, for example MuchSkills API. It must sign in with a password, not single sign-on: tokens created by an SSO-enabled user are rejected.
- Give it a read-only access role. Go to Company › Settings and, under Employee Data, open Roles & Permissions. Clone the Employee role and Edit the copy. In its field group bundles, give User read only, for the bundles that hold the fields you share, scoped to the people who should be in MuchSkills. The role also needs permission to use the API. Assign the role to the integration user.
- Create a personal access token. Signed in as the integration user, click the profile image in the navigation menu, select API, open Personal Access Tokens, enter a name such as MuchSkills and click Create. Copy the token straight away: Namely shows it only once. If API is missing from the menu, the role does not yet have API permission.
- Note your connection details. Your Namely subdomain (yourcompany in
https://yourcompany.namely.com), the personal access token, and the name of the integration user.
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 Namely 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
- Namely stays the source of truth. People data is entered once, in Namely, 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 Namely 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 Namely 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 Namely or your network limits access by IP address, add both to the allow list.
Absence. Namely's API does not offer dated absence records, so absence does not come from Namely. Availability can still be planned in Team Builder.
Common errors
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| Some people are missing | They are outside what the integration user can see in Namely, 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 Namely | Check that every manager is in scope and that reporting lines are filled in in Namely |
| A person appears twice | Their Namely email differs from the address they signed up with | Align the email in Namely, then contact support |
| The connection is refused | Namely 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 Namely and send us the new details securely |
Frequently asked questions
Namely is not listed in MuchSkills, or shows as Contact us. Can we still connect it?
Yes. Namely 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 Namely 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 Namely, 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.