When every user in your organization needs access to the same external service — like your support platform or observability tooling — asking each person to connect their own account creates friction, security risk, and inconsistency. Company-wide integrations solve this by letting an admin configure a shared connection once, making it instantly available to everyone in the organization.
You might need company-wide integrations when:
Your team uses a shared platform (like Intercom or DataDog) where individual logins aren't practical or appropriate
You want all agents across your organization to access the same data source without requiring each user to authenticate separately
You're onboarding new team members and want them to have immediate access to key integrations from day one
You need consistent, centrally managed credentials rather than relying on individual users to maintain their own connections
What Are Company-Wide Integrations?
Company-wide integrations are connections to external services that an admin sets up at the organization level. Once configured, these integrations are automatically available to all users — no individual account linking required.
This is different from personal integrations, where each user connects their own account credentials. Company-wide integrations use a single set of credentials or tokens managed centrally by your admin team.
Examples of company-wide integrations
Intercom MCP — Give every agent in your organization access to customer conversation data without each user needing an Intercom login.
DataDog MCP — Allow agents to query monitoring and observability data across your infrastructure from a single shared connection.
Company-Wide vs. Personal Integrations
Company-Wide Integrations | Personal Integrations |
Configured once by an admin | Each user connects their own account |
Shared across all users automatically | Only available to the individual user |
Best for shared organizational tools | Best for personal accounts or user-specific access |
Credentials managed centrally | Credentials stored per user |
Reduces onboarding friction | Gives users control over their own connections |
How to Set Up a Company-Wide Integration
You must have Admin or Owner permissions in elvex to complete these steps.
Navigate to Settings in the elvex sidebar.
Select Integrations from the settings menu.
Browse the available integrations or use the search bar to find the service you want to connect.
Click the integration you want to configure.
Follow the on-screen prompts to enter the required credentials, API keys, or authorization tokens for your organization's account.
Toggle the integration to Active once credentials are entered.
Confirm the integration appears as connected and is set to Company-Wide.
How Users Benefit
Zero setup required — Users don't need to find credentials, create API tokens, or navigate external platform settings.
Consistent access — Everyone works with the same connection, reducing discrepancies caused by different account permissions.
Faster onboarding — New team members have access to all shared integrations from day one.
Always up to date — When an admin updates credentials centrally, all users benefit immediately.
Permissions and Security Notes
Only users with Admin or Owner permissions can create, edit, or deactivate company-wide integrations.
The credentials entered are stored securely and are not visible to standard users.
Company-wide integrations give all users access to the integration's capabilities, but they do not grant users admin access to the external platform itself.
If you need to restrict an integration to specific users or teams, consider using a personal integration approach or reach out to your elvex admin.
Next Steps
Explore other available integrations in Settings > Integrations.
Work with your team to identify which tools should be company-wide versus personal.
To learn more about how integration permissions work, see How integration permissions and security work.
If an integration you need isn't listed, see How to Request a New Integration.