Visma Personec P (Publitech Lön & HR)
Bring your people data from Visma Personec P into MuchSkills. Your Visma Personec P 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 Personec P system owner and Visma PubliTech, 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 Visma Personec P 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 Visma Personec P.
Before you start
- A Visma Personec P administrator on your side, or your Visma Personec P implementation partner.
- A list of who should be in MuchSkills: everyone, or a selection by country, company, department or worker type.
- Your field names. Visma Personec P installations name custom fields differently, so have your field list to hand for the technical session.
Steps
In Visma Personec P
Personec P, now also called Publitech Lön & HR, has no self-service screen for API access. Integrations are arranged through Visma PubliTech, so the first step is with the people who manage your Personec P agreement. Visma Personec P documentation
- Contact your Personec P system owner. This is the person or team who manages Personec P and your agreement with Visma PubliTech. They order integrations from Visma.
- Ask Visma PubliTech for read-only access to employee data. Ask for read access through Personec P's API, with only the fields listed below. If your delivery has no API, ask which scheduled export it offers instead and tell us before the technical session. Visma confirms which option your delivery supports, whether a licence or consulting order is needed, and how the credentials are issued. Tell Visma that MuchSkills connects from two fixed IP addresses,
13.51.77.53and16.170.107.61, in case access is limited by address. - Limit the scope at the source. Ask for the access to cover only the companies, organisation units and employment types that should be in MuchSkills. Leave out personal identity numbers, salaries, bank details and absence causes. For absence, ask for dates and extent only.
- Confirm where work email addresses are held. Email is the one field MuchSkills needs for every person, together with the name. If Personec P does not hold work email addresses, tell us before the technical session.
- Note the connection details. The address of the API, or the export details, the credentials Visma issues and the field names.
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 Visma Personec P 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
- Visma Personec P stays the source of truth. People data is entered once, in Visma Personec P, 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 Visma Personec P 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 Visma Personec P 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 Visma Personec P 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 Visma Personec P, 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 Visma Personec P | Check that every manager is in scope and that reporting lines are filled in in Visma Personec P |
| A person appears twice | Their Visma Personec P email differs from the address they signed up with | Align the email in Visma Personec P, then contact support |
| The connection is refused | Visma Personec P 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 Visma Personec P and send us the new details securely |
Frequently asked questions
Visma Personec P is not listed in MuchSkills, or shows as Contact us. Can we still connect it?
Yes. Visma Personec P 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 Visma Personec P 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 Visma Personec P, 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.