Adobe Workfront

The Corma and Adobe Workfront integration connects Workfront to Corma's SaaS management and identity governance platform, so IT and operations teams can match each Workfront license to real usage and close access cleanly when people leave. Adobe Workfront is a cloud work management suite for planning, project management, collaboration and resource management, where each paid user consumes one license.

Key takeaways

• Adobe Workfront has three paid license types, Standard, Light and Contributor, and a user's license follows the access level they are assigned.
• Deactivating a user in Workfront frees the license but does not remove that user from the Workfront product profile in the Adobe Admin Console.
• Corma uses activity data to show which Standard users only review or request work, the usual candidates for a lighter Workfront license.

How does Workfront licensing work?

Under the current model described in the Workfront licenses overview, every paid user holds one of three licenses:

• Standard: plans and creates projects, request queues, templates, reports and resource management.
• Light: views, approves, logs time and manages issues, but cannot complete assigned work.
• Contributor: submits and tracks requests, uploads and approves documents.

Licenses are consumed through access levels, so a generous default access level quietly turns occasional reviewers into Standard users. Older contracts may still use the legacy Plan, Work, Review and Request licenses, which makes the mix even harder to read. At renewal time, the gap between assigned and needed licenses is where the budget leaks, and nobody inside Workfront is tasked with measuring it.

What Corma adds to Workfront

• License right-sizing: Corma compares each user's license with actual activity and flags Standard users who could move to Light or Contributor before your SaaS renewal.
• Reclaim at offboarding: when someone leaves, Corma revokes their Workfront access and triggers license reclaim, so the seat goes back to the pool instead of being bought again.
• Both layers covered: Adobe documents that deactivating a Workfront user leaves the Admin Console product profile in place, so a Corma offboarding workflow can include both steps.
• One SaaS view: Workfront sits next to your other Adobe products in Corma SaaS management, with owners, costs and renewal dates.

Companies such as Brevo use Corma to bring this control to their whole stack, as told in the Brevo customer story.

Frequently asked questions

How quickly can Corma connect to Adobe Workfront?

In about a minute: an administrator authorizes Corma through a secure OAuth flow, with no code required, and Corma starts syncing users and licenses.

Which Workfront users should move to a Light license?

Users who mostly view, approve, log time or manage issues, but never plan projects or build reports, match the Light license. Users who only submit requests and approve documents match Contributor.

Is our project data safe?

Corma requests only the permissions needed to manage users and licenses, encrypts data in transit and at rest, hosts it in France on AWS and holds ISO/IEC 27001:2022 certification.

Curious how many Workfront licenses you could free? Book a Corma demo.