The "rse_workflow" plugin enables complex bespoke workflows to be configured. Enable this via Admin -> System -> Manage Plugins -> Enterprise -> Activate.
In the base ResourceSpace installation, archive states are fixed. There is a basic workflow process in place involving user submission, approval, through to live then archived. This cannot be altered.
There are two core elements to workflow - states and actions.
A workflow state is the particular status of a given resource at a particular time, for example 'live' or 'archived'. There can be many workflow states. The workflow state typically determines who can see and edit a resource, and will determine the available workflow actions that can be performed (below).
These can be created and edited via the "Manage Workflow States" function within the "Manage Workflow" section of Admin. The existing basic workflow states will appear in that area - these cannot be edited.
From version 9.0 workflow states can be included when doing a simple search. This can only be done by administrators who have access to "Manage workflow states" and ticking the checkbox for "Search this workflow state when using Simple Search?"
Actions are the links between the workflow states. They appear as buttons on the resource view page to the users that have access to them. Each action has a 'from state' and a 'to state'. All actions for which the 'from state' matches the current resource state will appear on the resource view page, subject to user permissions. Performing an action (clicking the button) will cause the resource to move into the 'to' state.
Actions can be created, edited, and deleted via the "Manage Workflow Actions" function within the "Manage Workflow" section of Admin. A few standard actions are provided with the default installation of the plugin.
By default, all actions will appear on the resource edit page, as long as the user has write access to the 'from state' of the resource. It is possible to override this by allowing access to additional actions using the existing Permissions Manager function. This will allow users who don't have access to the 'to' state to move resources into it.
For example, a user who can only edit resources in Pending submission and Pending review could be pushing the resource into the Active state, even if the user doesn't have edit access to the Active state.
New workflow action management tools are available near the bottom of the permissions list. Ticking an action will allow the user to access this action, even when they do not have access to the 'to state' of the action.
Note that it is not necessary to tick all actions - only those where you specifically need to allow additional access in the event that the user does not have edit access to the 'to state' of the resource. In most cases using these permissions will not be necessary.
Users who can upload resources via My contributions can also view their contributions for any of the workflow states to which the user has access to. If the user group the user belongs to has blocked access to a particular workflow state (z permission) then the user will not be able to view his/ her contributions for that workflow state.