Fulfillment Options
Last updated
Was this helpful?
Last updated
Was this helpful?
BalkanID supports multiple fulfillment options allow you to configure how user accounts should be provisioned or deprovisioned for different applications connected to the BalkanID system, providing a super simple process to setup and versatility to configure via IdP, directly fulfill provisioning, connect via SCIM server, or create tickets for management via a Ticketing and Work Management solutions, or call webhooks and playbooks.
Note: To enable Fulfillment Options for your account, please .
The options are:
Fulfillment Option
Description
SSO or Federation
The user account will be provisioned in / deprovisioned from the IDP of the tenant
SaaS Direct or Direct
The user account will be provisioned in / deprovisioned from the app itself
Ticket Creation
The system will create a ticket to the ticketing system for manual provisioning / deprovisioning
SCIM or CLI
The account provisioning / deprovisioning will happen via SCIM (Needs SCIM configuration to be done first)
Webhook
The webhook configuration will be triggered post actions (Needs Webhooks to be setup first)
Playbook
The playbook server will be called post actions (Needs Playbook configuration to be done first)
The current set of applications supported are:
Fulfillment Option
Description
SSO or Federation
Custom
SaaS Direct or Direct
AWS, AzureAD, Google, Okta, and other apps on demand
Ticket Creation
Atlassian Jira
SCIM or CLI
All applications (Needs SCIM server steup and configuration to be done first)
Webhook
All applications (Needs Webhooks to be setup first)
Playbook
All applications (Needs Playbook configuration to be done first)
1. Go to Integrations page under Configure on your BalkanID tenant.
2. For the desired application integration click on Setup.
3. Enable the fulfillment options as you need for the particular application integration.
4. Once done, click on "Save Changes".
VoilĂ , all set! Your newly set fulfillment options will be taken into account if any event takes place on the event in the system.