Feat/signing (#2034)

* Basic structure of the three known scenarios. * Runtime delegated singing (brukerstyrt) * Role based signing. * Lots of edits of all the different signing guides. * Fix wrong insert url. * Fix intro insert for sign and submit. * Add missing recommendation to use altinn studio process editor. * Fix wrong insert url in runetime-delegated-singing. * Tiny fix. * Tiny fix. * Tiny adjustments. * prevent instance deletion * update concept to explain persistence * text resources * use full paths * Update content/altinn-studio/guides/development/signing/_index.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/_index.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/role-based-signing/_index.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/role-based-signing/backend-manual/add-process-task.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/role-based-signing/backend-manual/add-process-task.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/concepts/signing/_index.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/concepts/signing/_index.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/role-based-signing/backend-manual/add-process-task.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/role-based-signing/backend-manual/add-process-task.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/role-based-signing/backend-manual/configure-layouts.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/role-based-signing/backend-manual/configure-layouts.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/role-based-signing/backend-manual/configure-layouts.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/role-based-signing/backend-manual/configure-layouts.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/role-based-signing/backend-manual/configure-layouts.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/role-based-signing/backend-manual/configure-layouts.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/role-based-signing/backend-manual/configure-layouts.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/role-based-signing/studio/configure-layouts.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/_index.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/_index.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/_index.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/backend-manual/add-process-task.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/backend-manual/add-process-task.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/backend-manual/add-process-task.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/backend-manual/add-process-task.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/backend-manual/add-process-task.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * fix links * fix another bad link * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/backend-manual/configure-layouts.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/backend-manual/configure-layouts.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/backend-manual/setup-text-resources.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/backend-manual/setup-text-resources.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/backend-manual/signee-provider.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/backend-manual/signee-provider.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/backend-manual/signee-provider.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/intro.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/runtime-delegated-signing/intro.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/sign-and-submit/_index.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/sign-and-submit/_index.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/sign-and-submit/_index.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/sign-and-submit/_index.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/sign-and-submit/_index.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/sign-and-submit/_index.nb.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> * Update content/altinn-studio/guides/development/signing/sign-and-submit/_index.en.md Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com> --------- Co-authored-by: HauklandJ <hauklandjohannes@gmail.com> Co-authored-by: Johannes Haukland <42615991+HauklandJ@users.noreply.github.com> Co-authored-by: Camilla Marie Dalan <camillamdalan@gmail.com>
Altinn · Feb 28, 2025 · f72dbd2 · f72dbd2
1 parent 9f8d224
commit f72dbd2
Show file tree

Hide file tree

Showing 42 changed files with 2,032 additions and 12 deletions.
diff --git a/content/altinn-studio/concepts/signing/_index.en.md b/content/altinn-studio/concepts/signing/_index.en.md
@@ -1,44 +1,52 @@
 ---
-title: Signing  
-description: What is signing in an Altinn 3 service?  
-weight: 10  
-
+title: Signing
+description: What is signing in an Altinn 3 service?
+weight: 10
 ---
 
 ## Authenticated Electronic Signature
+
 An electronic signature is linked to traceability. Traceability means being able to demonstrate that an action was performed at a specific time and tied to a specific identity. The requirements for traceability describe the extent to which it should be possible to verify afterward that an actor was responsible for a piece of information or performed an action at a specific time.
 
 An authenticated electronic signature allows service owners to ensure traceability by verifying that an identified person performed a signing action at a specific time, e.g., when the end user confirms the accuracy of information by signing. The signing solution in Altinn 3 is an authenticated signature with the option of security level 3 or 4. The authentication level is configurable for each service. It is also possible to choose lower authentication levels than 3 and 4. If advanced signatures are desired, third-party products such as [eSignering | Samarbeidsportalen (digdir.no)](https://samarbeid.digdir.no/esignering/esignering/22) must be used.
 
 Service owners must make their own assessment of which electronic signature they want and need for their services, based on the requirements for signature and traceability in the regulations for which each service owner is responsible.
 
 ## Functionality
+
 ### What is being signed?
+
 The service owner controls the selection of data elements that are to be signed and selects which authentication level (identification level) the end user must log in with before signing (level 1-4). One or more signing steps in sequence are possible.
 
 ### Signature
+
 The signing action is logged, and a signature object is created. The signature object represents a signature performed by a person and contains information about which data elements are signed and which are not. The signature object contains a so-called hash code of the data associated with the data elements that are signed. Hashing is a one-way mathematical algorithm that calculates a unique code based on the data. If even one character in the data is changed, the hash code will no longer match. This ensures that the data no longer aligns with what was signed, making any changes to the data detectable.
 
 ### Logging
+
 An event log is kept, recording actions performed in the application. Signing is a type of action that is explicitly logged. The ID of the person who performed the signing action is logged, along with the security level of the login, the time of the action, which step in the process the action was performed on, and that it was a signing action. Log data related to electronic signatures in Altinn 3 is stored separately from services in a central event log database.
 
 ## Processing of personal data
+
 To ensure traceability, personal data is processed for logging purposes. The ID of the person who performed the signing action is logged, which can be linked to a national ID number, the security level of the login, the step in the process at which the action was performed, the time of the action, and that it was a signing action. Digdir is the data controller for the processing of this personal data for this purpose.
 
 The service owner is the data controller for the processing of personal data in their services and forms, including the relevant signature object and associated data. This includes the ID of the person who performed the signing action and the national ID number. According to the collaboration agreement, Digdir is the data processor for the service owner.
 
 ## Storage time
+
 After the process in Altinn 3 is completed, the service owner can download all data, including the signature object. The end user receives a receipt (PDF).
 
+You may configure the persistence lifetime of the instance and its data by configuring [Persistence](../../reference/data/persistence/). If not configured, the following applies:
+
 The service owner acknowledges that the signature object and associated data have been downloaded. The end user can choose to keep or delete their receipt for the signing from their inbox. If the end user chooses to delete their receipt after the service owner has downloaded the signature object, this means that Digdir deletes the signature object from our systems. Therefore, if you wish to archive the signature, the signature object and associated data must be stored in the service owner's systems.
 
 Digdir logs that the signing action was performed. This means that even if the signature object is deleted, Digdir still retains the log showing that a signing action was completed. Regular application logs (typically used for troubleshooting) are stored by Digdir for 90 days, while event logs are stored for 13 months.
 
 ## Verification of signature
+
 The service owner stores the signature object in their archival system. The signature object contains a hash code of the data associated with the data element. If the signature object is later altered, this can be verified by the fact that the hash code in the signature object no longer matches. This contributes to the traceability of the signature object. This assumes that the signature, i.e., the hash code, also exists on the end user's receipt so that both parties have their own copy.
 
 [Here you can read the technical description of how signature verification is done.](https://docs.altinn.studio/nb/altinn-studio/reference/process/tasks/signing/#verifisering-av-sha256-hash)
 
 ---
 
-Let me know if you need further adjustments!
diff --git a/content/altinn-studio/concepts/signing/_index.nb.md b/content/altinn-studio/concepts/signing/_index.nb.md
@@ -3,36 +3,47 @@ title: Signering
 description: Hva er signering i en Altinn 3 tjeneste?
 weight: 10
 ---
+
 ## Autentisert elektronisk signatur
-Elektronisk signatur er knyttet til sporbarhet. Sporbarhet innebærer å kunne sannsynliggjøre at en handling ble gjennomført på et bestemt tidspunkt og knyttet til en bestemt identitet. Krav til sporbarhet beskriver i hvilken grad det i ettertid skal være mulig å sannsynliggjøre at en aktør står bak et informasjonselement eller har utført en handling på et bestemt tidspunkt. 
+
+Elektronisk signatur er knyttet til sporbarhet. Sporbarhet innebærer å kunne sannsynliggjøre at en handling ble gjennomført på et bestemt tidspunkt og knyttet til en bestemt identitet. Krav til sporbarhet beskriver i hvilken grad det i ettertid skal være mulig å sannsynliggjøre at en aktør står bak et informasjonselement eller har utført en handling på et bestemt tidspunkt.
 
 Autentisert elektronisk signatur gjør det mulig for tjenesteeiere å sikre sporbarhet for å sannsynliggjøre at en identifisert person foretok en signeringshandling på et bestemt tidspunkt, f.eks. ved at sluttbruker bekrefter at opplysninger er riktig ved å signere. Signeringsløsningen i Altinn 3 er en autentisert signatur med mulighet for sikkerhetsnivå 3 eller 4. Autentiseringsnivå er konfigurerbart i den enkelte tjeneste. Man kan også velge lavere autentiseringsnivå enn 3 og 4. Ønsker man avansert signatur må man ta i bruk tredjeparts produkter som [eSignering | Samarbeidsportalen (digdir.no)](https://samarbeid.digdir.no/esignering/esignering/22).
 
 Tjenesteeierne må foreta en egen vurdering av hvilken elektronisk signatur de ønsker og har behov for i sine tjenester. Dette blant annet ut ifra hvilke krav som stilles til signatur og sporbarhet i det regelverket som den enkelte tjenesteeier har ansvar for.
 
 ## Funksjonalitet
+
 ### Hva signeres det på?
-Tjenesteeier styrer utvalg av dataelementer  som skal signeres og tjenesteeier velger hvilket autentiseringsnivå (identifikasjonsnivå) som sluttbruker må logge inn med før signering (nivå 1-4). Det er mulig med ett eller flere signeringssteg i sekvens.
+
+Tjenesteeier styrer utvalg av dataelementer som skal signeres og tjenesteeier velger hvilket autentiseringsnivå (identifikasjonsnivå) som sluttbruker må logge inn med før signering (nivå 1-4). Det er mulig med ett eller flere signeringssteg i sekvens.
 
 ### Signatur
-Signaturhandling logges og det opprettes et signaturobjekt. Signaturobjektet representerer en signatur utført av en person, inneholder informasjon om hvilke dataelementer som er signert og eventuelt ikke signert. Signaturobjektet inneholder en såkalt hash kode av dataene som tilhører dataelementene som det signeres på. Hashing er en enveis matematisk algoritme som beregner en unik kode med utgangspunkt i dataene. Dersom bare ett tegn i dataene endres vil ikke lenger hash koden bli lik. Dataene stemmer dermed ikke lenger med det som ble signert, og det blir dermed synlig hvis data endres. 
+
+Signaturhandling logges og det opprettes et signaturobjekt. Signaturobjektet representerer en signatur utført av en person, inneholder informasjon om hvilke dataelementer som er signert og eventuelt ikke signert. Signaturobjektet inneholder en såkalt hash kode av dataene som tilhører dataelementene som det signeres på. Hashing er en enveis matematisk algoritme som beregner en unik kode med utgangspunkt i dataene. Dersom bare ett tegn i dataene endres vil ikke lenger hash koden bli lik. Dataene stemmer dermed ikke lenger med det som ble signert, og det blir dermed synlig hvis data endres.
 
 ### Logging
-Det føres en hendelseslogg som inneholder hendelser utført i applikasjonen. Signering er en type handling som logges eksplisitt. Det logges id til den som utførte signeringshandlingen, sikkerhetsnivå for innloggingen, tidspunktet for handlingen, hvilket steg i prosessen handlingen ble utført på og at det var en signeringshandling. Loggdata knyttet til elektronisk signatur i Altinn 3 lagres adskilt fra tjenestene i en sentral hendelseslogg database. 
+
+Det føres en hendelseslogg som inneholder hendelser utført i applikasjonen. Signering er en type handling som logges eksplisitt. Det logges id til den som utførte signeringshandlingen, sikkerhetsnivå for innloggingen, tidspunktet for handlingen, hvilket steg i prosessen handlingen ble utført på og at det var en signeringshandling. Loggdata knyttet til elektronisk signatur i Altinn 3 lagres adskilt fra tjenestene i en sentral hendelseslogg database.
 
 ## Behandling av personopplysninger
+
 For å sikre sporbarhet behandles det personopplysninger til loggformål. Det logges id til den som utførte signeringshandlingen som kan kobles til fødselsnummer, sikkerhetsnivå for innloggingen, hvilket steg i prosessen handlingen ble utført på, tidspunktet for handlingen og at det er en signeringshandling. Behandling av disse personopplysningene til dette formål er Digdir behandlingsansvarlig for.
 
 Tjenesteeier er behandlingsansvarlig for behandling av personopplysninger i sine tjenester og skjema, og her for det aktuelle signeringsobjekt og tilhørende data. Dette inkluderer id til den som utførte signeringshandlingen og fødselsnummer. I henhold til samarbeidsavtalen er da Digdir databehandler for tjenesteeier.
 
 ## Lagringstid
-Etter at prosessen i Altinn 3 er gjennomført, kan tjenesteeier laste ned alle data inkludert signeringsobjektet. Sluttbruker mottar en kvittering (PDF). 
+
+Etter at prosessen i Altinn 3 er gjennomført, kan tjenesteeier laste ned alle data inkludert signeringsobjektet. Sluttbruker mottar en kvittering (PDF).
+
+Du kan konfigurere levetiden for persistens av instansen og dataene ved å konfigurere [Persistens](../../reference/data/persistence/). Hvis dette ikke er konfigurert, gjelder følgende:
 
 Tjenesteeier kvitterer ut at signeringsobjekt og at tilhørende data er lastet ned. Sluttbruker kan velge å beholde eller å slette sin kvittering på signeringen i sin innboks. Dersom sluttbruker velger å slette sin kvittering etter at tjenesteeier har lastet ned signeringsobjektet, så innebærer det at Digdir sletter signeringsobjektet i våre systemer. Signeringsobjektet og tilhørende data må dermed lagres i tjenesteeiers systemer om man ønsker å arkivere signaturen.
 
-Digdir logger at signeringshandlingen er utført. Det betyr at selv om signeringsobjektet er slettet, så lagrer Digdir fortsatt loggen som viser at det er utført en signaturhandling. Vanlige applikasjonslogger (benyttes som regel til feilsøking) lagrer Digdir i 90 dager, mens hendelseslogger lagrer vi i 13 måneder. 
+Digdir logger at signeringshandlingen er utført. Det betyr at selv om signeringsobjektet er slettet, så lagrer Digdir fortsatt loggen som viser at det er utført en signaturhandling. Vanlige applikasjonslogger (benyttes som regel til feilsøking) lagrer Digdir i 90 dager, mens hendelseslogger lagrer vi i 13 måneder.
 
 ## Verifisering av signatur
+
 Tjenesteeier lagrer signaturobjektet i sitt arkivsystem. Signaturobjektet inneholder en hash kode av dataene som tilhører dataelementet. Dersom signaturobjektet senere endres vil dette kunne verifiseres ved at hash koden i signaturobjektet ikke lenger stemmer, dette bidrar til sporbarhet for signaturobjektet. Dette forutsetter at signaturen, dvs. hash koden, også finnes på sluttbruker sin kvittering slik at begge parter har hver sin kopi.
 
-[Her kan du kan lese den teknisk beskrivelse for hvordan verifisering av signaturen gjøres.](https://docs.altinn.studio/nb/altinn-studio/reference/process/tasks/signing/#verifisering-av-sha256-hash) 
+[Her kan du kan lese en teknisk beskrivelse for hvordan verifisering av signaturen gjøres.](https://docs.altinn.studio/nb/altinn-studio/reference/process/tasks/signing/#verifisering-av-sha256-hash)
diff --git a/content/altinn-studio/guides/development/signing/_index.en.md b/content/altinn-studio/guides/development/signing/_index.en.md
@@ -0,0 +1,29 @@
+---
+title: How to configure signing in your Altinn app
+linktitle: Signing
+description: Below you will find guides for common configurations of signing.
+tags: [signing]
+weight: 50
+aliases:
+  - /altinn-studio/guides/signing/
+---
+
+The different scenarios below can to some extent be combined with each other, but many services will only need one of them.
+
+## Role/access package based signing
+
+{{% insert "content/altinn-studio/guides/development/signing/role-based-signing/intro.en.md" %}}
+
+[How to configure](/altinn-studio/guides/development/signing/role-based-signing)
+
+## Runetime delegated singing
+
+{{% insert "content/altinn-studio/guides/development/signing/runtime-delegated-signing/intro.en.md" %}}
+
+[How to configure](/altinn-studio/guides/development/signing/runtime-delegated-signing)
+
+## Sign and submit
+
+{{% insert "content/altinn-studio/guides/development/signing/sign-and-submit/intro.en.md" %}}
+
+[How to configure](/altinn-studio/guides/development/signing/sign-and-submit)
diff --git a/content/altinn-studio/guides/development/signing/_index.nb.md b/content/altinn-studio/guides/development/signing/_index.nb.md
@@ -0,0 +1,26 @@
+---
+title: Hvordan konfigurere signering i din Altinn-app 
+linktitle: Signering
+description: Nedenfor finner du veiledninger for vanlige oppsett av signering.
+tags: [signering]
+weight: 50
+aliases:
+- /nb/altinn-studio/guides/signing/
+---
+
+De ulike scenarioene nedenfor kan i noen grad kombineres med hverandre, men ofte trenger en tjeneste bare en av variantene.
+
+## Rolle-/tilgangspakkebasert
+{{% insert "content/altinn-studio/guides/development/signing/role-based-signing/intro.nb.md" %}}
+
+[Slik gjør du det](/nb/altinn-studio/guides/development/signing/role-based-signing)
+
+## Brukerstyrt
+{{% insert "content/altinn-studio/guides/development/signing/runtime-delegated-signing/intro.nb.md" %}}
+
+[Slik gjør du det](/nb/altinn-studio/guides/development/signing/runtime-delegated-signing)
+
+## Signer og send inn
+{{% insert "content/altinn-studio/guides/development/signing/sign-and-submit/intro.nb.md" %}}
+
+[Slik gjør du det](/nb/altinn-studio/guides/development/signing/sign-and-submit)
diff --git a/content/altinn-studio/guides/development/signing/role-based-signing/_index.en.md b/content/altinn-studio/guides/development/signing/role-based-signing/_index.en.md
@@ -0,0 +1,47 @@
+---
+title: Role and access package based signing
+linktitle: Role and access package
+description: Follow these steps to implement role based signing in your service.
+tags: [role based, signing]
+weight: 50
+aliases:
+  - /altinn-studio/guides/signing/role-based-signing
+---
+
+## What does role/access package-based signing mean?
+
+{{% insert "content/altinn-studio/guides/development/signing/role-based-signing/intro.en.md" %}}
+
+## Prerequisites
+
+If the service should send a signature receipt to the inbox of the signee, the Altinn message service (Correspondence) must be enabled.
+
+See [how](/correspondence/getting-started/) to get started.
+
+## 1. Add a signing task to the app process, with related configuration
+
+{{<content-version-selector classes="border-box">}}
+
+{{<content-version-container version-label="Manual setup">}}
+{{% insert "content/altinn-studio/guides/development/signing/role-based-signing/backend-manual/add-process-task.en.md" %}}
+{{</content-version-container>}}
+
+{{<content-version-container version-label="Altinn Studio Designer">}}
+{{% insert "content/altinn-studio/guides/development/signing/role-based-signing/studio/add-process-task.en.md" %}}
+{{</content-version-container>}}
+
+{{</content-version-selector>}}
+
+## 2. Add layout-set for signing
+
+{{<content-version-selector classes="border-box">}}
+
+{{<content-version-container version-label="Manual setup">}}
+{{% insert "content/altinn-studio/guides/development/signing/role-based-signing/backend-manual/configure-layouts.nb.md" %}}
+{{</content-version-container>}}
+
+{{<content-version-container version-label="Altinn Studio Designer">}}
+{{% insert "content/altinn-studio/guides/development/signing/role-based-signing/studio/configure-layouts.nb.md" %}}
+{{</content-version-container>}}
+
+{{</content-version-selector>}}
diff --git a/content/altinn-studio/guides/development/signing/role-based-signing/_index.nb.md b/content/altinn-studio/guides/development/signing/role-based-signing/_index.nb.md
@@ -0,0 +1,45 @@
+---
+title: Rolle- og tilgangspakkebasert signering
+linktitle: Rolle/tilgangspakke
+description: Følg disse stegene for å implementere rolle- og tilgangspakkebasert signering i din tjeneste.
+tags: [rollebasert, signering]
+weight: 50
+aliases:
+- /nb/altinn-studio/guides/signing/role-based-signing
+---
+
+## Hva betyr rolle- og tilgangspakkebasert signering?
+{{% insert "content/altinn-studio/guides/development/signing/role-based-signing/intro.nb.md" %}}
+
+## Avhengigheter
+Dersom appen skal kunne sende signeringskvittering til innboksen til den som signerer så må oppsett for bruk av meldingstjenesten i Altinn være satt opp.
+
+Se [hvordan](/nb/correspondence/getting-started/) du kommer i gang med det.
+
+## 1. Legg til en signeringsoppgave i appens prosess, med tilhørende konfigurasjon
+
+{{<content-version-selector classes="border-box">}}
+
+{{<content-version-container version-label="Manual setup">}}
+{{% insert "content/altinn-studio/guides/development/signing/role-based-signing/backend-manual/add-process-task.nb.md" %}}
+{{</content-version-container>}}
+
+{{<content-version-container version-label="Altinn Studio Designer">}}
+{{% insert "content/altinn-studio/guides/development/signing/role-based-signing/studio/add-process-task.nb.md" %}}
+{{</content-version-container>}}
+
+{{</content-version-selector>}}
+
+## 2. Legg til layout-set for signering
+
+{{<content-version-selector classes="border-box">}}
+
+{{<content-version-container version-label="Manual setup">}}
+{{% insert "content/altinn-studio/guides/development/signing/role-based-signing/backend-manual/configure-layouts.nb.md" %}}
+{{</content-version-container>}}
+
+{{<content-version-container version-label="Altinn Studio Designer">}}
+{{% insert "content/altinn-studio/guides/development/signing/role-based-signing/studio/configure-layouts.nb.md" %}}
+{{</content-version-container>}}
+
+{{</content-version-selector>}}