Create an issuance template
An issuance profile is what you actually issue from. It bundles one or more document types with the flow and policy used to hand them over.
What a profile decides
| Contents | Which document types, in which formats — a profile may issue several at once |
| Grant type | Pre-authorized code, or authorization code with an upstream identity provider |
| Claim source | Your request body, or attributes resolved from a login |
| Policy | The assurance posture applied to the issuance |
Because the profile fixes all of this, issuing is a single call: reference the profile, supply the data.
Getting one
Issuance profiles are provisioned by LutraID. The organization API exposes the catalogue read-only; what you control is which profiles each issuer may use.
Tell us which document types belong together, whether claims come from your systems or from a login, and whether a transaction code should be required.
Assign it to an issuer
Open the issuer under Issuers and assign the profile from its detail page. Over the API this is a PUT on the issuer's issuance profiles; unassigning is a DELETE. An issuer can only issue from profiles assigned to it, and a mismatch is the usual cause of a profile not appearing in the Issue wizard.