Summary and recommendation
Coralogix user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Coralogix user management lives at Settings → User Management (https://dashboard.coralogix.com/#/settings/user-management).
Admins invite users by email, assign them to one or more teams, and set a role per team - meaning the same person can hold different roles across different teams.
Every app in your stack that feeds Coralogix data should have its access reviewers mapped to the correct team scope before onboarding begins.
Quick facts
| Admin console path | Settings → User Management |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | All plans |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Organization Admin | Full access to all platform features, team management, billing, user management, and organization-level settings. | Organization Admin role operates at the organization level; team-level roles are separate. | |||
| Team Admin | Full administrative access within a specific team, including managing team members, alerts, dashboards, and integrations. | Cannot manage organization-level settings or billing. | Admin rights are scoped to the team; a user may be Admin in one team and a lower role in another. | ||
| User | Can view and interact with logs, metrics, traces, dashboards, and alerts within assigned teams. Cannot manage users or team settings. | Cannot invite or remove users, modify team settings, or access billing. | |||
| Read Only | View-only access to dashboards, logs, metrics, and traces. Cannot create or modify any resources. | Cannot create alerts, dashboards, parsing rules, or any write operations. | |||
| Custom Role | Granular permissions configured by an admin from available permission sets. | Business or Enterprise (custom pricing; verify with Coralogix sales) | Custom roles availability should be confirmed against current plan; not documented as available on all tiers. |
Permission model
- Model type: hybrid
- Description: Coralogix uses predefined roles (Organization Admin, Team Admin, User, Read Only) combined with the ability to create custom roles with granular permission sets. Permissions are scoped at both the organization level and the team level.
- Custom roles: Yes
- Custom roles plan: Business or Enterprise (custom pricing; verify with Coralogix sales)
- Granularity: Permissions can be configured per feature area (e.g., logs, metrics, traces, alerts, dashboards, integrations, user management) within a team or organization scope.
How to add users
- Navigate to Settings → User Management in the Coralogix dashboard.
- Click 'Invite User' or the equivalent invite button.
- Enter the user's email address.
- Select the team(s) to which the user should be added.
- Assign a role (Organization Admin, Team Admin, User, Read Only, or a custom role).
- Click 'Send Invitation'. The user receives an email invitation to join.
Required fields: Email address, Role, Team assignment
Watch out for:
- Users must accept the email invitation before they can access the platform.
- A user can belong to multiple teams with different roles in each team.
- If SSO is enforced, users may be required to authenticate via the configured identity provider.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Business (SCIM provisioning requires SSO to be configured; SSO availability should be confirmed against current plan) |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: Coralogix documentation indicates that admins can delete (remove) users from a team or organization via the User Management settings page. SCIM deprovisioning also supports removing users automatically when deprovisioned in the IdP.
- Navigate to Settings → User Management.
- Locate the user in the user list.
- Select the option to remove or delete the user from the team or organization.
- Confirm the action.
| Data impact | Behavior |
|---|---|
| Owned records | Not documented |
| Shared content | Not documented |
| Integrations | Not documented |
| License freed | Removing a user frees their seat; Coralogix pricing is consumption-based so the impact on billing depends on the specific plan terms. |
Watch out for:
- If SCIM provisioning is active, user removal should be managed from the IdP to avoid conflicts between manual and automated provisioning.
- Removing a user from one team does not remove them from other teams they belong to.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| User seat | Access to the Coralogix platform within assigned teams and roles. | Coralogix pricing is primarily consumption-based (data ingestion/storage); user seat costs are not separately published and are bundled into plan pricing. |
- Where to check usage: Settings → User Management (view current users and team assignments); billing details available under Settings → Billing or via Coralogix account management.
- How to identify unused seats: No officially documented automated inactive-user detection; admins must manually review the user list and last-login data if available.
- Billing notes: Coralogix pricing is primarily based on data ingestion volume, not per-seat. User seat costs are not separately itemized in publicly available pricing documentation. Custom pricing applies to Business and Enterprise plans.
The cost of manual management
Coralogix pricing is consumption-based (data ingestion volume), not per-seat, so user seat costs are not separately itemized in any publicly available documentation. Custom pricing applies to Business and Enterprise plans; no free or fixed-price tiers are published.
There is no officially documented automated inactive-user detection - admins must manually audit the user list and cross-reference last-login data if available.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Use manual provisioning if your team count is low, SSO is not yet deployed, or you need to assign asymmetric roles across teams quickly without IdP configuration overhead. Move to SCIM-backed provisioning once SSO is live and you need every app access lifecycle - join, role change, departure - handled without per-team manual edits.
Custom roles exist but plan availability should be confirmed with Coralogix sales before designing a permission model that depends on them.
Bottom line
Coralogix's hybrid role model (predefined roles plus optional custom roles, scoped per team) gives precise access control but demands deliberate team-structure planning upfront. Manual management is straightforward for small, stable teams;
the per-team role scoping becomes a maintenance liability at scale.
If your organization runs SSO on a Business or Enterprise plan, SCIM provisioning is the cleaner long-term path - but SSO must come first, and the regional cluster URL must match your data residency region or provisioning will silently fail.
Automate Coralogix workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
