Fundamentally, that can't be implicit or it is not a requirement that can be validated or verified.
It could be states as a high level requirement as Kiron suggests but rather than the functionality should not require anyone to assume responsibilities outside their current role. In some cases, a better solution might require some organizational transformation and role changes. When computers became prevalent in the workplace, many people took on administrative work that once was assigned to assistants such as typing their own communications.
Changing roles can have significant issues such as if labor unions are involved, so the requirement might be written as not requiring users to perform duties outside of existing boundaries as defined in contracts or by HR.
Other times, you might find that being agile involves shifting some responsibilities or removing "non-value-added" steps from a process. True digital transformation also frequently involves some level of organizational transformation.
