At a glance: Enhance your account protection with the Enterprise-Grade Security Package, a premium offering designed for enterprise-grade identity management, token access control, and extended audit visibility.
Intro
The Enterprise-Grade Security Package brings together three key features that elevate your organization’s security:
- Multi-token management with service restrictions: Scalable token creation and granular access controls across APIs, S2S, and OneLink.
- Audit log API with extended retention: Gain long-term visibility into platform activity and integrate audit events into your monitoring stack.
- SCIM provisioning: Automate and centralize user access control via your identity provider.
- IP allowlist for Login: Prevent unauthorized access, ensuring log in to the AppsFlyer dashboard from only trusted networks and IPs
Compare the standard and Enterprise-Grade packages:
| Feature | Standard package | Enterprise-Grade Security Package |
|---|---|---|
| Single sign on (SSO) | SSO login (existing customers only) | SSO SAML 2.0 with SCIM provisioning for automated user and role management |
| Token management | Manage up to 2 tokens per type (API, S2S, or OneLink) | Manage multiple tokens per type (up to 30) with granular permissions |
| Audit log access | UI access only, 90 day retention data | UI and API access, 180-day data retention |
| User management based on roles (RBAC) | Up to 10 custom roles | Up to 50 custom roles |
| IP allowlist | IP Allow list for APIs | IP allowlist for Login and APIs for enhanced security |
| 24/7 security monitoring | Included | Included |
| Multi-factor authentication | Included | Included |
Multi-Token Management with Restrictions
Create and manage up to 30 tokens per type (API, S2S, OneLink) with service-level restrictions to enhance scalability, security, and control over tokens.
Key features
- Admins can create up to 30 tokens per type, compared to the 2 tokens with the standard tokens, supporting larger teams and complex workflows.
- Assign service-specific access permissions to API tokens, restricting access to sensitive operations.
- Tokens can be revoked or rotated without breaking integrations or automations.
- Restrict a token to a specific app so the token can only access data or perform actions for that app.
- Simplifies collaboration with internal teams and external partners through token-specific permissions.
Example
Create two tokens to help maintain least-privilege access and prevent accidental data exposure.
Data only access token: Create a token that accesses aggregated data only. This token won’t be able to access raw data or perform actions like configuration changes. Use this for analytics teams or read-only agency users.
Settings-only access token: Issue a token that lets internal teams manage configuration settings but doesn’t allow them to pull data. This isolates admin capabilities from data access.
App-specific access token: Create a token that works for one app only. Use this token when an internal team, external partner, or automation must access only a specific app.
Note
For general information about standard tokens, see managing AppsFlyer tokens.
How to access and control tokens
To create a restricted token
- From the top bar, open the account menu (email address dropdown) -> Security Center.
- Go to the Token Management page.
- Click Create Token.
- Select the token type:
- API
- S2S
- OneLink
- For API tokens, select one or more services from the Access restriction dropdown.
Access is binary: full access or none. - Select the restriction type:
- Service restriction: Select one or more services from the Access restriction drop-down list.
- App restriction: Select the app that the token can access.
- Click Save
Manage tokens
To manage your tokens, from the top bar, open the account menu (email address dropdown) -> Security center -> Token Management page.
Here you can:
- View token metadata: name, type, restrictions, creation/expiration
- Delete tokens individually
- Monitor token activity in audit logs
Note
Tokens cannot be edited. To change access, delete, and recreate a token.
Audit log API and extended retention
Enhancing the existing audit log capabilities, this feature introduces an API for audit log consumption and extends data retention from 90 days to 180 days. Ideal for teams needing long-term access to user action logs or integrating audit events into external monitoring tools like SOC and SEIM.
Key features
- Access audit logs programmatically using a dedicated API
- Retain logs for up to 180 days, compared to 90 days with the standard audit logs
- Filter and export data for compliance, security, or operational use
- Use service-specific tokens to isolate log access
- Export data to SIEM tools, dashboards, or cloud storage
Note
For general information about the standard audit log, see Standard audit log.
How to access the audit log via API
To use the Audit Log API:
- From the top bar, open the account menu (email address dropdown): Security Center.
- In the Audit log section, click View audit log.
- Go to the Token Management page.
- Use an existing or create a new API token.
- Under Access restriction, select Audit log service.
- Use the token to authenticate requests to the audit log API endpoint.
Note
Make sure to store your API token securely. It can’t be retrieved after creation.
SSO and SCIM provisioning
SCIM provisioning enhances AppsFlyer SSO capabilities by automating user lifecycle management directly from your identity provider (IdP), such as Okta, Entra ID (Azure), OneLogin, JumpCloud, or self-managed IDPs supporting attribute-based access. This allows organizations to onboard, update, or deactivate users without manual intervention.
By syncing users via SCIM, you maintain full control over access permissions in real-time. Combined with SAML 2.0 SSO, this forms a complete identity and access management solution for enterprise customers.
Key features
- Automatically create users in AppsFlyer based on identity provider (IdP) records.
- Changes in user roles or status in the IdP are instantly reflected in AppsFlyer.
- Uses SAML 2.0 for secure SSO and SCIM for provisioning—compatible with leading IdPs like Okta and Azure AD.
How to set up SCIM provisioning
To start using SCIM provisioning in AppsFlyer, you need to:
SSO set up
To set up SSO, you need to:
Enable SCIM
Note
To enable SCIM, SSO must be set up first.
To enable SCIM, there are a few steps that must be followed:
- Follow the idP configuration instructions
- Configure the SCIM connections
- Add the SCIM Attributes
- Add roles
- Add external namespace
IdP instruction links
The instructions for the IdPs can be found below. Okta, Entra ID (Azure), OneLogin, JumpCloud
SCIM connections
In the SCIM connections, the following fields must be filled in:
| Field name | Value |
|---|---|
| SCIM connector base URL (SCIM endpoint) | https://hq1.appsflyer.com/api/scim/v2 |
| Unique identifier field for users | userName |
| Authentication method: HTTP header called "Authorization" | Bearer <Your AppsFlyer API token> |
SCIM attributes
| Attribute | Type | Required | Field name | External namespace | Description |
|---|---|---|---|---|---|
| Role | String | ✅ | role | urn:ietf:params:scim:schemas:extension:AppsFlyer:2.0:User |
|
| Allow access to all future apps | Boolean | ❌ | allowAccessToAllFutureApps | urn:ietf:params:scim:schemas:extension:AppsFlyer:2.0:User | If enabled, the user will be granted access to new apps automatically. |
| Allowed App IDs | String | ❌ | appIDs | urn:ietf:params:scim:schemas:extension:AppsFlyer:2.0:User | Comma-separated list of app IDs. Leave empty for all apps or set to "None" for no apps. |
Roles
The roles must match the AppsFlyer roles. The table below shows the current AppsFlyer roles and their values. Custom roles can be added. For JumpCloud, see the limitations below.
| Display name | Value |
|---|---|
| Admin | admin |
| Team manager | team_manager |
| Marketing lead | marketing_lead |
| Marketing | marketing |
| Marketing-limited | marketing_limited |
| Contributor | developer |
| Accounting | accounting |
| Security | security |
| Quality Assurance | quality_assurance |
| Custom Role | [enter custom role value] |
Limitations
| Limitation | Description |
|---|---|
| JumpCloud - custom atttributes | Custom attributes aren’t supported. As a workaround, map the Role field to the supported field Work Street Address. See JumpCloud SCIM support. |
IP allowlist for Login
Enhanced IP allowlisting improves security by preventing unauthorized access, ensuring only trusted networks can interact with the platform. This feature is especially valuable for enterprises enforcing strict security policies or managing remote access.
Key features
- Reduces attacks by blocking login attempts from unknown IPs.
- Enables the ability to specify IP addresses or ranges to ensure that only authorized users and networks can access the platform.
- Ideal for organizations using VPNs or requiring stricter access controls.
Adding IPs to the list
- From the top bar, open the account menu (email address dropdown) > Security center.
- In the Login IP allowlist section, click Manage IP allowlist.
- Add IPs manually or via a CSV upload.
- If adding manually, enter the IP address or CIDR range and click Add IP to list.
- Examples:
192.168.1.1,185.114.120.140 - To enter a range of IP addresses, use this format:
185.114.120.1/32
(where185.114.120.1is the first address in the range and185.114.120.32is the last address in the range).
- Examples:
- If adding manually, enter the IP address or CIDR range and click Add IP to list.
- Added IPs will be shown on the right side under See your IPs in the IP allowlist.
- Click Save list.
Important!
- Make sure the IP addresses or ranges you add are correct. Incorrect entries may prevent you from accessing your account.
- The allowlist must contain at least one IP address or range before you can save and activate it, and you can add up to 100 IP addresses or ranges to the allowlist.
- After you click Save list, the IP restrictions will be enforced starting with your next log in.
Removing IPs from the list
- From the top bar, open the account menu (email address dropdown) > Security center.
- In the Login IP allowlist section, click Manage IP allowlist.
- Added IPs will be shown on the right side under See your IPs in the IP allowlist.
- Click the trash icon next to the IP address you want to delete.
- Be sure to save your changes by clicking the Save list button.
Frequently asked questions about our security package
What is AppsFlyer's Enterprise-Grade Security Package?
Scale securely with advanced security capabilities that go beyond standard protections. Get SSO with SCIM provisioning, granular access controls, extended audit logs, and compliance tools designed for enterprise security and IT leaders.
Who is the Enterprise-Grade Security Package designed for?
Enterprise security and IT leaders preparing for audits, procurement and legal teams in regulated industries evaluating SaaS vendors, and platform admins managing complex access requirements across multiple teams and integrations.
How does SCIM provisioning work?
Automate user lifecycle management by connecting directly with your identity provider. SCIM automatically syncs user access and roles, handles instant onboarding and offboarding, and eliminates manual account management and orphaned access risks.
What compliance standards does this support?
Support audit readiness for SOC2, ISO 27001, and GDPR requirements with 180-day audit log retention, comprehensive access documentation, and real-time SIEM integration for continuous monitoring and compliance verification.
How many roles and API tokens can I create?
Create up to 50 customizable roles tailored to your organizational structure and up to 30 service-specific or app-specific restrictions. Isolate access for different integrations and job functions while maintaining least-privilege principles.
Can I integrate with my existing security tools?
Yes. Stream audit data directly to your SIEM and security tools through API-based log streaming. Enable real-time monitoring, anomaly detection, and automated security responses within your existing SOC infrastructure.
What network restrictions can I apply?
Control platform access through IP allowlists and geographic restrictions. Define trusted networks and locations to prevent unauthorized access while supporting remote work scenarios and secure partner collaboration.
How long are audit logs retained?
Access comprehensive audit trails with 180-day log retention that captures every platform interaction. Get complete visibility into user actions, API calls, and access patterns for thorough compliance documentation and security investigations.
Does this replace standard security features?
No. The Enterprise-Grade Security Package adds advanced capabilities on top of standard security features. You get enhanced controls, automation, and visibility while maintaining all existing security protections.
How quickly can I implement these security controls?
Deploy enterprise security controls rapidly through seamless SSO integration and automated SCIM provisioning. Most organizations can implement core features within days while maintaining operational continuity and user productivity.