Govern BigChange with Corma: Resource and Web User licences, Administrator to Basic User roles, inactive over deleted users, SSO add-on, scoped API keys.
The Corma and BigChange integration keeps your BigChange web users and field resources in line with the office staff and engineers who use them. BigChange describes itself as job management software built for UK field service teams, bringing job management, scheduling, fleet tracking, customer service and invoicing into one platform, and Simpro Group announced its acquisition of BigChange in October 2024. BigChange works with Resource licences for field staff and Web User licences for office users, so every departure touches a licence and an audit trail.
BigChange's guide to creating web users warns that deleting a web user removes their name from jobs and financial documents in the audit trail, and in User Events the link between a deleted user's entries and their identity is broken. Making a user inactive blocks login, with no limit on the number of inactive users. Setting a field resource to Not active for JobWatch frees its licence for a new resource.
BigChange's API guide recommends a non-specific User for Integration so integrations are not disrupted when someone leaves. Managing API keys from a web user profile requires an Active User licence and the Administrate API Keys permission, though a User for Integration needs no active licence for this, and BigChange recommends assigning only the scopes needed. The REST API uses OAuth 2.0 client credentials, while the legacy JobWatch API authenticates with a user's username and password plus a customer key. BigChange documents no expiry for API keys.
BigChange single sign-on connects to identity providers such as Okta, Microsoft Entra or Google Workspace, as a chargeable add-on that requires customers to enforce MFA themselves. BigChange's SSO article does not name the protocol, and BigChange documents no SCIM provisioning. Learn what single sign-on covers.
Through the BigChange REST API where it fits, which can list users with the users:read scope, or through Corma's browser-based agents in BigChange's settings. See also how Corma helps HR teams automate onboarding and offboarding.
Corma runs on AWS, with web servers and databases in data centers inside the European Union. Data is encrypted in transit and at rest, and Corma is ISO/IEC 27001:2022 certified.
Want BigChange leavers made inactive without losing their audit trail? Book a Corma demo.
Check out other integrations that could help you on managing your software licences and accesses!