License types

Last updated: February 19, 2026

Overview

amplo licenses control how people and systems access amplo’s managed package inside Salesforce. Assigning the right license ensures users and integrations can view and interact with amplo’s custom objects and fields as intended. For more information on adding new licenses, see 📄 User management.

amplo

There are two primary license types:

  • Essential user license

  • Integration user license

Each serves a different purpose. Understanding the difference helps you maintain clean access controls, protect your data, and keep your Salesforce environment organized as your team evolves.

Essential user license

An Essential user license is assigned to an individual person. It grants access to the necessary custom objects and fields included in amplo’s managed package. In short, this license allows a team member to use amplo within Salesforce as part of their daily workflow.

When to use it

Assign an Essential user license to:

  • Account managers

  • Producers

  • Service representatives

  • Operations team members

  • Any employee who works directly in amplo

If someone needs to view, edit, or interact with amplo data, they should have an Essential user license.

Integration user license

An Integration user license is assigned to an application or external system — not a person. It allows that system to access amplo’s custom objects and fields in Salesforce.

This setup is common and recommended in Salesforce environments. Instead of connecting integrations through an individual employee’s login, you create a dedicated Integration user.

When to use it

Using an Integration user license helps you:

  • Maintain consistency when employees join or leave

  • Keep integrations independent from individual user accounts

  • Preserve a clean and accurate audit trail

  • Simplify ongoing maintenance and upgrades

Example

Suppose your agency uses an external quoting platform. Instead of connecting that platform through an employee’s Salesforce login, you would:

  1. Create a dedicated Integration user.

  2. Assign the Integration user license.

  3. Connect the quoting platform using that Integration user.

When data flows into Salesforce and amplo, the audit trail will show that the “Integration User" made the update. This keeps system activity separate from employee activity and avoids confusion about who made specific changes.

amplo can also use an Integration user to access your org for upgrades or support, though it is not strictly required. Without one, you may need to complete a few additional steps to grant temporary access.

Best practices

  • Create one Integration user per external system.

  • Use clear naming conventions (for example: “Integration – Quoting Platform”).

  • Avoid tying integrations to individual employees.

  • Review license assignments periodically to ensure only active users have access.

AccountingSeed

AccountingSeed licenses control how users access embedded insurance accounting functionality within Salesforce. Choosing the right license ensures team members have the level of accounting access they need — without adding unnecessary permissions. There are two primary license types:

  • Full use

  • Limited use

Full use

A Full use license is a named user license that provides complete access to embedded insurance accounting functionality inside your Salesforce org. With a Full use license, a user can directly access:

  • General ledger

  • Journal entries

  • Accounting variables

  • Bank deposits

  • Month-end close functions

When to use it

Assign a Full use license to users who:

  • Oversee financial reporting

  • Manage the general ledger

  • Perform reconciliations

  • Handle month-end or year-end close

  • Require broad accounting visibility and control

This license is designed for users who manage or oversee accounting operations.

Limited use

A Limited use license is a named user license that provides limited access to specific embedded insurance accounting functions within Salesforce. They allow users to complete role-specific tasks without granting full access to core accounting controls like the general ledger or month-end close processes. This helps maintain appropriate access boundaries while still supporting day-to-day operations. Below are examples of how limited user licenses are applied:

Account manager / producer

Can:

  • Create billings

  • View billing status

  • Create credit memos

  • Print invoices

  • View status of payables

  • Access related reporting

This supports revenue-related activity without providing direct ledger access.

AP/AR clerk or customer service representative (handles cash)

Can:

  • Create billings

  • Create credit memos

  • Post cash receipts

  • Process payables

  • Process cash disbursements

  • Access related reporting

This role requires transactional accounting access but does not typically manage the general ledger structure.

Customer service representative (does not handle cash)

Can view:

  • Billings

  • Credit memos

  • Cash receipts

  • Producer payables

This role has visibility into financial activity but does not post or process accounting transactions.

Best practices

  • Assign Full use licenses only to users who require ledger-level control.

  • Use Limited use licenses to align access with job responsibilities.

  • Review license assignments regularly to ensure they match current roles.

  • Avoid granting broader access than necessary — clear role alignment strengthens internal controls.

Clear license management builds a strong accounting foundation. It keeps financial data secure, responsibilities well defined, and your amplo environment easier to maintain over time.