User Licensing
This article details Coalesce's current licensing policies and procedures. Coalesce reserves the right to change its licensing policies and procedures in the future. These changes will not be imparted without prior notification to existing customers.
Coalesce is licensed on a per-individual developer basis. Each developer account that is not disabled or deleted is counted as a license. A developer is defined as an individual who is actively--within the last 90 days--building objects and pipelines in Coalesce Workspaces.
The Coalesce platform does not prevent an organization from creating additional developers once it has reached its license limit. Rather, license adherence is monitored via auditing by the Coalesce team.
Coalesce allows Environment Admin and Environment reader accounts to be used for deploy and refresh activities to account for organizations that don't wish to use individual developer accounts to do so. Service accounts used for deploy and refresh activities do not count against the license allocation.
RBAC Organizations
If you are using RBAC to manage your users, the following applies for license allocation. To learn more about RBAC, see Role-Based Access Control.
Any user assigned at least one of the following roles, will count towards your license allocation.
- Org Admin
- Project Admin
- Project Architect
- Project Contributor
Users who are only assigned the following roles are considered read-only users and will not count against the license allocation. The user can't be assigned any of the above roles.
- Org Contributor
- Org Member
- Project Member
- Environment Reader
- Environment Admin