Custom Approval Types
Custom Approval Types allows you to define specialized approval criteria, attributes, and multi-language translations for your interactive application. All approvals defined here will be visible in your Authenticator App.
Management of Custom Approval Types is strictly restricted to Visma internal teams (1st-party context).
Managing Approval Types in the Portal
1. Viewing Existing Approval Types
When you navigate to your application's Authenticator App menu, you will see a list of all active Custom Approval Types configured for that specific client.
If no custom approval types have been set up yet, the list will appear empty.
You can click on any specific approval type in the list to view its detailed configurations, attributes, and language translations.
2. Creating a New Approval Type
To set up a new validation requirement:
Click the + Add New Approval Type button.
Define the Type Identifier (a unique systemic name) and the Display Name your team will see.
Add Attributes (between 1 and 10 custom fields) that this approval process must capture. Each attribute requires a unique key and a user-facing label.
You can see (in the last column below) how the user of the Authenticator app will see your approval.
Save your changes.
Note: The system will automatically block you from saving if the Approval Type name already exists, or if you use restricted/reserved attribute names.
3. Updating an Existing Type
If your business workflow changes, you can modify existing configurations:
You can update display names, add/remove attributes (within the 1–10 limit), and update localized language translations.
Changes take effect immediately across the authenticator module.
4. Deleting an Approval Type
If a specific approval process is no longer required by your application, you can delete it by clicking the Delete button next to the type.
Warning: This action is permanent. Once deleted, the application will no longer challenge users with this specific approval criteria.
Language & Translations
Custom Approval Types fully support multi-language environments using standard language codes (such as en for English, no for Norwegian, etc.).
When creating or editing an approval type, ensure that every custom attribute label you define has a matching translation for the languages your users require. If a translation is misconfigured or missing its matching attribute key, the portal will display a validation error and prevent you from saving.