---
title: "Integration Profiles Explained"
slug: "integration-profiles-explained"
updated: 2025-12-14T14:36:51Z
published: 2025-12-14T14:36:51Z
canonical: "resources.realtheory.io/integration-profiles-explained"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://resources.realtheory.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration Profiles Explained

Integration Profiles store a specific set of configuration options so users do not have to enter the third-party ticketing system configuration details each time they want to open a ticket against a RealTheory recommendation. These profiles define the connection between RealTheory and a specific third-party ticketing system, including the authentication credentials, the project, and the default ticket type settings.

## Example

You have two teams that use the same Jira project, but each team needs a different Default Issue Type.

You might create the following two Integration Profiles:

### Profile 1 for the DevOps Team

- Profile Name: DevOps-Bugs
- Description: For logging defects in deployment configurations
- Provider: Jira Cloud
- Authentication:
  - Username: K8S_PROD@serviceaccount.atlassian.com
  - Secret: <API Token>
- API URL: https://company.atlassian.net
- Console URL: https://company.atlassian.net
- Default Project Key: K8S_PROD
- Default Issue Type: Bug

### Profile 2 for the Platform Team

- Profile Name: Platform-Stories
- Description: For creating infrastructure/operational requests
- Provider: Jira Cloud
- Authentication:
  - Username: K8S_PROD@serviceaccount.atlassian.com
  - Secret: <API Token>
- API URL: https://company.atlassian.net
- Console URL: https://company.atlassian.net
- Default Project Key: K8S_PROD
- Default Issue Type: Story

By creating two Integration Profiles, team members simply select the appropriate profile when creating a ticket, and RealTheory opens the correct issue type in the correct Jira project.

## Support for Multiple Profiles

Teams often create multiple profiles for practical reasons, such as:

- Different **Issue Types** (Bugs vs Stories vs Tasks)
- Different **Projects** (ENG vs OPS vs QA)
- Different **environments** (Jira Cloud vs Jira Data Center)
- Different **team boundaries** or workflows
- Different **authentication credentials** (required when integrating with different ticketing systems or different security domains)

RealTheory places no restrictions on the number of profiles you can create.

**See Also** [Creating an Integration Profile](/v1/docs/creating-an-integration-profile)