Limosaidentity
← All integrations

Business applications · CONNECTOR GUIDE

Freshservice
Connected to governance.

Agents, agent groups and direct memberships. Requesters, lifecycle suspension, deletion and group writes are outside this connector.

Provider administration APIInventory + supported writes

HOW IT FITS TOGETHER

Connect inventory.
Follow changes through.

Import observed accounts and access, then use configured policies and approved requests to drive supported changes.

Freshservice integration architecture
01 / SOURCE SYSTEM

Freshservice

Accounts and supported access inventory

Provider administration API
Read inventory
02 / CONNECTION

Limosa connector

Authenticate · read · normalize

Import &
correlate
03 / GOVERNANCE

Identity & access

Inventory · policy · review evidence

← Supported changes return through the connector

Supported provider operations execute after the relevant policy and approval steps. Subsequent reads provide observations of the result.

Conceptual architecture, not a product screenshot. Approval, execution and observed access remain distinct.

SUPPORTED FEATURES

What you can do.

The following operations are exposed by this connector. Target permissions, subscriptions and configuration still apply.

  • Import inventory

    Read the connector’s supported records into Limosa.

  • Create accounts

    Create accounts using required target attributes and mappings.

  • Update accounts

    Update the account attributes supported by this connector.

PREPARE YOUR CONNECTION

Start with the right scope
and credentials.

Use an administrator API key and set the group workspace ID. Agents are account-scoped; groups are workspace-scoped.

Credential type

Administrator API key

Provider documentation ↗ (opens in a new tab)

Connection settings

  • Group workspace ID
  • Freshservice instance URL

Required account creation fields

email · first_name

Store credentials through the application’s credential controls or an approved external secret reference. Confirm roster visibility and review import policy before the first full import.

FROM CONNECTION TO GOVERNANCE

Map & correlate

Choose stable identifiers, map source attributes and link accounts to the right governed identities.

Review the inventory

Check imported records and memberships. Resolve unexpected gaps before relying on the connection for governance.

Enable changes deliberately

Configure supported writes, test the target behavior and follow provisioning history separately from approval decisions.

FULL AI SUPPORT

Your workflow.
Your AI assistant.

Operate and configure Limosa through an MCP-compatible AI assistant. The full management interface is available to AI, with the same permissions, validation and audit trail as the web workspace.

Start with https://identity.limosa.io/mcp. No existing Limosa account needed: sign in and create your workspace when prompted.

Connect your assistant ↗

YOUR NEXT STEP

See governance in practice.

Explore the public demo or bring your applications and governance questions to a guided conversation.