In order for org and study configuration to be moved around between environments, the system should be able to easily map user accounts. That's difficult because of passwords and unique email addresses. Roles are currently mapped but user accounts are not. Since views and scripts can be run as a user and resources created must have a creator, packages will need user accounts to act on their behalf. Service accounts enable running a view or a script without having to use a named account. Developer tools and deployments will be able to import and export service accounts.