Set up the Altinn integration in Simployer Classic

Modified on Fri, 2 Oct at 2:09 PM

This article is not available in Swedish, view it in English

Activate Altinn version 3 to receive digital sick notes and submit follow-up plans.

Before you set up the Altinn integration in Simployer Classic

Make sure that:

The organization number and company number are registered in the organizational structure in Simployer Classic
The Managing Director has an active user account in Simployer. No specific roles are required
Users with the Application programming interface (API) role can also complete the setup for follow-up plans
The Altinn integration is set up separately for each legal entity if the organization has more than one

Sign in to the Simployer portal as the Managing Director
Go to https://altinn.simployer.com/companies
Follow the on-screen instructions to connect the organization to the new functionality for digital sick notes and follow-up plans
Select Approve in the Altinn window when you have completed the setup
Go to step 15 in the activation guide and select Test. Confirm that the follow-up plan configuration turns green

Note

You must complete both configurations: digital sick notes and follow-up plans.

Problem	Solution
The page displays “No companies found”	The organization number or company number is missing from the organizational structure. Contact Support through mysupport.simployer.com
You completed the setup in Altinn, but Simployer displays “Not configured”	The page has not been updated yet. If you selected Approve in Altinn, the setup is complete
The follow-up plan still displays “Not configured”	Go to step 15 and select Test. The status should turn green
You are using the beta version of Altinn, which has a different interface	Select Switch to old Altinn in the lower-left corner, and continue the process there
You receive an error message during setup	An error that affected the solution at launch has been fixed. Contact Support if the error persists

Name	Host	Duration	Description
_fw_crm_v	simployer.freshdesk.com	1 year	Freshchat/Freshworks cookie (Used to track Visitor/User identity and chat sessions performed by the User).
_x_w	simployer.freshdesk.com	Session	Contains the shard ID at which the account runs on.
_x_m	simployer.freshdesk.com	Session	Contains the state of the shard.
_helpkit_session	simployer.freshdesk.com	Session	Your secret key for verifying cookie session data integrity. If you change this key, all old sessions will become invalid!
helpdesk_node_session	simployer.freshdesk.com	Session	An encrypted hash that stores the secret key and id of the login attempt.
user_credentials	simployer.freshdesk.com	2 months	Used for user authentication.
wf_order	simployer.freshdesk.com	Session	Used to check in which the order the tickets are filtered for custom ticket filters eg: due_by, agent_responded_at, requester_responded_at, etc.
wf_order_type	simployer.freshdesk.com	Session	Used to check if the order is ascending or descending for custom ticket filters.
wf_filter	simployer.freshdesk.com	Session	Denotes which filter is applied for the tickets list.