LogoLogo
SupportDeveloper Docs
  • Welcome
  • Getting Started
    • Introduction to BalkanID
      • BalkanID Onboarding
      • BalkanID Summary Dashboard
    • Setting Up BalkanID
      • User Role Management
      • Users Entitlements Discovery
      • Employee Data Extraction
      • Application Integration & Entitlement Data Extraction
      • Business Owners for Application Integrations
    • Entitlement Discovery
      • Entitlements Discovery
      • Applications Entitlements Discovery
      • Connection Entitlement Discovery
      • Resource Entitlement Discovery
      • Identities Entitlements Discovery
      • Working with Filters
      • Impact Analysis
    • Access Review Management
      • Access Review Campaigns
      • Performing Access Reviews
      • Campaign dashboard and management
      • Campaign Audit Reporting
      • Access Review Campaign Notifications and Reminders
      • Configuring Integration Specific Multi-Level Review Settings
      • Configuring Multi-Level Review Settings in Campaigns
      • Reviewer Insight Escalation for Campaigns
      • Recurring Campaigns
      • Campaign Escalation
      • Nominate Delegate In Account Preferences
      • Access Review Graphs
      • Access Review Recommendations
    • Access Request Management
      • Creating and Managing Access Requests
        • New User Access Request
        • New Service Account Access Request
        • New Identity Access Request
        • New Connection Access Request
        • New Resource Access Request
        • New SCIM Access Request
    • System Notifications & Automatic Ticket Creation
      • Notification Preferences
      • In-app Notifications
      • Supported Ticketing Systems
    • BalkanID CLI
      • BalkanID Extractor CLI
      • BalkanID API CLI
  • Configurations and Integrations
    • Integrations Overview
    • HRIS Integrations
      • Integrate via Merge
    • Direct Application Integrations
      • Asana Integration Setup
      • Atlassian Confluence Integration Setup
      • Atlassian Jira Application Integration Setup
      • AWS Application Integration Setup
      • AWS Identity Center Integration Setup
      • Bitbucket Integration Setup
      • Box Integration Setup
      • Code Climate Integration SetupPage
      • Datadog Integration Setup
      • Dropbox Integration Setup
      • GitHub Application Integration Setup
      • Gitlab Integration Setup
      • Google Cloud Platform Integration Setup
      • Google Drive Integration Setup Guide
      • Google Workspace Integration Setup
      • Jenkins Integration Setup
      • JumpCloud Integration Setup
      • MariaDB Integration Setup
      • Microsoft Azure and Active Directory (AD) Integration Setup
      • On-Prem Active Directory (AD) Integration Setup
      • Microsoft Office365 Integration Setup
      • MongoDB Integration Setup
      • MySQL Integration Setup
      • Netsuite Application Integration Setup
      • New Relic Integration Setup
      • Okta Application Integration Setup
      • Onelogin Integration Setup
      • OpenVPN Integration Setup
      • Pagerduty Integration Setup
      • Ping Identity Integration SetupPage
      • PostgreSQL Integration Setup
      • Ramp Integration Setup
      • Salesforce Application Integration Setup
      • SAP Integration Setup
      • Sendgrid Integration Setup
      • Sentry Integration Setup
      • Slack Application Integration Setup
      • Smartsheet Integration Setup
      • Snowflake Integration setup
      • Splunk Integration Setup
      • Sumologic Integration Setup
      • Twingate Integration Setup
      • Zoom Integration Setup
    • Manual Uploads
      • Application Entitlement Data
      • Employee Data
      • Mapping Identities to Employees
    • SSO Integrations
      • Ping Identity
      • Okta
      • OneLogin
      • Microsoft
    • Fulfillment Options
    • BalkanID API
  • Playbooks and Webhooks
    • Playbooks Overview
    • Configuring Global Playbooks
    • Configuring Integration Specifc Playbooks
    • Configuring Global Webhooks
    • Configuring Integration Specific Webhooks
    • Automated Employee Data Upload Playbook with AWS Lambda & S3
    • Automated Entitlement Data Upload Playbook with AWS Lambda & S3
  • IAM RISK ANALYZER
    • Findings
    • Current State RBAC
    • IAM Risk & RBAC Analysis Report
  • Insights and Rules
    • Entitlement Rules & Labels
      • Setup Rules and Labels
      • Terminated Employee Label
      • Privileged identity Label
      • Setup privileged identities
    • Entity Insights and Finding Rules
      • Creating entity filters
      • Setup insights using entity filters
      • Setup finding rules using entity filters
  • BalkanID Slackbot
    • Setting up BalkanID Slackbot
    • Access Requests and Access Review Notifications with BalkanID Slackbot
    • Findings (Daily Alert) with BalkanID Slackbot
  • JITPBAC
    • Overview of JITPBAC
    • Purposes
      • Create Purpose
      • Edit Purpose
      • Delete Purpose
      • Filtering Purposes
      • Create User-Purpose Access Request
        • Creating a Request Through the Web App
        • Creating a Request Through the Slackbot
      • Starting & Stopping Assigned Purposes
  • BalkanID Copilot
    • BalkanID Copilot
  • Updates
    • Release Notes
      • Introducing Findings: Prioritize, Act, and Automate Identity Risk Management
      • Action Center as a command hub for identity risk findings
      • Introducing Impact Analysis: Visualize, Understand, and Manage Access
      • In-app Notifications & Notification Preferences
      • Upgrades to RBAC Analyzer
      • Slackbot for Access Requests and Review Notifications
      • Playbooks and Webhooks for enhanced workflow automation
      • Introducing support assistant for BalkanID application for in-app support
      • Scheduling campaigns & multi-level approvals, nomination & delegation of reviews and graph views for
      • Campaign dashboard actions, access reviews by identity, enhanced access requests and entities connec
      • Access Provisioning & Deprovisioning, Email Notifications, Access Reviews & Campaigns Updates and Ne
      • Quickly find what you’re looking for with the new People, Applications, and Identities pages
      • Integrate your HRIS or Identity Provider without exposing sensitive personnel data or powerful admin
      • Quickly find unusual entitlements with Outliers (Early Access)
      • Announcing “Days Since Termination” filter
      • Announcing JumpCloud direct integration
      • Published Access Review Campaigns can now be deleted
      • Easily switch between tenants using the new tenant picker
      • Skip Access Review Campaigns by downloading a PDF report of your Entitlements
      • User account information now available on the Account page
      • Announcing Bulk API (Early Access)
      • Announcing HRIS integration capability with 23 new HRIS integrations
      • Privileged Identity insights help to quickly identify privileged identities
      • Terminated insights help to quickly identify and remediate entitlements held by terminated employees
      • Announcing Azure and Azure Active Directory direct integration
      • Access Review Campaign drafts can now be permanently deleted
  • Terms & Conditions
    • Privacy Policy
    • Terms of Service
    • AI Policy FAQ
    • Trust Center
