Summary

A system administrator asks:

As a general rule when estimating the number of workbaskets for an application, is it reasonable to assume "one workbasket per role" as an initial approximation?

Suggested Approach

Access roles provide one approach to determining how many workbaskets to include in an application design. Another approach might be to consider the number of unique instructions associated with assignments - and plan to create that number of workbaskets.

For example, if your application has one assignment instructing the users to collect available rates, another to verify employment, and a third to crosscheck references, you may want three workbaskets.  That way, a pool of workers can draw assignments from a designated workbasket to handle common tasks. 

When you create and organize workbaskets based on intent rather than by user role, it allows role reclassification and/or renaming to occur later without impact on the workbaskets specified in flows rules.