# Glossary [A](#a) | [B](#b) | [C](#c) | [D](#d) | [E](#e) | [F](#f) | [H](#h) | [I](#i) | [L](#l) | [M](#m) | [O](#o) | [P](#p) | [R](#r) | [S](#s) | [T](#t) | [W](#w) ## A ### Account The primary isolation boundary in Synqly, representing a customer, tenant, or business unit. Every Integration belongs to an Account, and data — credentials, configuration, and operational state never crosses the Account boundaries. - **Test Account** — An Account used for development and validation. Test Accounts use Mock Providers to verify configuration, Mappings, and API behavior without connecting to live systems or processing real customer data. - **Production Account** — An Account used for live integrations. Production Accounts connect to real Providers and process live business data after an integration has been validated in a Test Account. → *Learn more:* [Accounts](/guides/concepts/accounts) ### Adaptive Mapping A feature that configures which Mapping is applied to an Integration — either at the Integration Point level (as a default for new integrations) or at the Integration level (for that specific integration only). → *Learn more:* [Adaptive Mapping](/api-reference/adaptive-mapping) ### Asynchronous Operation An API operation that accepts a request and returns before processing is complete. Rather than returning the result in the same request/response cycle, Synqly delivers the completed result to a configured output Sink. → *Learn more:* [Asynchronous Operations](/guides/async-operations) ## B ### Bloblang A data transformation language used by Synqly to define Custom Mappings. Bloblang expressions transform data between provider-specific schemas and normalized formats. → *Learn more:* [Bloblang](/api-reference/customer-defined-mappings#bloblang-direct-10) ### Bridge An agent that runs within a customer's private network and establishes an outbound connection to Synqly, enabling secure access to private resources without exposing them to inbound internet traffic. → *Learn more:* [Synqly Bridge](/bridge/agent-setup) ## C ### Connect UI An embeddable user interface provided by Synqly that enables end users to connect, authorize, and configure integrations directly within your application. ### Connector Synqly's abstraction layer for a category of Providers. A Connector defines a unified API, a common data model, and consistent operational behavior across all Providers that solve the same business problem. → *Learn more:* [Connectors](/guides/concepts/connectors) ### Connector API The Synqly API surface used to interact with external providers through an Integration, such as fetching events, routing alerts, or creating tickets. Requests are authenticated using an Integration Token. The Connector API is distinct from the Management API, which is used to manage Synqly resources. ### Credential A securely stored authentication secret used to connect to a Provider. Once created, the secret value cannot be retrieved through the API or Management Console. Credentials are referenced when creating Integrations. ### Custom Mapping A user-defined Mapping created in Synqly using Bloblang. Custom Mappings allow you to customize how data is transformed between provider-specific schemas and normalized formats such as OCSF. → *Learn more:* [Customer Defined Mappings](/api-reference/customer-defined-mappings) ## E ### End User A person who uses or authorizes integrations through your application. End Users interact with the application's user interface rather than directly with Synqly and typically do not require access to the Management Console or Management API. → *Learn more:* [End Users](/guides/concepts/end-users) ### Event A structured, timestamped record of an activity that occurred within a connected Provider. Events are the primary data type surfaced by security and observability Connectors — for example, a login event from an identity provider, a detection alert from an EDR platform, or an audit log entry from a SaaS application. Synqly normalizes events to OCSF format via its default Mappings, making them structurally comparable across providers without custom parsing logic. ## I ### Integration A live, authorized connection between an Account and a specific Provider. Integrations reference the credentials and configuration needed to maintain that connection and are the runtime unit Synqly uses to route API calls to the correct Provider on behalf of an Account. → *Learn more:* [Integrations](/guides/concepts/integrations) ### Integration Token An access token that authenticates Connector API calls and is scoped to a single Integration. Issued per integration, per session and with configurable expiration times. Integration Tokens cannot be used to call the Management API. → *Learn more:* [Integration Tokens](/guides/concepts/integration-access-tokens) ### Integration Point A reusable configuration defined at the Organization level that defines the shared settings for one or more Integrations. Integration Points let you define common requirements once, such as which Connector to use or which Mappings to apply, and have them automatically applied when new Integrations are created and associated with the Integration Point. → *Learn more:* [Integration Points](/guides/concepts/integration-points) ## M ### Management API The Synqly API surface for administrative operations — creating Accounts, configuring Integration Points, managing Members, issuing Tokens, and more. Requests are authenticated using an Organization Token. The Management API is distinct from the Connector API, which is used to access provider capabilities. ### Management Console The web-based administrative application available at [app.synqly.com](https://app.synqly.com). Organization Owners and other authorized Members use the Management Console to create and manage Organizations, Accounts, Integrations, tokens, and other Synqly resources without calling the Management API directly. ### Mapping A transformation rule that converts data between formats — for example, from a provider-specific schema to OCSF or vice versa. Mappings use Bloblang and are referenced by its ID or name. ### Member A person or service with access to the Synqly Organization. Permissions and resources constraints are defined by the Roles associated with the Member. → *Learn more:* [Members](/guides/concepts/members) ### Meta Function A request option that instructs Synqly to include additional metadata in an API response, or alter the behavior of the request. Meta Functions can return information such as raw provider responses, statistics, or the mapping chain applied to the request. → *Learn more:* [Meta Functions](/api-reference/meta-functions) ### Mock Provider A simulated Provider used in the Test environment to develop and test integrations without connecting to a live third-party system. Mock Providers emulate provider behavior using synthetic data. → *Learn more:* [Mock Providers](/guides/labs/mock-provider-overview) ### MCP (Model Context Protocol) A protocol that enables AI agents to interact directly with the Synqly integration platform. The MCP Server allows AI agents to manage and use integrations across all Synqly Connectors. → *Learn more:* [Synqly MCP Integration Guide](/guides/mcp-integration-guide) ## O ### OCSF (Open Cybersecurity Schema Framework) An open standard for representing cybersecurity events and related data in a consistent format. Synqly uses OCSF as a common schema when transforming provider-specific security event data through Mappings. → *Learn more:* [OCSF Schema](https://schema.ocsf.io) ### Organization The top-level container in Synqly that owns and governs platform resources. Organizations contain Accounts, Members, Integration Points, tokens, and other resources used to manage access and integrations. → *Learn more:* [Organizations](/guides/concepts/organization) ### Organization Token A token used to authenticate requests to the Management API on behalf of an organization. Organization Tokens provide organization-level access according to their assigned permission. Organization Tokens should be stored securely and never exposed in client-side code. → *Learn more:* [Organization Tokens](/guides/concepts/organization-access-tokens) ## P ### Permission Set A named collection of permissions that defines the API actions a user, service account, or token is allowed to perform. Permission Sets are combined with optional Resource Restrictions to create a Role. → *Learn more:* [API Tokens and Access Control](/guides/security-model/api-tokens-and-access-control) ### Provider A specific third-party service or platform, such as Jira, ServiceNow, Okta, Slack, or Amazon S3, that integrates with Synqly through a Connector. Each Provider exposes its own APIs, authentication requirements, and data model. → *Learn more:* [Providers](/guides/concepts/providers) ## R ### Refresh Token The rotation half of a Token Pair. Used only when refreshing or resetting the active access token, and can not be used for any other API calls. Must be stored securely. ### Resource An entity managed by Synqly that can be accessed or managed through the platform or its APIs. Resources include objects such as Organizations, Accounts, Integration Points, Integrations, and Members. Access to resources is controlled through Permission Sets and Resource Restrictions. ### Resource Restrictions Constraints that limit which resources a Role or token can access. Resource Restrictions narrow access based on resource attributes, such as `account_id`, ensuring permissions apply only to the intended resources. → *Learn more:* [API Tokens and Access Control](/guides/security-model/api-tokens-and-access-control) ### Role A named combination of one or more Permission Sets and optional Resource Restrictions that defines the actions a Member is authorized to perform. → *Learn more:* [Manage Members and Roles](/guides/security-model/manage-members-and-roles) ## S ### Service Account A Member type that represents a non-human identity used by automated systems or processes, such as pipelines, bots, or scheduled workers. Service Accounts are identified by a unique name instead of an email address. → *Learn more:* [Build a Service Account](/guides/security-model/build-a-service-account) ### Sink A configured destination where Synqly delivers data, events, or operation results. Sink Providers define the external storage, messaging, or other delivery systems used by the sink. → *Learn more:* [Sink](/guides/connectors/sink/overview) ## T ### Tenant A customer or customer organization in your system that is represented by an Account in Synqly. Each Account provides an isolated boundary for that tenant's data, credentials, and integrations. → *Learn more:* [Accounts](/guides/concepts/accounts) ### Token Scoping The principle that a token's scope can only be reduced, never expanded. A delegated token cannot grant access to accounts or resources beyond the issuing token's scope, nor can it remove any Resource Restrictions applied to the issuing token. → *Learn more:* [Create Scoped Organization Tokens](/guides/security-model/create-scoped-organization-tokens) ### Token Pair The token structure returned by Synqly token APIs. It contains a short-lived access token for authenticating API requests and a refresh token used to obtain a new access token when the current one expires.