Powered by GitBook
On this page
  • Overview
  • Who are Business Owners?
  • How to Set Up Business Owners
  • Why Are Business Owners Important?
  • Best Practices for Assigning Business Owners

Was this helpful?

Export as PDF
  1. Getting Started
  2. Setting Up BalkanID

Business Owners for Application Integrations

PreviousApplication Integration & Entitlement Data ExtractionNextEntitlement Discovery

Last updated 3 months ago

Was this helpful?

© 2025 · BalkanID, Inc. | Nothing on the BalkanID website, platform, or services, nor any portion thereof constitutes actual legal or regulatory advice, opinion, or recommendation by BalkanID, Inc.

Overview

In the context of application integrations, Business Owners are key individuals responsible for managing and overseeing access to connections/resources within an integrated application. These owners play a vital role in ensuring that access reviews, access requests, and other important tasks are properly handled with respect to a connection/resource their assigned.

This documentation will guide you through the concept of business owners, how to assign them, and the responsibilities associated with each role.

Who are Business Owners?

Business Owners are designated individuals or groups with the authority to manage access to specific resources and connections within an integrated application (e.g., Okta, GitHub, etc.). They are responsible for reviewing access, approving or denying requests, and ensuring that permissions remain up-to-date and compliant with the organization’s security policies.

In other words, Business Owners oversee access to the resources and connections they manage.

There are two types of business owners you can assign:

  • Primary Owner: The main individual responsible for overseeing the application resources/connections and taking action on access reviews and requests.

  • Secondary Owner: An additional individual(s) who can take over responsibilities if the primary owner is unavailable.

How to Set Up Business Owners

To configure business owners for an application integration, follow these steps:

  1. Open the Application Integration Setup Modal Navigate to the Integrations page under the Configure section. You will see a list of your application integrations.

  2. Select an application to setup business owners Choose which application integration you'd like to setup business owners. Click on the "Setup application business owners" icon (). This will open a dialog with a table showcasing a list of connections and resources within your integration.

  3. Assign Business Owners

    You have two choices ahead of you:

    1. Mapping via UI Select the connections/resources you would like to map. Clicking on the "Map Business Owner(s)" will open a sidebar. Click on "Save changes" after selecting your choice of business owners or click on "Map to App Owner(s)" if you want to map the selected connections/resources to the application integration owner.

    2. Bulk Business Owner Mapping: Business Owners can be mapped by uploading the BO mapping CSV. Simply click the “Map Business Owner(s)” button without selecting any connections or resources. This will open a side panel where you can download the mapping CSV. After filling in the CSV with the primary and secondary owner emails for a set of entities (connections/resources), you can upload it back using the same panel. The secondary owner emails should be separated by a semicolon (;). Once the mapping is complete, upload the CSV in the designated section of the side panel and click the “Upload New Mapping” button. The mapping will be processed and updated in the UI within a few minutes.

Why Are Business Owners Important?

Many enterprises have multiple applications federated with their primary Identity Provider (IDP) application (e.g., Okta, OneLogin). These federated applications are treated as separate resources during entitlement discovery. Since each resource is an application in itself, different users typically manage and oversee access to each application.

By assigning primary and secondary business owners to these application integrations, each set of owners can take responsibility for their specific application’s access reviews and requests. The primary owner is the main point of contact for managing and approving access, while the secondary owner serves as a backup.

This approach ensures that access reviews and requests are handled by the right individuals with the appropriate expertise for each application, improving efficiency. It also helps in maintaining segregation of duties, as different owners are responsible for different applications, reducing the risk of conflicts or errors. Ultimately, having them streamlines access management and ensures the right approvals are made in a timely and compliant manner.

Best Practices for Assigning Business Owners

  • Ensure Clear Responsibility: Clearly assign the primary business owner to avoid confusion and ensure accountability. The primary owner should be someone who is actively involved in managing the connections/resources they are assigned to.

  • Use Secondary Owners for Continuity: If the primary owner is frequently unavailable, consider assigning a secondary owner to ensure continuity in access management. Secondary owners can help prevent delays and ensure that the right approvals are made.

  • Review Ownership Regularly: As your team or organization evolves, periodically review and update the assigned owners to ensure they remain appropriate for the tasks at hand.