Corma combines up to 10 types of data sources to build a full picture of your apps, users, licenses and costs. Each type brings a different piece of that picture, so the more you connect, the more complete and accurate your data becomes.
Browser extension
Installed on your employees' browsers through your device management tool. Available on Chrome, Edge and other major browsers.
What it brings to Corma
The web apps employees use and when, including apps IT doesn't know about yet (Shadow IT and Shadow AI). It also shows employees your Shadow IT policies.
What it collects, and what it doesn't
Only work-related apps. Corma doesn't display websites that aren't related to work.
Only the professional browser session. The extension is deployed on the work profile, not on personal sessions such as a personal Gmail account.
Usage, not accounts. The extension sees that an app is used, not which account is used. Corma can't tell a personal ChatGPT account from a professional one.
The extension only sees the browsers it is installed on. If employees use several browsers, deploy it on each one.
OS agent
Installed on your employees' Windows computers, through Microsoft Intune or Group Policy (GPO).
What it brings to Corma
The apps installed and used on the computer, outside the browser.
Good to know
Users are identified through Microsoft Entra ID.
Usage, not accounts. Like the extension, the OS agent sees that an app is used, not which account is used.
When it syncs: the first data can take up to 48 hours to appear after deployment.
Integrations
Connected from the Connectors page in a few clicks. Corma connects to your tools in two ways: through their API, or through a browser agent.
API connectors
Data source | Examples | What it brings to Corma |
|---|---|---|
SSO providers | Microsoft Entra ID, Google Workspace, Okta | Your users and their IdP status, the apps employees sign in to with SSO, their sign-in activity, and the OAuth tokens granted to third-party apps |
Password managers | LastPass, Bitwarden | Third-party app usage and license data, from the password manager's audit logs |
SaaS apps | Slack, Notion, Atlassian, Adobe | For each app: the users who hold a license, license type, role, date granted and last activity. With writes turned on, Corma can also create and remove accounts |
HR tools | Lucca, Personio, BambooHR | Start and end dates, job title, team, manager, country and custom fields. This sets each user's HR status |
Device management (MDM) | Jamf, Microsoft Intune | Your computers, their owners, operating system and installed apps. Turn on Reads → Devices in the connector |
When it syncs: API connectors sync once a day. Your first data arrives within 24 hours of connecting.
Each integration depends on the vendor's API. Not every app shares last activity or roles, or lets Corma create and remove accounts.
Browser agents
For apps with no API, or an API that doesn't cover what you need. Agents work in the app's admin interface the way an admin would, and appear on the Connectors page next to your other connectors.
Agent | What it does |
|---|---|
Extractor agent | Reads the app's member and license list, so Corma knows who has access |
Clicker agent | Creates and removes accounts in the app, for onboarding and offboarding |
You can build an agent for any app yourself with the Custom Agent, from the Connectors page.
Contracts and expenses
Corma tracks what you committed to pay (contracts) and what you actually pay (invoices with amount, currency, date and supplier). You can bring this data in several ways:
Accounting tools: connect a tool such as Pennylane or Qonto from the Connectors page. It syncs once a day.
Invoices by email: forward the invoices you receive to your dedicated Corma address. Corma automatically matches each invoice to the right app and imports it, every morning (Paris time). This works well if you don't use a finance tool Corma integrates with.
Import with AI: drop a PDF invoice or contract and Corma fills in the details.
Invoices are matched to apps by supplier name. A supplier name that starts with the app name (for example
Slack SAS) matches best.
Other ways to add data
When no source covers something, you can add it yourself:
CSV import: users or licenses in bulk.
Manual entry: from the app's page.
Where to start
Start with your SSO provider. It is the foundation of Corma's data: it creates your user list and shows which apps your employees sign in to. Then add the sources that matter most to you.
Reads and writes
Each connector lists what it reads from an app (users, licenses, last activity, HR data, expenses) and what it writes back (creating an account, removing a user from a group, revoking a license). You can turn each read and write on or off on its own, without disconnecting the connector.
ℹ️ To see exactly which data Corma collects from each source and how it is protected, read Security, Data & Privacy.
🎯 Use cases
Deploying the OS agent via Group Policy (GPO)
How to import licenses via CSV
How to import invoices into Corma
The data you see in Corma is only as complete as the sources you connect. If a license shows as Unknown, no source follows that app or that user yet.
